[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fuOFPOZPgNIMH16PfDhzb3ehd2mFCiWT82RYBHnwscRs":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":22,"download_link":23,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":34,"analysis":131,"fingerprints":186},"dont-mess-up-prod","Don't Mess Up Prod","1.0.1","Dave Kellam","https:\u002F\u002Fprofiles.wordpress.org\u002Feightface\u002F","\u003Cp>Don’t Mess Up Prod helps developers and content managers quickly identify which environment they’re working in by displaying a colored indicator in the WordPress admin bar. Hopefully this prevents messing up production 😅\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdavekellam\u002Fdont-mess-up-prod\" rel=\"nofollow ugc\">Active development is on Github\u003C\u002Fa>\u003C\u002Fp>\n","Displays a colored environment indicator in the admin bar.",0,204,"2026-01-28T21:10:00.000Z","6.9.4","6.7","8.0",[18,19,20,21],"admin-bar","debug","development","environment","https:\u002F\u002Fgithub.com\u002Fdavekellam\u002Fdont-mess-up-prod","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdont-mess-up-prod.1.0.1.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":11,"avg_security_score":24,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},"eightface",1,30,94,"2026-04-04T07:16:21.522Z",[35,55,76,92,111],{"slug":36,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":24,"num_ratings":45,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":52,"download_link":53,"security_score":54,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"what-template","What Template","0.1","Brian Alexander","https:\u002F\u002Fprofiles.wordpress.org\u002Fironprogrammer\u002F","\u003Cp>Adds the current page’s template name to the admin bar.\u003C\u002Fp>\n\u003Cp>Because this plugin reveals potentially sensitive information about the active theme, it is recommended for development environments only, and should not be enabled on a production site.\u003C\u002Fp>\n","Adds the current page's template name to the admin bar.",1000,22245,3,"2024-07-19T20:49:00.000Z","6.6.5","3.1","",[18,19,20,51],"template","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwhat-template\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwhat-template.0.1.2.zip",92,{"slug":56,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":11,"num_ratings":11,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":68,"tags":69,"homepage":73,"download_link":74,"security_score":75,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"dev-info-bar","Dev Info Bar","1.0.2","istvankrucsanyica","https:\u002F\u002Fprofiles.wordpress.org\u002Fistvankrucsanyica\u002F","\u003Cp>A simple WordPress extension which adds itself to the admin bar, providing system information such as PHP, MySQL version and  details of the WordPress being used.\u003C\u002Fp>\n","A simple WordPress extension which adds itself to the admin bar, providing system information such as PHP, MySQL version and  details of the WordPress …",80,2303,"2019-01-21T19:14:00.000Z","5.0.25","4.5","5.6",[70,18,71,21,72],"admin","debugging","server","http:\u002F\u002Fistvankrucsanyica.com\u002Fdevinfobar\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdev-info-bar.1.0.2.zip",85,{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":11,"downloaded":84,"rating":11,"num_ratings":11,"last_updated":85,"tested_up_to":14,"requires_at_least":86,"requires_php":87,"tags":88,"homepage":90,"download_link":91,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"current-template-insights","Current Template Insights","1.0.3","macurious","https:\u002F\u002Fprofiles.wordpress.org\u002Fmacurious\u002F","\u003Cp>\u003Cstrong>Displays the current template file and key page details in the WordPress admin bar for logged-in administrators.\u003C\u002Fstrong>\u003Cbr \u002F>\nNo setup required: just install, activate, and see the info bar on any front-end page.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003Cbr \u002F>\n– Shows “📄 Template: ” in the front-end admin bar\u003Cbr \u002F>\n– Details on hover\u002Fclick: full template path, post ID, post type, slug, theme name & version, locale, body classes, query vars, conditionals, DB query count, memory usage, and more\u003Cbr \u002F>\n– No settings page, no configuration\u003Cbr \u002F>\n– Works with classic and block\u002FFSE themes (special info for block themes)\u003Cbr \u002F>\n– Developer-friendly, lightweight, no bloat\u003C\u002Fp>\n","Quickly view the active template file and important page information directly in your WordPress admin bar.",347,"2025-12-17T16:14:00.000Z","5.5","7.4",[18,19,20,51,89],"theme","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcurrent-template-insights\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcurrent-template-insights.1.0.3.zip",{"slug":93,"name":94,"version":95,"author":96,"author_profile":97,"description":98,"short_description":99,"active_installs":100,"downloaded":101,"rating":102,"num_ratings":103,"last_updated":104,"tested_up_to":14,"requires_at_least":105,"requires_php":87,"tags":106,"homepage":109,"download_link":110,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"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","6.1",[19,107,20,108,93],"debug-bar","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",{"slug":112,"name":113,"version":114,"author":115,"author_profile":116,"description":117,"short_description":118,"active_installs":119,"downloaded":120,"rating":24,"num_ratings":121,"last_updated":122,"tested_up_to":123,"requires_at_least":124,"requires_php":49,"tags":125,"homepage":129,"download_link":130,"security_score":75,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"monkeyman-rewrite-analyzer","Monkeyman Rewrite Analyzer","1.0","Jan Fabry","https:\u002F\u002Fprofiles.wordpress.org\u002Fjanfabry\u002F","\u003Cp>This is a tool to understand your rewrite rules (“Pretty Permalinks”). It is indispensable if you are adding or modifying rules and want to understand how they work (or why they don’t work).\u003C\u002Fp>\n\u003Cp>It is only an analyzer, it does not change any rules for you. It parses the rules down to their components and shows the connection with the resulting query variables. It allows you to try out different URLs to see which rules will match and what the value of the different query variables will be (see screenshots).\u003C\u002Fp>\n\u003Cp>This plugin was written as a tool to help answering questions about rewrite rules on \u003Ca href=\"http:\u002F\u002Fwordpress.stackexchange.com\u002F\" rel=\"nofollow ugc\">the WordPress Stack Exchange\u003C\u002Fa>.\u003C\u002Fp>\n","Making sense of the rewrite mess. Display and play with your rewrite rules.",2000,73356,26,"2011-05-12T17:49:00.000Z","3.2.1","3.0",[19,20,126,127,128],"mod_rewrite","permalinks","rewrite","http:\u002F\u002Fwordpress.stackexchange.com\u002Fq\u002F3606\u002F8","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmonkeyman-rewrite-analyzer.1.0.zip",{"attackSurface":132,"codeSignals":173,"taintFlows":181,"riskAssessment":182,"analyzedAt":185},{"hooks":133,"ajaxHandlers":169,"restRoutes":170,"shortcodes":171,"cronEvents":172,"entryPointCount":11,"unprotectedCount":11},[134,140,144,150,154,157,163,166],{"type":135,"name":136,"callback":137,"file":138,"line":139},"action","admin_menu","add_settings_page","includes\\class-admin-settings.php",81,{"type":135,"name":141,"callback":142,"file":138,"line":143},"admin_init","register_settings",82,{"type":145,"name":146,"callback":147,"priority":148,"file":138,"line":149},"filter","dmup_environment_colors","apply_saved_colors",20,83,{"type":145,"name":151,"callback":152,"priority":148,"file":138,"line":153},"dmup_environment_urls","apply_saved_urls",84,{"type":145,"name":155,"callback":156,"file":138,"line":75},"plugin_action_links_dont-mess-up-prod\u002Fdont-mess-up-prod.php","add_plugin_action_links",{"type":135,"name":158,"callback":159,"priority":160,"file":161,"line":162},"admin_bar_menu","add_environment_indicator_item",999,"includes\\class-environment-indicator.php",93,{"type":135,"name":164,"callback":165,"file":161,"line":32},"admin_enqueue_scripts","enqueue_styles",{"type":135,"name":167,"callback":165,"file":161,"line":168},"wp_enqueue_scripts",95,[],[],[],[],{"dangerousFunctions":174,"sqlUsage":175,"outputEscaping":177,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":30,"bundledLibraries":180},[],{"prepared":11,"raw":11,"locations":176},[],{"escaped":178,"rawEcho":11,"locations":179},32,[],[],[],{"summary":183,"deductions":184},"The 'dont-mess-up-prod' plugin version 1.0.1 exhibits a strong security posture based on the provided static analysis. The plugin effectively minimizes its attack surface, with no identified AJAX handlers, REST API routes, shortcodes, or cron events.  Crucially, all detected code signals indicate good security practices. There are no dangerous functions used, all SQL queries are properly prepared, and all output is correctly escaped. File operations and external HTTP requests are absent, and while there are no nonce checks, a capability check is present, which is a positive indicator for authorization. The absence of any taint analysis findings further strengthens this positive assessment, signifying no identified issues with unsanitized data flow.  The plugin also has a clean vulnerability history, with no known CVEs, indicating a well-maintained codebase free from past exploitable flaws.  Overall, this plugin appears to be very securely coded with robust protections against common web vulnerabilities. The primary strength lies in its minimal attack surface and adherence to secure coding principles. The only slight concern, though not explicitly a vulnerability in this context, is the absence of nonce checks, which could be a consideration in more complex scenarios, but given the lack of other entry points, it poses minimal risk here.",[],"2026-03-17T06:48:23.619Z",{"wat":187,"direct":193},{"assetPaths":188,"generatorPatterns":190,"scriptPaths":191,"versionParams":192},[189],"\u002Fwp-content\u002Fplugins\u002Fdont-mess-up-prod\u002Fassets\u002Fcss\u002Fadmin-bar.css",[],[],[],{"cssClasses":194,"htmlComments":198,"htmlAttributes":199,"restEndpoints":202,"jsGlobals":203,"shortcodeOutput":204},[195,196,197],"dmup-environment-indicator","dmup-environment-","dmup-nav-external",[],[200,201],"class=\"dmup-environment-","class=\"dmup-nav-external\" target=\"_blank\" rel=\"noopener\"",[],[],[]]