[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fm0DUdnhAvCJvIysKi3GSNmo9kilotdvJXfsQ_OvtCEY":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":21,"download_link":22,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":35,"analysis":135,"fingerprints":165},"fg-debug-bar-rewrite-rules","Debug Bar Rewrite Rules","1.1.3","Kerfred","https:\u002F\u002Fprofiles.wordpress.org\u002Fkerfred\u002F","\u003Cp>Displays the current rewrite rules for the site. Requires the debug bar plugin.\u003C\u002Fp>\n","Displays the current rewrite rules for the site. Requires the debug bar plugin.",50,9776,0,"2025-04-29T08:47:00.000Z","6.8.5","3.1","5.3",[19,20],"debug-bar","rewrite-rules","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffg-debug-bar-rewrite-rules\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffg-debug-bar-rewrite-rules.1.1.3.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":31,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"kerfred",9,9650,99,674,78,"2026-04-04T16:47:53.604Z",[36,57,81,98,120],{"slug":37,"name":5,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":23,"num_ratings":45,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":54,"download_link":55,"security_score":56,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"debug-bar-rewrite-rules","0.6.5","Oleg Butuzov","https:\u002F\u002Fprofiles.wordpress.org\u002Fbutuzov\u002F","\u003Cp>Debug Bar Rewrite Rules adds information about Rewrite Rules (changed via filters) to a new panel in the Debug Bar. This plugin is an extension for \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa>, but it is also can work in standalone mode (as admin tools page). Note: this plugin not able to track \u003Ccode>add_rewrite_rule\u003C\u002Fcode> function calls, for a reason this function is untraceable.\u003C\u002Fp>\n\u003Cp>Once installed, you will have access to the following information:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Number of existing rewrite rules\u003C\u002Fli>\n\u003Cli>List of rewrite rules\u003C\u002Fli>\n\u003Cli>List of available filter hooks that can affect rewrite rules.\u003C\u002Fli>\n\u003Cli>List of filters that affects rewrite rules.\u003C\u002Fli>\n\u003Cli>Ability to search in rules with highlighting matches.\u003C\u002Fli>\n\u003Cli>Ability to test url and see what rules can be applied to it.\u003C\u002Fli>\n\u003Cli>Ability to flush rules directly from debug bar panel\u002Ftools page.\u003C\u002Fli>\n\u003C\u002Ful>\n","Debug Bar Rewrite Rules adds a new panel to Debug Bar that displays information about WordPress Rewrites Rules (if used).",800,54106,5,"2024-07-06T08:11:00.000Z","6.5.8","3.4","",[51,19,52,20,53],"debug","permalinks","testing","https:\u002F\u002Fgithub.com\u002Fbutuzov\u002FDebug-Bar-Rewrite-Rules","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.6.5.zip",92,{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":65,"downloaded":66,"rating":67,"num_ratings":68,"last_updated":69,"tested_up_to":70,"requires_at_least":71,"requires_php":72,"tags":73,"homepage":76,"download_link":77,"security_score":78,"vuln_count":79,"unpatched_count":13,"last_vuln_date":80,"fetched_at":25},"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.9.4","6.1","7.4",[51,19,74,75,58],"development","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",97,1,"2026-03-30 23:21:22",{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":89,"downloaded":90,"rating":23,"num_ratings":91,"last_updated":92,"tested_up_to":70,"requires_at_least":93,"requires_php":72,"tags":94,"homepage":96,"download_link":97,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"rewrite-rules-inspector","Rewrite Rules Inspector","1.6.0","Automattic","https:\u002F\u002Fprofiles.wordpress.org\u002Fautomattic\u002F","\u003Cp>A simple WordPress admin tool for inspecting rewrite rules. View a listing of all your rewrite rules, see which rewrite rules match a given URL (and the priorities they match in), or filter by different sources of rewrite rules. Perform a soft flush of your rewrite rules to regenerate them.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002FRewrite-Rules-Inspector\u002F\" rel=\"nofollow ugc\">Developed on GitHub\u003C\u002Fa> — pull requests are always welcome. Please leave feedback, questions, bug reports, and feature requests in the GitHub issues.\u003C\u002Fp>\n\u003Ch3>Where to find it\u003C\u002Fh3>\n\u003Cp>Go to \u003Ccode>Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Rewrite Rules\u003C\u002Fcode> in the WordPress admin.\u003C\u002Fp>\n\u003Ch3>URL Tester\u003C\u002Fh3>\n\u003Cp>Quickly test any URL (or path) against your site’s rewrite rules:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>See whether the URL would be a \u003Cstrong>404\u003C\u002Fstrong> or which rule would match first (the one WordPress uses).\u003C\u002Fli>\n\u003Cli>View the list of \u003Cstrong>all matching rules\u003C\u002Fstrong>, in match priority order.\u003C\u002Fli>\n\u003Cli>Inspect the \u003Cstrong>query variables\u003C\u002Fstrong> extracted from the match and the resulting \u003Cstrong>final query\u003C\u002Fstrong> WordPress would run.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Works with full URLs or paths and automatically handles sites installed in a subdirectory.\u003C\u002Fp>\n\u003Ch3>Permastructs\u003C\u002Fh3>\n\u003Cp>Browse a table of all \u003Cstrong>permastructs\u003C\u002Fstrong> that WordPress is aware of, including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Name\u003C\u002Fstrong> — the permastruct key (e.g. for posts, taxonomies, authors).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Structure\u003C\u002Fstrong> — the permalink structure pattern used to generate rules.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Description\u003C\u002Fstrong> — a human-friendly summary of what the permastruct controls.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Flush Rules\u003C\u002Fh3>\n\u003Cp>The “Flush Rules” button allows you to regenerate your site’s rewrite rules. Here’s exactly what happens when you click it:\u003C\u002Fp>\n\u003Ch4>What the Flush Rules Button Does\u003C\u002Fh4>\n\u003Cp>When you click the “Flush Rules” button, the following sequence occurs:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Security Check\u003C\u002Fstrong>: The system verifies you have the proper permissions (\u003Ccode>manage_options\u003C\u002Fcode> capability) and validates the security nonce to prevent unauthorized access.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Cache Clearing\u003C\u002Fstrong>: WordPress deletes the cached rewrite rules from the options cache using \u003Ccode>wp_cache_delete('rewrite_rules', 'options')\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Rule Regeneration\u003C\u002Fstrong>: WordPress calls \u003Ccode>flush_rewrite_rules(false)\u003C\u002Fcode> to regenerate all rewrite rules based on:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Current permalink structure settings\u003C\u002Fli>\n\u003Cli>Custom post types and taxonomies\u003C\u002Fli>\n\u003Cli>Any custom rewrite rules added by themes or plugins\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Hook Execution\u003C\u002Fstrong>: The \u003Ccode>rri_flush_rules\u003C\u002Fcode> action hook is fired, allowing other plugins to perform additional cleanup or actions after the flush.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Success Feedback\u003C\u002Fstrong>: You’re redirected back to the Rewrite Rules Inspector page with a success message confirming the rules have been flushed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>When to Use Flush Rules\u003C\u002Fh4>\n\u003Cp>Use the “Flush Rules” button when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Missing Rules\u003C\u002Fstrong>: You see rules marked as “missing” (red background) in the inspector\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom URLs Not Working\u003C\u002Fstrong>: Your custom permalinks or post type URLs aren’t working properly\u003C\u002Fli>\n\u003Cli>\u003Cstrong>After Plugin Changes\u003C\u002Fstrong>: You’ve activated\u002Fdeactivated plugins that register custom rewrite rules\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Permalink Structure Changes\u003C\u002Fstrong>: You’ve modified your site’s permalink structure\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Post Type Issues\u003C\u002Fstrong>: New custom post types or taxonomies aren’t generating proper URLs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Important Notes\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Soft Flush\u003C\u002Fstrong>: This performs a “soft” flush (using \u003Ccode>flush_rewrite_rules(false)\u003C\u002Fcode>), which is safer than a hard flush as it doesn’t force regeneration of all rules unnecessarily.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Permissions Required\u003C\u002Fstrong>: Only users with \u003Ccode>manage_options\u003C\u002Fcode> capability can flush rules.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No Data Loss\u003C\u002Fstrong>: Flushing rules doesn’t delete any content or settings, it only regenerates the URL routing rules.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Immediate Effect\u003C\u002Fstrong>: Changes take effect immediately after flushing.\u003C\u002Fli>\n\u003C\u002Ful>\n","A simple admin tool for inspecting rewrite rules.",10000,454626,26,"2026-01-06T15:59:00.000Z","6.4",[20,95],"tools","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Frewrite-rules-inspector\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frewrite-rules-inspector.1.6.0.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":23,"num_ratings":108,"last_updated":109,"tested_up_to":110,"requires_at_least":111,"requires_php":112,"tags":113,"homepage":116,"download_link":117,"security_score":118,"vuln_count":79,"unpatched_count":13,"last_vuln_date":119,"fetched_at":25},"debug-bar-elasticpress","ElasticPress Debugging Add-On","3.1.1","10up","https:\u002F\u002Fprofiles.wordpress.org\u002F10up\u002F","\u003Cp>Allows you to examine every ElasticPress query running on any given request by adding an \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Felasticpress\" rel=\"ugc\">ElasticPress\u003C\u002Fa> panel to \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa> and\u002For \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> plugins.\u003C\u002Fp>\n\u003Cp>Alternatively, go to ElasticPress > Query Log and set it to record ElasticPress queries.\u003C\u002Fp>\n\u003Ch4>Requirements:\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Felasticpress\" rel=\"ugc\">ElasticPress 4.4.0+\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar 1.0+\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>PHP 7.0+\u003C\u002Fli>\n\u003C\u002Ful>\n","Extends the Query Monitor and Debug Bar plugins for ElasticPress queries.",900,8476266,2,"2024-12-11T17:31:00.000Z","6.7.5","5.6","7.0",[51,19,114,115],"elasticpress","elasticsearch","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar-elasticpress","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-elasticpress.3.1.1.zip",91,"2022-08-16 00:00:00",{"slug":121,"name":122,"version":123,"author":124,"author_profile":125,"description":126,"short_description":127,"active_installs":128,"downloaded":129,"rating":23,"num_ratings":29,"last_updated":130,"tested_up_to":70,"requires_at_least":71,"requires_php":72,"tags":131,"homepage":133,"download_link":134,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"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,"2025-12-01T22:51:00.000Z",[51,19,132,74],"debugbar","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fblackbar","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblackbar.4.1.4.zip",{"attackSurface":136,"codeSignals":153,"taintFlows":160,"riskAssessment":161,"analyzedAt":164},{"hooks":137,"ajaxHandlers":149,"restRoutes":150,"shortcodes":151,"cronEvents":152,"entryPointCount":13,"unprotectedCount":13},[138,144],{"type":139,"name":140,"callback":141,"file":142,"line":143},"filter","debug_bar_panels","debug_bar_rewrite_rules_panel","debug-bar-rewrite-rules.php",13,{"type":145,"name":146,"callback":147,"file":142,"line":148},"action","debug_bar_enqueue_scripts","debug_bar_rewrite_rules_scripts",22,[],[],[],[],{"dangerousFunctions":154,"sqlUsage":155,"outputEscaping":157,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":159},[],{"prepared":13,"raw":13,"locations":156},[],{"escaped":13,"rawEcho":13,"locations":158},[],[],[],{"summary":162,"deductions":163},"The \"fg-debug-bar-rewrite-rules\" plugin version 1.1.3 demonstrates an excellent security posture based on the provided static analysis.  The absence of any identified entry points, such as AJAX handlers, REST API routes, shortcodes, or cron events, significantly reduces the potential attack surface.  Furthermore, the code analysis reveals a clean codebase with no dangerous functions, all SQL queries utilizing prepared statements, and complete output escaping.  The lack of file operations, external HTTP requests, and the absence of non-critical security checks like nonce and capability checks on entry points (due to their non-existence) also contribute to this strong security profile. The vulnerability history is equally clean, with no known CVEs or past issues, which suggests a history of diligent security practices by the developers.  Overall, this plugin appears to be exceptionally well-secured, with no discernible security weaknesses based on the static analysis and vulnerability history provided.",[],"2026-03-16T22:02:15.816Z",{"wat":166,"direct":173},{"assetPaths":167,"generatorPatterns":169,"scriptPaths":170,"versionParams":171},[168],"\u002Fwp-content\u002Fplugins\u002Ffg-debug-bar-rewrite-rules\u002Fcss\u002Fdebug-bar-rewrite-rules.css",[],[],[172],"fg-debug-bar-rewrite-rules\u002Fcss\u002Fdebug-bar-rewrite-rules.css?ver=",{"cssClasses":174,"htmlComments":175,"htmlAttributes":176,"restEndpoints":177,"jsGlobals":178,"shortcodeOutput":179},[],[],[],[],[],[]]