[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fB9qTxJtv1i1XnFIQGSjChshi4ZpTscYlSLZOFBJjQOE":3,"$fqFH6fjnX5xS_KTiZ5W43-ljAi6CX42Tbei3_haxHY-g":229,"$fclmQz6sj-KfZKBIhImnA_KA5Q7ycoWSXSKsS3sQeMD8":233},{"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":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"discovery_status":31,"vulnerabilities":32,"developer":33,"crawl_stats":29,"alternatives":41,"analysis":139,"fingerprints":211},"debug-bar-rewrite-rules","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,54673,100,5,"2024-07-06T08:11:00.000Z","6.5.8","3.4","",[20,21,22,23,24],"debug","debug-bar","permalinks","rewrite-rules","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,0,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":34,"display_name":7,"profile_url":8,"plugin_count":35,"total_installs":36,"avg_security_score":37,"avg_patch_time_days":38,"trust_score":39,"computed_at":40},"butuzov",2,900,89,30,86,"2026-05-19T20:03:26.763Z",[42,60,76,100,119],{"slug":43,"name":44,"version":45,"author":46,"author_profile":47,"description":48,"short_description":49,"active_installs":50,"downloaded":51,"rating":13,"num_ratings":35,"last_updated":52,"tested_up_to":53,"requires_at_least":54,"requires_php":18,"tags":55,"homepage":57,"download_link":58,"security_score":59,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"rewrite-testing","Rewrite Rule Testing","0.1.1","Matthew Boynes","https:\u002F\u002Fprofiles.wordpress.org\u002Fmboynes\u002F","\u003Cp>This plugin provides a simple interface for testing your custom rewrite rules.\u003C\u002Fp>\n\u003Cp>The purpose of this plugin is to be able to test your \u003Cem>own\u003C\u002Fem> rewrite rules, so\u003Cbr \u002F>\nyou’re probably most interested in knowing how to do that, right? The plugin\u003Cbr \u002F>\nprovides a filter, \u003Ccode>rewrite_testing_tests\u003C\u002Fcode> to add your own tests. That filter\u003Cbr \u002F>\npasses an associative array of name => tests. The tests array is an associative\u003Cbr \u002F>\narray of URI => expected match. In the outer array, the “name” is arbitrary and\u003Cbr \u002F>\nfor your own reference. In the inner array, the “URI” is the path you want to\u003Cbr \u002F>\ntest, and the “expected match” is what WordPress should find as a rewrite\u003Cbr \u002F>\nmatch.\u003C\u002Fp>\n\u003Cp>Enough chit-chat, here’s an example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function my_rewrite_tests( $tests ) {\n  return array(\n    'Events' => array(\n      '\u002Fevent\u002Fsuper-bowl\u002F' => 'index.php?event=$matches[1]',\n      '\u002Fevent\u002Fsuper-bowl\u002Fpage\u002F2\u002F' => 'index.php?event=$matches[1]&paged=$matches[2]'\n    )\n  );\n}\nadd_filter( 'rewrite_testing_tests', 'my_rewrite_tests' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can see the \u003Ccode>test_cases()\u003C\u002Fcode> method for a full suite of tests for the “Day\u003Cbr \u002F>\nand Name” permalink structure. It’s not necessary to leave these in (in fact,\u003Cbr \u002F>\nthe above demo would wipe them out), unless you want to make sure that your\u003Cbr \u002F>\ncustom rewrites aren’t affecting core rewrites. If you aren’t using “Day and\u003Cbr \u002F>\nName” permalinks, you’ll need to adjust the tests to fit your permalink\u003Cbr \u002F>\nstructure.\u003C\u002Fp>\n\u003Ch3>Todo\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Add a debug bar extension which reads a transient; the transient would be\u003Cbr \u002F>\nupdated whenever rewrite rules are flushed. The debug bar extension would\u003Cbr \u002F>\nshow pass\u002Ffail status and link directly to the settings page.\u003C\u002Fli>\n\u003Cli>Add tests for other permalink structures?\u003C\u002Fli>\n\u003Cli>Add a way to run this as part of phpunit\u003C\u002Fli>\n\u003C\u002Ful>\n","Unit test your rewrite rules from the WordPress Admin.",300,29937,"2014-05-20T16:53:00.000Z","3.9.40","3.9",[22,23,24,56],"tests","https:\u002F\u002Fgithub.com\u002Falleyinteractive\u002Frewrite-testing","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frewrite-testing.0.1.1.zip",85,{"slug":61,"name":5,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":28,"num_ratings":28,"last_updated":69,"tested_up_to":70,"requires_at_least":71,"requires_php":72,"tags":73,"homepage":74,"download_link":75,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"fg-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,9831,"2025-04-29T08:47:00.000Z","6.8.5","3.1","5.3",[21,23],"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",{"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":90,"requires_php":91,"tags":92,"homepage":95,"download_link":96,"security_score":97,"vuln_count":98,"unpatched_count":28,"last_vuln_date":99,"fetched_at":30},"query-monitor","Query Monitor","4.0.6","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>Thanks\u003C\u002Fh3>\n\u003Cp>The time that I spend maintaining this plugin and others is in part sponsored by:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fautomattic.com\u002F\" rel=\"nofollow ugc\">Automattic\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fservmask.com\u002F\" rel=\"nofollow ugc\">ServMask\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwp-staging.com\u002F\" rel=\"nofollow ugc\">WP Staging\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsponsors\u002Fjohnbillion\" rel=\"nofollow ugc\">All my kind sponsors on GitHub\u003C\u002Fa>\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,19993201,98,465,"2026-04-11T11:53:00.000Z","6.9.4","6.1","7.4",[20,21,93,94,77],"development","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.4.0.6.zip",97,1,"2026-03-30 23:21:22",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":108,"downloaded":109,"rating":13,"num_ratings":110,"last_updated":111,"tested_up_to":112,"requires_at_least":113,"requires_php":18,"tags":114,"homepage":117,"download_link":118,"security_score":59,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"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,74113,26,"2011-05-12T17:49:00.000Z","3.2.1","3.0",[20,93,115,22,116],"mod_rewrite","rewrite","http:\u002F\u002Fwordpress.stackexchange.com\u002Fq\u002F3606\u002F8","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmonkeyman-rewrite-analyzer.1.0.zip",{"slug":120,"name":121,"version":122,"author":123,"author_profile":124,"description":125,"short_description":126,"active_installs":36,"downloaded":127,"rating":13,"num_ratings":35,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":131,"tags":132,"homepage":135,"download_link":136,"security_score":137,"vuln_count":98,"unpatched_count":28,"last_vuln_date":138,"fetched_at":30},"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.",8670964,"2024-12-11T17:31:00.000Z","6.7.5","5.6","7.0",[20,21,133,134],"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",{"attackSurface":140,"codeSignals":181,"taintFlows":204,"riskAssessment":205,"analyzedAt":210},{"hooks":141,"ajaxHandlers":171,"restRoutes":178,"shortcodes":179,"cronEvents":180,"entryPointCount":98,"unprotectedCount":28},[142,148,151,156,161,164,167,169],{"type":143,"name":144,"callback":145,"file":146,"line":147},"action","wp_enqueue_scripts","assets","debug-bar.php",38,{"type":143,"name":149,"callback":145,"file":146,"line":150},"admin_enqueue_scripts",39,{"type":143,"name":152,"callback":153,"file":154,"line":155},"generate_rewrite_rules","track_generate_rewrite_rules","rewrite-rules.php",134,{"type":157,"name":158,"callback":159,"file":154,"line":160},"filter","debug_bar_panels","debug_bar_panel",137,{"type":143,"name":162,"callback":162,"file":154,"line":163},"init",140,{"type":143,"name":165,"callback":165,"file":154,"line":166},"admin_menu",154,{"type":143,"name":149,"callback":145,"file":154,"line":168},155,{"type":143,"name":144,"callback":145,"file":154,"line":170},279,[172],{"action":173,"nopriv":174,"callback":175,"hasNonce":176,"hasCapCheck":176,"file":154,"line":177},"debug_bar_rewrite_rules",false,"ajax",true,159,[],[],[],{"dangerousFunctions":182,"sqlUsage":183,"outputEscaping":185,"fileOperations":28,"externalRequests":28,"nonceChecks":98,"capabilityChecks":98,"bundledLibraries":203},[],{"prepared":28,"raw":28,"locations":184},[],{"escaped":186,"rawEcho":187,"locations":188},14,10,[189,192,193,194,196,197,199,200,201,202],{"file":146,"line":190,"context":191},77,"raw output",{"file":146,"line":190,"context":191},{"file":146,"line":190,"context":191},{"file":154,"line":195,"context":191},218,{"file":154,"line":195,"context":191},{"file":154,"line":198,"context":191},226,{"file":154,"line":198,"context":191},{"file":154,"line":198,"context":191},{"file":154,"line":198,"context":191},{"file":154,"line":198,"context":191},[],[],{"summary":206,"deductions":207},"The 'debug-bar-rewrite-rules' plugin v0.6.5 exhibits a generally strong security posture based on the provided static analysis. It demonstrates good practices by not utilizing dangerous functions, performing all SQL queries using prepared statements, and including nonce and capability checks for its sole AJAX entry point. The absence of file operations and external HTTP requests further reduces the attack surface.  However, a significant concern is the output escaping, where only 58% of the 24 total outputs are properly escaped. This leaves room for potential cross-site scripting (XSS) vulnerabilities if malicious input is ever processed and displayed without adequate sanitization. The plugin also has no recorded vulnerability history, which is a positive indicator, but this should not be solely relied upon, especially given the output escaping issues.\n\nDespite the lack of critical or high-severity issues found in taint analysis and vulnerability history, the incomplete output escaping is a notable weakness. While the attack surface is minimal and protected, the potential for stored or reflected XSS through unescaped output on the admin side is a tangible risk. Therefore, while the plugin is relatively secure due to its other robust security implementations, developers should prioritize addressing the output escaping to achieve a truly secure state.",[208],{"reason":209,"points":14},"Incomplete output escaping","2026-03-16T19:16:23.648Z",{"wat":212,"direct":221},{"assetPaths":213,"generatorPatterns":216,"scriptPaths":217,"versionParams":218},[214,215],"\u002Fwp-content\u002Fplugins\u002Fdebug-bar-rewrite-rules\u002Fassets\u002Fdebug-bar-rewrite-rules.css","\u002Fwp-content\u002Fplugins\u002Fdebug-bar-rewrite-rules\u002Fassets\u002Fdebug-bar-rewrite-rules.js",[],[215],[219,220],"debug-bar-rewrite-rules\u002Fassets\u002Fdebug-bar-rewrite-rules.css?ver=","debug-bar-rewrite-rules\u002Fassets\u002Fdebug-bar-rewrite-rules.js?ver=",{"cssClasses":222,"htmlComments":224,"htmlAttributes":225,"restEndpoints":226,"jsGlobals":227,"shortcodeOutput":228},[223],"debug-bar-rewrites-urls",[],[],[],[],[],{"error":176,"url":230,"statusCode":231,"statusMessage":232,"message":232},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fdebug-bar-rewrite-rules\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":187,"versions":234},[235,240,247,254,261,268,275,282,289,296],{"version":6,"download_url":26,"svn_tag_url":236,"released_at":29,"has_diff":174,"diff_files_changed":237,"diff_lines":29,"trac_diff_url":238,"vulnerabilities":239,"is_current":176},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.6.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.4&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.5",[],{"version":241,"download_url":242,"svn_tag_url":243,"released_at":29,"has_diff":174,"diff_files_changed":244,"diff_lines":29,"trac_diff_url":245,"vulnerabilities":246,"is_current":174},"0.6.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.6.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.6.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.3&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.4",[],{"version":248,"download_url":249,"svn_tag_url":250,"released_at":29,"has_diff":174,"diff_files_changed":251,"diff_lines":29,"trac_diff_url":252,"vulnerabilities":253,"is_current":174},"0.6.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.6.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.6.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.2&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.3",[],{"version":255,"download_url":256,"svn_tag_url":257,"released_at":29,"has_diff":174,"diff_files_changed":258,"diff_lines":29,"trac_diff_url":259,"vulnerabilities":260,"is_current":174},"0.6.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.6.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.6.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.1&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.2",[],{"version":262,"download_url":263,"svn_tag_url":264,"released_at":29,"has_diff":174,"diff_files_changed":265,"diff_lines":29,"trac_diff_url":266,"vulnerabilities":267,"is_current":174},"0.6.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.6.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.6.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6.1",[],{"version":269,"download_url":270,"svn_tag_url":271,"released_at":29,"has_diff":174,"diff_files_changed":272,"diff_lines":29,"trac_diff_url":273,"vulnerabilities":274,"is_current":174},"0.6","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.6.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.6\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.5&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.6",[],{"version":276,"download_url":277,"svn_tag_url":278,"released_at":29,"has_diff":174,"diff_files_changed":279,"diff_lines":29,"trac_diff_url":280,"vulnerabilities":281,"is_current":174},"0.5","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.5.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.4&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.5",[],{"version":283,"download_url":284,"svn_tag_url":285,"released_at":29,"has_diff":174,"diff_files_changed":286,"diff_lines":29,"trac_diff_url":287,"vulnerabilities":288,"is_current":174},"0.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.3&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.4",[],{"version":290,"download_url":291,"svn_tag_url":292,"released_at":29,"has_diff":174,"diff_files_changed":293,"diff_lines":29,"trac_diff_url":294,"vulnerabilities":295,"is_current":174},"0.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.2&new_path=%2Fdebug-bar-rewrite-rules%2Ftags%2F0.3",[],{"version":297,"download_url":298,"svn_tag_url":299,"released_at":29,"has_diff":174,"diff_files_changed":300,"diff_lines":29,"trac_diff_url":29,"vulnerabilities":301,"is_current":174},"0.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-rewrite-rules.0.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-bar-rewrite-rules\u002Ftags\u002F0.2\u002F",[],[]]