[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fOltpHOTl3H4VakaEOLZIlsNFRKmJ0wJ1eLAroPUefLQ":3,"$fMC8cxJb-Um90_x8Xy6N-D0kjVFJFv3lHgEQE6C3CTgI":217,"$fTP7wqVa8qLMgR_s-wlCGLw4HWj3c_hQBuVh_iHoZNYY":221},{"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":18,"download_link":22,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26,"discovery_status":27,"vulnerabilities":28,"developer":29,"crawl_stats":25,"alternatives":36,"analysis":134,"fingerprints":203},"taylors-debug-toggle","Taylor's Debug Toggle","1.0","taylor.mitchellstjoseph","https:\u002F\u002Fprofiles.wordpress.org\u002Ftaylormitchellstjoseph\u002F","\u003Cp>This plugin adds an option in the admin toolbar to toggle WP_DEBUG on\u002Foff.\u003C\u002Fp>\n\u003Cp>wp-config.php must be writable by the server and code must be in the default format\u002Fspacing – \u003Cstrong>define(‘WP_DEBUG’, false);\u003C\u002Fstrong>\u003C\u002Fp>\n","Toggle WP_DEBUG on\u002Foff through the admin toolbar",10,1383,20,1,"2015-03-08T15:26:00.000Z","4.1.42","3","",[20,21],"debug","wp_debug","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftaylors-debug-toggle.1.0.zip",85,0,null,"2026-03-15T15:16:48.613Z","no_bundle",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":23,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"taylormitchellstjoseph",3,2410,30,84,"2026-05-20T07:42:12.737Z",[37,59,80,101,117],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":11,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":18,"tags":51,"homepage":56,"download_link":57,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":58},"log-deprecated-notices","Log Deprecated Notices","0.4.1","Andrew Nacin","https:\u002F\u002Fprofiles.wordpress.org\u002Fnacin\u002F","\u003Cp>This plugin logs the usage of deprecated files, functions, and function arguments. It identifies where the deprecated functionality is being used and offers the alternative if available.\u003C\u002Fp>\n\u003Cp>This is a plugin for developers. WP_DEBUG is not needed, though its general usage is strongly recommended. Deprecated notices normally exposed by WP_DEBUG will be logged instead.\u003C\u002Fp>\n\u003Cp>This plugin also logs incorrect function usage, which WordPress started reporting in 3.1.\u003C\u002Fp>\n\u003Cp>Please report any bugs to plugins in a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Flog-deprecated-notices\" rel=\"ugc\">support thread\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>This is young software. It works, but there’s a lot left on the todo (check out the Other Notes tab). Have an idea? Let me know.\u003C\u002Fp>\n\u003Ch3>Ideas\u003C\u002Fh3>\n\u003Cp>These are the various things on the @todo:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Plugin identification. Also, an unobstrusive note on plugins page next to said plugins.\u003C\u002Fli>\n\u003Cli>Perhaps the ability to auto-purge the log.\u003C\u002Fli>\n\u003Cli>Ability to filter on file or plugin in which the deprecated functionality is used.\u003C\u002Fli>\n\u003Cli>Offer some kind of better multisite support.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Want to add something here? I’m all ears. plugins at \u003Ca href=\"http:\u002F\u002Fandrewnacin.com\u002F\" rel=\"nofollow ugc\">andrewnacin.com\u003C\u002Fa> or @\u003Ca href=\"http:\u002F\u002Ftwitter.com\u002Fnacin\" rel=\"nofollow ugc\">nacin\u003C\u002Fa> on Twitter.\u003C\u002Fp>\n\u003Cp>I will prioritize these tasks based on feedback, so let me know what you’d like to see.\u003C\u002Fp>\n","Logs the usage of deprecated files, functions, and function arguments, and identifies where the deprecated functionality is being used.",1000,166286,100,"2021-06-25T14:17:00.000Z","5.8.13","3.0",[52,53,54,55,21],"admin","deprecated","e_notice","logging","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Flog-deprecated-notices\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flog-deprecated-notices.0.4.1.zip","2026-04-16T10:56:18.058Z",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":47,"downloaded":67,"rating":68,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":73,"tags":74,"homepage":18,"download_link":79,"security_score":47,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":58},"conflict-finder-wp-fix-it","Conflict Finder","7.2","WP Fix It - WordPress Experts","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpfixit\u002F","\u003Cp>Conflict Finder is a comprehensive troubleshooting plugin designed for WordPress administrators, developers, and support professionals who need to identify the root cause of site issues.\u003C\u002Fp>\n\u003Cp>From a single interface, Conflict Finder allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable and manage WP_DEBUG without manually editing files\u003C\u002Fli>\n\u003Cli>View, download, and clear the WordPress debug log\u003C\u002Fli>\n\u003Cli>Temporarily disable plugins to identify conflicts\u003C\u002Fli>\n\u003Cli>Switch themes to test theme-related issues\u003C\u002Fli>\n\u003Cli>Test WordPress email delivery using \u003Ccode>wp_mail()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Important:\u003C\u002Fstrong>\u003Cbr \u002F>\nConflict Finder \u003Cstrong>does temporarily affect site behavior\u003C\u002Fstrong> while troubleshooting is active. This may include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disabled plugins\u003C\u002Fli>\n\u003Cli>A different active theme\u003C\u002Fli>\n\u003Cli>Debug notices or errors being displayed\u003C\u002Fli>\n\u003Cli>Changes visible to logged-out visitors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For this reason, troubleshooting should be performed during maintenance windows or on staging sites whenever possible.\u003C\u002Fp>\n\u003Cp>Conflict Finder automatically tracks your original configuration and allows you to restore plugins, themes, and debugging settings once testing is complete.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Troubleshooting Dashboard\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Central overview of debugging and conflict states\u003C\u002Fli>\n\u003Cli>Environment snapshot including WordPress, PHP, memory, and server software\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>WP_DEBUG Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable or disable WP_DEBUG with a single switch\u003C\u002Fli>\n\u003Cli>Control error display and logging behavior\u003C\u002Fli>\n\u003Cli>Load unminified scripts for debugging\u003C\u002Fli>\n\u003Cli>View, download, or clear \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Safely updates \u003Ccode>wp-config.php\u003C\u002Fcode> as needed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Plugin Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily deactivate all active plugins\u003C\u002Fli>\n\u003Cli>Save and restore original plugin states\u003C\u002Fli>\n\u003Cli>Activate plugins one at a time to identify conflicts\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Theme Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily switch to another installed theme\u003C\u002Fli>\n\u003Cli>Identify theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Restore the original theme instantly\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Email Delivery Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Send a real test email using WordPress mail\u003C\u002Fli>\n\u003Cli>Confirm whether the server can successfully send email\u003C\u002Fli>\n\u003Cli>Helps identify SMTP or hosting mail issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>When to Use Conflict Finder\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Diagnosing white screens or fatal errors\u003C\u002Fli>\n\u003Cli>Identifying plugin conflicts\u003C\u002Fli>\n\u003Cli>Testing theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Investigating PHP notices or warnings\u003C\u002Fli>\n\u003Cli>Verifying WordPress email delivery\u003C\u002Fli>\n\u003Cli>Support and development workflows\u003C\u002Fli>\n\u003C\u002Ful>\n","Conflict Finder is a WordPress troubleshooting toolkit that helps diagnose plugin conflicts, theme issues, debugging errors, and email delivery proble …",8971,90,4,"2026-01-27T14:26:00.000Z","6.9.4","4.9","5.6",[75,76,77,78,21],"debug-log","plugin-conflict","theme-conflict","troubleshooting","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fconflict-finder-wp-fix-it.7.2.zip",{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":47,"downloaded":88,"rating":89,"num_ratings":90,"last_updated":91,"tested_up_to":92,"requires_at_least":93,"requires_php":18,"tags":94,"homepage":97,"download_link":98,"security_score":99,"vuln_count":14,"unpatched_count":24,"last_vuln_date":100,"fetched_at":58},"enable-wp-debug-from-admin-dashboard","Debug Bar – Enable WP_DEBUG from admin dashboard","1.93","Puvox Software","https:\u002F\u002Fprofiles.wordpress.org\u002Fpuvoxsoftware\u002F","\u003Ch4>[ ✅ 𝐒𝐄𝐂𝐔𝐑𝐄 𝐏𝐋𝐔𝐆𝐈𝐍𝐒 b𝓎 𝒫𝓊𝓋𝑜𝓍] :\u003C\u002Fh4>\n\u003Cblockquote>\n\u003Cp>• Revised for security to be reliable and free of vulnerability holes.\u003Cbr \u002F>\n  • Efficient, not to add any extra load\u002Fslowness to site.\u003Cbr \u002F>\n  • Don’t collect private data.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Plugin Description\u003C\u002Fh4>\n\u003Cp>READ DESCRIPTION BEFORE INSTALLING!\u003Cbr \u002F>\nEasily enable\u002Fdisable WP_DEBUG with one single click from Admin Toolbar. What’s more, this plugin is failsafe & clever – in case of errors, it automatically exits the WP_DEBUG mode, thus, you won’t face any problems.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Works with \u003Ccode>Debug Bar\u003C\u002Fcode> plugin. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>NOTE\u003C\u002Fh4>\n\u003Cp>Plugin modifies \u003Ccode>wp-config.php\u003C\u002Fcode>. However, on some sites, this might cause some conflict with existing wp-config, causing to interfere the page-load. So, use at your own responsibility. If unsure, use on test site.\u003C\u002Fp>\n\u003Ch4>Available Options\u003C\u002Fh4>\n\u003Cp>See all available options and their description on plugin’s settings page.\u003C\u002Fp>\n","[ ✅ 𝐒𝐄𝐂𝐔𝐑𝐄 𝐏𝐋𝐔𝐆𝐈𝐍𝐒 b𝓎 𝒫𝓊𝓋𝑜𝓍]  You can easily enable WP_DEBUG using a toolbar button. READ DESCRIPTION!",15538,36,5,"2024-10-30T11:24:00.000Z","6.5.8","6.0",[52,20,95,96,21],"enable","wp","https:\u002F\u002Fpuvox.software\u002Fsoftware\u002Fwordpress-plugins\u002F?plugin=enable-wp-debug-from-admin-dashboard","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fenable-wp-debug-from-admin-dashboard.zip",92,"2022-08-01 00:00:00",{"slug":102,"name":103,"version":104,"author":105,"author_profile":106,"description":107,"short_description":108,"active_installs":68,"downloaded":109,"rating":24,"num_ratings":24,"last_updated":110,"tested_up_to":71,"requires_at_least":111,"requires_php":73,"tags":112,"homepage":115,"download_link":116,"security_score":47,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":58},"debug-status-display-footer","Debug Status display","1.1.0","apasionados","https:\u002F\u002Fprofiles.wordpress.org\u002Fapasionados\u002F","\u003Cp>This plugin displays if WP_DEBUG is active (\u003Ccode>define('WP_DEBUG', true);\u003C\u002Fcode> in the wp-config.php configuration file) in the admin footer. If WP_DEBUG is not active it shows WP_DEBUG strike through in the admin footer and if it’s active it show WP_DEBUG in orange color. This helps to identify in one second if WP_DEBUG is active on a site or not.\u003C\u002Fp>\n\u003Cp>It can be used alone or together with the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fserver-ip-memory-usage\u002F\" rel=\"ugc\">“Server IP & Memory Usage Display”\u003C\u002Fa> and\u002For the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdisplay-mysql-version\u002F\" rel=\"ugc\">“Display MySql version”\u003C\u002Fa> plugin.\u003C\u002Fp>\n\u003Ch4>What can I do with this plugin?\u003C\u002Fh4>\n\u003Cp>This plugin displays if WP_DEBUG is active (\u003Ccode>define('WP_DEBUG', true);\u003C\u002Fcode> in the wp-config.php configuration file) in the admin footer. If WP_DEBUG is not active it shows WP_DEBUG strike through. If it’s active it show WP_DEBUG in orange color.\u003C\u002Fp>\n\u003Ch4>What ideas is this plugin based on?\u003C\u002Fh4>\n\u003Cp>We have had some requirements to add the information if WP_DEBUG is active and some other information to the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fserver-ip-memory-usage\u002F\" rel=\"ugc\">Server IP & Memory Usage Display\u003C\u002Fa> plugin. As we want to keep this plugin as simple as possible and without settings page, we decided to create this small plugin, which can be used alone or together with the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fserver-ip-memory-usage\u002F\" rel=\"ugc\">“Server IP & Memory Usage Display”\u003C\u002Fa> and\u002For the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdisplay-mysql-version\u002F\" rel=\"ugc\">“Display MySql version”\u003C\u002Fa> plugin.\u003C\u002Fp>\n\u003Ch4>System requirements\u003C\u002Fh4>\n\u003Cp>PHP version 5.6 or greater.\u003C\u002Fp>\n\u003Ch4>Debug status display Plugin in your Language!\u003C\u002Fh4>\n\u003Cp>This first release is avaliable in English and Spanish. In the “lang” folder we have included the necessary files to translate this plugin.\u003C\u002Fp>\n\u003Cp>If you would like the plugin in your language and you’re good at translating, please drop us a line at \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-debug-status-display-home\" rel=\"nofollow ugc\">Contact us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cp>You can access the description of the plugin in Spanish at: \u003Ca href=\"https:\u002F\u002Fapasionados.es\u002Fblog\u002Fmostrar-aviso-si-wordpress-esta-en-modo-debug-wordpress-plugin-7758\u002F\" rel=\"nofollow ugc\">Debug status display en español\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Contact\u003C\u002Fh3>\n\u003Cp>For further information please send us an \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-debug-status-display-contact\" rel=\"nofollow ugc\">email\u003C\u002Fa>.\u003C\u002Fp>\n","Displays if WP_DEBUG is active in the admin footer. This plugin can be used alone or together with the \"Server IP & Memory Usage Display\" plugin.",2667,"2026-01-27T14:04:00.000Z","3.0.1",[20,113,114,21],"info","server","http:\u002F\u002Fapasionados.es\u002F#utm_source=wpadmin&utm_medium=plugin&utm_campaign=debug-status-display-plugin","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-status-display-footer.1.1.0.zip",{"slug":118,"name":119,"version":6,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":124,"downloaded":125,"rating":126,"num_ratings":14,"last_updated":127,"tested_up_to":128,"requires_at_least":50,"requires_php":18,"tags":129,"homepage":18,"download_link":133,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":58},"disable-deprecated-warnings","Disable Deprecated Warnings","tamlyn","https:\u002F\u002Fprofiles.wordpress.org\u002Ftamlyn\u002F","\u003Cp>As a theme developer, you want to have WP_DEBUG enabled but you’re not interested in the deprecated warnings created by other plugins. Use this plugin to disable these messages while still displaying other errors, warnings and notices.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Foutlandishideas.co.uk\u002Fblog\u002F2012\u002F06\u002Fhide-deprecated-errors-in-wordpress\u002F\" rel=\"nofollow ugc\">Plugin by Outlandish Ideas\u003C\u002Fa>\u003C\u002Fp>\n","Prevents plugins from showing deprecated errors in the WordPress admin.",60,3366,80,"2012-06-22T16:12:00.000Z","3.4.2",[20,130,53,131,132],"depracated","errors","wp-debug","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-deprecated-warnings.zip",{"attackSurface":135,"codeSignals":155,"taintFlows":163,"riskAssessment":192,"analyzedAt":202},{"hooks":136,"ajaxHandlers":151,"restRoutes":152,"shortcodes":153,"cronEvents":154,"entryPointCount":24,"unprotectedCount":24},[137,144,148],{"type":138,"name":139,"callback":140,"priority":141,"file":142,"line":143},"action","init","tdt_toggle",99,"plugin.php",21,{"type":138,"name":145,"callback":146,"priority":141,"file":142,"line":147},"admin_bar_menu","tdt_toggle_links",22,{"type":138,"name":139,"callback":149,"file":142,"line":150},"tdt_init",77,[],[],[],[],{"dangerousFunctions":156,"sqlUsage":157,"outputEscaping":159,"fileOperations":161,"externalRequests":24,"nonceChecks":24,"capabilityChecks":14,"bundledLibraries":162},[],{"prepared":24,"raw":24,"locations":158},[],{"escaped":24,"rawEcho":24,"locations":160},[],2,[],[164,182],{"entryPoint":165,"graph":166,"unsanitizedCount":14,"severity":181},"tdt_toggle (plugin.php:58)",{"nodes":167,"edges":178},[168,173],{"id":169,"type":170,"label":171,"file":142,"line":172},"n0","source","$_SERVER['REQUEST_URI']",67,{"id":174,"type":175,"label":176,"file":142,"line":172,"wp_function":177},"n1","sink","wp_redirect() [Open Redirect]","wp_redirect",[179],{"from":169,"to":174,"sanitized":180},false,"medium",{"entryPoint":183,"graph":184,"unsanitizedCount":24,"severity":191},"\u003Cplugin> (plugin.php:0)",{"nodes":185,"edges":188},[186,187],{"id":169,"type":170,"label":171,"file":142,"line":172},{"id":174,"type":175,"label":176,"file":142,"line":172,"wp_function":177},[189],{"from":169,"to":174,"sanitized":190},true,"low",{"summary":193,"deductions":194},"The \"taylors-debug-toggle\" plugin v1.0 exhibits a generally strong security posture based on the provided static analysis.  The plugin demonstrates good practices by avoiding dangerous functions, using prepared statements for all SQL queries, and properly escaping all output.  The complete absence of known CVEs and recorded vulnerability history further suggests a mature and secure development process.  The plugin also has a negligible attack surface with no exposed entry points like AJAX handlers, REST API routes, or shortcodes that are not protected by authentication or permission checks.\n\nHowever, the static analysis does highlight a potential concern. One taint flow was found with an unsanitized path. While no critical or high severity taint issues were identified, and the plugin has a capability check, this specific flow warrants attention as it could potentially lead to unintended behavior or vulnerabilities if an attacker can manipulate the path input. The presence of file operations, even if not directly linked to a taint flow in this analysis, also represents a potential area for concern in broader security assessments. The lack of nonce checks, while not a direct critical finding in this isolated analysis, is a best practice that is missing.\n\nIn conclusion, \"taylors-debug-toggle\" v1.0 appears to be a securely developed plugin with a strong emphasis on preventing common web vulnerabilities. The limited attack surface and secure coding practices are significant strengths. The primary area for improvement lies in investigating and sanitizing the identified unsanitized path flow to eliminate any potential risk. The absence of any recorded vulnerabilities is a positive indicator, but vigilance regarding the taint flow and file operations is recommended for maintaining its secure status.",[195,198,200],{"reason":196,"points":197},"Flows with unsanitized paths",8,{"reason":199,"points":161},"File operations present",{"reason":201,"points":90},"Missing nonce checks","2026-03-17T00:44:29.518Z",{"wat":204,"direct":209},{"assetPaths":205,"generatorPatterns":206,"scriptPaths":207,"versionParams":208},[],[],[],[],{"cssClasses":210,"htmlComments":212,"htmlAttributes":213,"restEndpoints":214,"jsGlobals":215,"shortcodeOutput":216},[211],"tdt",[],[],[],[],[],{"error":190,"url":218,"statusCode":219,"statusMessage":220,"message":220},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Ftaylors-debug-toggle\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":24,"versions":222},[]]