[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fE2yB4ljw8Unx2bovH5HAVxG7a9mK2n-PLnFawJnhSlg":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":24,"download_link":25,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":38,"analysis":122,"fingerprints":265},"blackbar","Black Bar","4.1.4","Gemini Labs","https:\u002F\u002Fprofiles.wordpress.org\u002Fgeminilabs\u002F","\u003Cp>Black Bar is an unobtrusive Debug Bar for WordPress developers. It collects and displays errors, executed SQL queries, slow actions and hooks, theme templates, global variables, and provides a profiler.\u003C\u002Fp>\n\u003Cp>How it helps you with development:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Debug your code with the Console\u003C\u002Fli>\n\u003Cli>Inspect global variables (COOKIE, GET, POST, SERVER, SESSION, WP_Screen)\u003C\u002Fli>\n\u003Cli>Measure performance of your code with the Profiler\u003C\u002Fli>\n\u003Cli>View any PHP errors that occur when loading a page in the Console\u003C\u002Fli>\n\u003Cli>View executed MySQL queries along with execution time and backtrace\u003C\u002Fli>\n\u003Cli>View template files of the active theme in loaded order\u003C\u002Fli>\n\u003Cli>View the 50 slowest action and filter hooks along with callbacks ordered by priority\u003C\u002Fli>\n\u003C\u002Ful>\n","Black Bar is an unobtrusive Debug Bar for WordPress developers that attaches itself to the bottom of the browser window.",600,38607,100,9,"2025-12-01T22:51:00.000Z","6.9.4","6.1","7.4",[20,21,22,23],"debug","debug-bar","debugbar","development","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fblackbar","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblackbar.4.1.4.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"geminilabs",3,70610,94,427,75,"2026-04-04T00:36:22.123Z",[39,56,76,95,110],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":52,"homepage":54,"download_link":55,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"query-monitor","Query Monitor – The developer tools panel for WordPress","3.20.2","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>Query Monitor is the developer tools panel for WordPress and WooCommerce. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more.\u003C\u002Fp>\n\u003Cp>It includes some advanced features such as debugging of Ajax calls, REST API calls, user capability checks, and full support for block themes and full site editing. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions.\u003C\u002Fp>\n\u003Cp>Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item.\u003C\u002Fp>\n\u003Cp>Query Monitor supports versions of WordPress up to three years old, and PHP version 7.4 or higher.\u003C\u002Fp>\n\u003Cp>For complete information, please see \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002F\" rel=\"nofollow ugc\">the Query Monitor website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Here’s an overview of what’s shown for each page load:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (\u003Ccode>SELECT\u003C\u002Fcode>, \u003Ccode>UPDATE\u003C\u002Fcode>, \u003Ccode>DELETE\u003C\u002Fcode>, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each.\u003C\u002Fli>\n\u003Cli>The template filename, the complete template hierarchy, and names of all template parts that were loaded or not loaded (for block themes and classic themes).\u003C\u002Fli>\n\u003Cli>PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar.\u003C\u002Fli>\n\u003Cli>Usage of “Doing it Wrong” or “Deprecated” functionality in the code on your site.\u003C\u002Fli>\n\u003Cli>Blocks and associated properties within post content and within full site editing (FSE).\u003C\u002Fli>\n\u003Cli>Matched rewrite rules, associated query strings, and query vars.\u003C\u002Fli>\n\u003Cli>Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies.\u003C\u002Fli>\n\u003Cli>Language settings and loaded translation files (MO files and JSON files) for each text domain.\u003C\u002Fli>\n\u003Cli>HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.\u003C\u002Fli>\n\u003Cli>User capability checks, along with the result and any parameters passed to the capability check.\u003C\u002Fli>\n\u003Cli>Environment information, including detailed information about PHP, the database, WordPress, and the web server.\u003C\u002Fli>\n\u003Cli>The values of all WordPress conditional functions such as \u003Ccode>is_single()\u003C\u002Fcode>, \u003Ccode>is_home()\u003C\u002Fcode>, etc.\u003C\u002Fli>\n\u003Cli>Transients that were updated.\u003C\u002Fli>\n\u003Cli>Usage of \u003Ccode>switch_to_blog()\u003C\u002Fcode> and \u003Ccode>restore_current_blog()\u003C\u002Fcode> on Multisite installations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect.\u003C\u002Fli>\n\u003Cli>The response from any jQuery-initiated Ajax request on the page will contain various debugging information in its headers. PHP errors also get output to the browser’s developer console.\u003C\u002Fli>\n\u003Cli>The response from an authenticated WordPress REST API request will contain an overview of performance information and PHP errors in its headers, as long as the authenticated user has permission to view Query Monitor’s output. An \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Frest-api\u002Fusing-the-rest-api\u002Fglobal-parameters\u002F#_envelope\" rel=\"nofollow ugc\">an enveloped REST API request\u003C\u002Fa> will include even more debugging information in the \u003Ccode>qm\u003C\u002Fcode> property of the response.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.\u003C\u002Fp>\n\u003Cp>In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.\u003C\u002Fp>\n\u003Ch3>Other Plugins\u003C\u002Fh3>\n\u003Cp>I maintain several other plugins for developers. Check them out:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002F\" rel=\"ugc\">User Switching\u003C\u002Fa> provides instant switching between user accounts in WordPress.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-crontrol\u002F\" rel=\"ugc\">WP Crontrol\u003C\u002Fa> lets you view and control what’s happening in the WP-Cron system\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor is private by default and always will be. It does not persistently store any of the data that it collects. It does not send data to any third party, nor does it include any third party resources. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Fprivacy\u002F\" rel=\"nofollow ugc\">Query Monitor’s full privacy statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor aims to be fully accessible to all of its users. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Faccessibility\u002F\" rel=\"nofollow ugc\">Query Monitor’s full accessibility statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n","Query Monitor is the developer tools panel for WordPress and WooCommerce.",200000,19156533,98,463,"2025-12-11T22:16:00.000Z",[20,21,23,53,40],"performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":13,"num_ratings":32,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":69,"tags":70,"homepage":73,"download_link":74,"security_score":75,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"debug-bar-list-dependencies","Debug Bar List Script & Style Dependencies","1.1","Per Søderlind","https:\u002F\u002Fprofiles.wordpress.org\u002Fpers\u002F","\u003Cp>We all know that when we’re add a script or style to WordPress, we should use \u003Ccode>wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer )\u003C\u002Fcode> and \u003Ccode>wp_enqueue_style( $handle, $src, $deps, $ver, $media )\u003C\u002Fcode> as in:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function themeslug_enqueue_style() {\n    wp_enqueue_style( 'core', 'style.css', array('twentytwelve-style') );\n}\n\nfunction themeslug_enqueue_script() {\n    wp_enqueue_script( 'my-js', 'filename.js', array('jquery') );\n}\n\nadd_action( 'wp_enqueue_scripts', 'themeslug_enqueue_style' );\nadd_action( 'wp_enqueue_scripts', 'themeslug_enqueue_script' )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>$deps (dependencies), the handle name and an optional parameter, lets you control when\u002Fwhere your script or style should be added. If $deps is \u003Ccode>array('jquery')\u003C\u002Fcode>, your script will be loaded after jquery is loaded.\u003C\u002Fp>\n\u003Cp>The problem is, which one exists and in which order are they loaded ?\u003C\u002Fp>\n\u003Cp>Debug Bar List Script & Style Dependencies, an add-on to \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa>, will list the dependencies.\u003C\u002Fp>\n\u003Ch4>Use\u003C\u002Fh4>\n\u003Cp>To view the loaded scripts and styles\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Front-end: Go to the front-end, and on the admin bar choose Debug and view Script & Style Dependencies\u003C\u002Fli>\n\u003Cli>Back-end: Go to the back-end, on the admin bar choose Debug and view Script & Style Dependencies\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Note, the front-end and back-end loads different scripts and styles. Also, different pages on the front-end and back-end can load different scripts and styles.\u003C\u002Fp>\n","Debug Bar List Script & Style Dependencies is an add-on to WordPress Debug Bar",200,86242,"2016-12-12T20:11:00.000Z","4.7.32","3.4","",[20,21,23,71,72],"wp_enqueue_script","wp_enqueue_style","http:\u002F\u002Fsoderlind.no\u002Fdebug-bar-list-script-and-style-dependencies\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-list-dependencies.1.1.2.zip",85,{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":86,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":68,"requires_php":90,"tags":91,"homepage":93,"download_link":94,"security_score":75,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"debug-bar-post-types","Debug Bar Post Types","2.0.0","Juliette Reinders Folmer","https:\u002F\u002Fprofiles.wordpress.org\u002Fjrf\u002F","\u003Cp>Debug Bar Post Types adds a new panel to the Debug Bar that displays detailed information about the registered post types for your site.\u003C\u002Fp>\n\u003Ch4>Important\u003C\u002Fh4>\n\u003Cp>This plugin requires the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa> plugin to be installed and activated.\u003C\u002Fp>\n\u003Cp>Also note that this plugin should be used solely for debugging and\u002For in a development environment and is not intended for use on a production site.\u003C\u002Fp>\n\u003Cp>If you like this plugin, please \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Fdebug-bar-post-types\" rel=\"ugc\">rate and\u002For review\u003C\u002Fa> it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdebug-bar-post-types\" rel=\"ugc\">Support Forum\u003C\u002Fa> or in the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjrfnl\u002FDebug-Bar-Post-Types\u002Fissues\" rel=\"nofollow ugc\">GitHub repository\u003C\u002Fa>.\u003C\u002Fp>\n","Debug Bar Post Types adds a new panel to the Debug Bar with detailed information about registered post types. Requires \"Debug Bar\" plugin.",50,37131,80,1,"2018-01-22T11:24:00.000Z","4.9.29","5.2.4",[21,77,22,92],"post-types","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar-post-types\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-post-types.2.0.0.zip",{"slug":96,"name":97,"version":98,"author":80,"author_profile":81,"description":99,"short_description":100,"active_installs":101,"downloaded":102,"rating":13,"num_ratings":32,"last_updated":103,"tested_up_to":104,"requires_at_least":105,"requires_php":69,"tags":106,"homepage":108,"download_link":109,"security_score":75,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"debug-bar-shortcodes","Debug Bar Shortcodes","2.0.3","\u003Cp>Debug Bar Shortcodes adds a new panel to the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa> that displays the registered shortcodes for the current request.\u003C\u002Fp>\n\u003Cp>Additionally it will show you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Which function\u002Fmethod is called by the shortcode\u003C\u002Fli>\n\u003Cli>Whether the shortcode is used on the current post\u002Fpage\u002Fpost type and how (only when on singular)\u003C\u002Fli>\n\u003Cli>Any additional information available about the shortcode, such as a description, which parameters it takes, whether or not it is self-closing.\u003Cbr \u002F>\n\u003Cem>Want to control the additional information displayed about your own shortcodes ? You can! See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar-shortcodes\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for more info.\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Find out all pages\u002Fposts\u002Fetc on which a shortcode is used\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin is compatible with the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flrh-shortcode-list\u002F\" rel=\"ugc\">LRH-Shortcode list\u003C\u002Fa> and the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fshortcode-ui\u002F\" rel=\"ugc\">Shortcake\u002FShortcode UI\u003C\u002Fa> plugins. Additional information about a shortcode provided to these plugins will be taken into account and made available through this plugin too.\u003C\u002Fp>\n\u003Ch4>Why is it useful to have insight into the shortcodes ?\u003C\u002Fh4>\n\u003Cp>There are a number of typical uses I can think of:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>If you are a \u003Cstrong>\u003Cem>blog author\u003C\u002Fem>\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>to know which shortcodes you can use in your posts\u002Fpages.\u003C\u002Fli>\n\u003Cli>if you switch plugins or remove a plugin, to know in which posts\u002Fpages you need to remove\u002Freplace old shortcodes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you are a \u003Cstrong>\u003Cem>web designer \u002F web master\u003C\u002Fem>\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>if you switch plugins or remove a plugin, to know in which posts\u002Fpages you need to remove\u002Freplace old shortcodes.\u003C\u002Fli>\n\u003Cli>to know which shortcodes you can use in theme files.\u003C\u002Fli>\n\u003Cli>to avoid name conflicts for website specific shortcodes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you are a \u003Cstrong>\u003Cem>developer\u003C\u002Fem>\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>to avoid name conflicts with shortcodes registered by other plugins\u002Fthemes.\u003C\u002Fli>\n\u003Cli>to check whether your shortcode registers properly and whether the conditionals are applied correctly.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Important\u003C\u002Fh4>\n\u003Cp>This plugin requires the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa> plugin to be installed and activated.\u003C\u002Fp>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>The additional information functionality is inspired by \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flrh-shortcode-list\u002F\" rel=\"ugc\">LRH-Shortcode list\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fshortcode-reference\u002F\" rel=\"ugc\">Shortcode reference\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>The finding of shortcode uses throughout the site is inspired by \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftr-all-shortcodes\u002F\" rel=\"ugc\">TR All Shortcodes\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you like this plugin, please \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Fdebug-bar-shortcodes\" rel=\"ugc\">rate and\u002For review\u003C\u002Fa> it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdebug-bar-shortcodes\" rel=\"ugc\">Support Forum\u003C\u002Fa> or in the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjrfnl\u002FDebug-Bar-Shortcodes\u002Fissues\" rel=\"nofollow ugc\">GitHub repository\u003C\u002Fa>.\u003C\u002Fp>\n","Debug Bar Shortcodes adds a new panel to the Debug Bar that displays the registered shortcodes for the current request.",40,26220,"2016-04-30T05:41:00.000Z","4.4.34","3.6",[21,96,22,107],"shortcodes","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar-shortcodes\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-shortcodes.2.0.3.zip",{"slug":111,"name":112,"version":79,"author":80,"author_profile":81,"description":113,"short_description":114,"active_installs":115,"downloaded":116,"rating":13,"num_ratings":87,"last_updated":117,"tested_up_to":89,"requires_at_least":68,"requires_php":90,"tags":118,"homepage":120,"download_link":121,"security_score":75,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"debug-bar-constants","Debug Bar Constants","\u003Cp>Debug Bar Constants adds three new panels to the Debug Bar that display the defined constants available to you as a developer for the current request:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WP Constants\u003C\u002Fli>\n\u003Cli>WP Class Constants\u003C\u002Fli>\n\u003Cli>PHP Constants\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Important\u003C\u002Fh4>\n\u003Cp>This plugin requires the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa> plugin to be installed and activated.\u003C\u002Fp>\n\u003Cp>Also note that this plugin should be used solely for debugging and\u002For in a development environment and is not intended for use on a production site.\u003C\u002Fp>\n\u003Cp>If you like this plugin, please \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Fdebug-bar-constants\" rel=\"ugc\">rate and\u002For review\u003C\u002Fa> it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdebug-bar-constants\" rel=\"ugc\">Support Forum\u003C\u002Fa> or in the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjrfnl\u002FDebug-Bar-Constants\u002Fissues\" rel=\"nofollow ugc\">GitHub repository\u003C\u002Fa>.\u003C\u002Fp>\n","Debug Bar Constants adds three new panels to the Debug Bar that display the defined WP and PHP constants for the current request.",30,53492,"2018-01-22T11:21:00.000Z",[119,21,111,22],"constants","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar-constants\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-constants.2.0.0.zip",{"attackSurface":123,"codeSignals":184,"taintFlows":255,"riskAssessment":256,"analyzedAt":264},{"hooks":124,"ajaxHandlers":180,"restRoutes":181,"shortcodes":182,"cronEvents":183,"entryPointCount":26,"unprotectedCount":26},[125,131,134,140,143,148,151,154,158,161,165,168,173,176],{"type":126,"name":127,"callback":128,"file":129,"line":130},"action","activated_plugin","deactivate","activate.php",48,{"type":126,"name":132,"callback":128,"file":129,"line":133},"admin_notices",49,{"type":135,"name":136,"callback":137,"file":138,"line":139},"filter","gform_noconflict_scripts","closure","compatibility.php",15,{"type":135,"name":141,"callback":137,"file":138,"line":142},"gform_noconflict_styles",24,{"type":126,"name":144,"callback":145,"file":146,"line":147},"all","initConsole","plugin\\Application.php",54,{"type":126,"name":144,"callback":149,"file":146,"line":150},"initHooks",55,{"type":126,"name":144,"callback":152,"file":146,"line":153},"initProfiler",56,{"type":126,"name":155,"callback":156,"file":146,"line":157},"plugins_loaded","registerLanguages",59,{"type":126,"name":159,"callback":137,"file":146,"line":160},"init",60,{"type":126,"name":162,"callback":163,"file":146,"line":164},"admin_enqueue_scripts","enqueueAssets",64,{"type":126,"name":166,"callback":163,"file":146,"line":167},"wp_enqueue_scripts",65,{"type":126,"name":169,"callback":170,"priority":171,"file":146,"line":172},"admin_footer","renderBar",99999,66,{"type":126,"name":174,"callback":170,"priority":171,"file":146,"line":175},"wp_footer",67,{"type":135,"name":177,"callback":178,"file":146,"line":179},"admin_body_class","filterBodyClasses",68,[],[],[],[],{"dangerousFunctions":185,"sqlUsage":186,"outputEscaping":188,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":87,"bundledLibraries":254},[],{"prepared":26,"raw":26,"locations":187},[],{"escaped":167,"rawEcho":189,"locations":190},34,[191,195,197,199,201,203,205,208,209,210,211,213,214,216,218,220,222,225,227,229,231,233,235,237,238,239,240,242,243,244,246,248,250,252],{"file":192,"line":193,"context":194},"views\\debug-bar.php",6,"raw output",{"file":192,"line":196,"context":194},12,{"file":192,"line":198,"context":194},20,{"file":192,"line":200,"context":194},25,{"file":192,"line":202,"context":194},31,{"file":192,"line":204,"context":194},32,{"file":206,"line":207,"context":194},"views\\panels\\console.php",8,{"file":206,"line":198,"context":194},{"file":206,"line":202,"context":194},{"file":206,"line":204,"context":194},{"file":206,"line":212,"context":194},33,{"file":206,"line":189,"context":194},{"file":206,"line":215,"context":194},35,{"file":206,"line":217,"context":194},36,{"file":206,"line":219,"context":194},37,{"file":206,"line":221,"context":194},38,{"file":223,"line":224,"context":194},"views\\panels\\hooks.php",7,{"file":223,"line":226,"context":194},18,{"file":223,"line":228,"context":194},19,{"file":223,"line":230,"context":194},21,{"file":223,"line":232,"context":194},22,{"file":223,"line":234,"context":194},28,{"file":223,"line":236,"context":194},29,{"file":223,"line":115,"context":194},{"file":223,"line":202,"context":194},{"file":223,"line":204,"context":194},{"file":241,"line":193,"context":194},"views\\panels\\profiler.php",{"file":241,"line":224,"context":194},{"file":241,"line":207,"context":194},{"file":245,"line":224,"context":194},"views\\panels\\queries.php",{"file":245,"line":247,"context":194},13,{"file":245,"line":249,"context":194},14,{"file":245,"line":251,"context":194},16,{"file":245,"line":253,"context":194},17,[],[],{"summary":257,"deductions":258},"The static analysis of the \"blackbar\" plugin v4.1.4 reveals a generally positive security posture.  There are no identified dangerous functions, SQL injection vulnerabilities due to prepared statements, or file operations. The absence of external HTTP requests and a lack of bundled libraries further contribute to a reduced attack surface. The plugin also shows good practices regarding output escaping, with a high percentage of outputs being properly escaped. The vulnerability history is also completely clear, with no past or present CVEs recorded, indicating a stable and secure development history.",[259,262],{"reason":260,"points":261},"Unescaped output rate is concerning",5,{"reason":263,"points":139},"Missing nonce checks on entry points","2026-03-16T19:27:04.356Z",{"wat":266,"direct":274},{"assetPaths":267,"generatorPatterns":270,"scriptPaths":271,"versionParams":272},[268,269],"\u002Fwp-content\u002Fplugins\u002Fblackbar\u002Fassets\u002Fblackbar.js","\u002Fwp-content\u002Fplugins\u002Fblackbar\u002Fassets\u002Fblackbar.css",[],[268],[273],"ver=4.1.4",{"cssClasses":275,"htmlComments":276,"htmlAttributes":277,"restEndpoints":279,"jsGlobals":280,"shortcodeOutput":282},[4],[],[278],"data-blackbar-hook",[],[281],"window.blackbar",[]]