[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fg9iUaOQWtj1-DsgjfXuwC55KV7m1vb0unf7pVhCQw8E":3,"$fXLLuRkjVDymGN2AHUniTG8x5Fzy7Y8rwVaHTN27-U98":177,"$fTsr50KAZJGlE7UupoVskDRawYAFwOmKXG8z6KMTEh3A":182},{"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":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":36,"analysis":135,"fingerprints":160},"debug-logger","Debug Logger","0.3.0","Andrew Woods","https:\u002F\u002Fprofiles.wordpress.org\u002Fawoods\u002F","\u003Cp>As PHP moves forward, so must WordPress. This plugin helps WordPress use the tools of modern PHP. Monolog — PHP’s most popular logging package — is a composer package. Since WordPress doesn’t currently have a universal way to support composer, this WordPress plugin is meant to start bridging the gap. This logger is \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fphp-fig\u002Ffig-standards\u002Fblob\u002Fmaster\u002Faccepted\u002FPSR-3-logger-interface.md\" rel=\"nofollow ugc\">PSR-3\u003C\u002Fa> compliant, a PHP standard which Monolog also uses.\u003C\u002Fp>\n\u003Ch3>Logging Levels\u003C\u002Fh3>\n\u003Cp>There are 8 logging levels available, \u003Ca href=\"https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc5424\" rel=\"nofollow ugc\">defined by RFC 5424\u003C\u002Fa>. The levels specified in\u003Cbr \u002F>\norder from the most severe to the least severe:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Emergency\u003C\u002Fstrong>: system is unusable\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Alert\u003C\u002Fstrong>: action must be taken immediately\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Critical\u003C\u002Fstrong>: critical conditions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Error\u003C\u002Fstrong>: error conditions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Warning\u003C\u002Fstrong>: warning conditions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Notice\u003C\u002Fstrong>: normal but significant condition\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Info\u003C\u002Fstrong>: informational messages\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug\u003C\u002Fstrong>: debug-level messages\u003C\u002Fli>\n\u003C\u002Ful>\n","Provide a PSR-3 compatible logger for WordPress core that writes to the debug.log",0,1012,"2021-05-03T20:02:00.000Z","5.7.15","5.7","7.4",[18,19,20,21,22],"debug","logging","logs","monolog","psr-3","https:\u002F\u002Fgithub.com\u002Fandrewwoods\u002Fwp-debug-logger","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-logger.0.3.0.zip",85,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"awoods",1,30,84,"2026-05-20T02:03:18.730Z",[37,56,73,91,116],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":11,"num_ratings":11,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":16,"tags":50,"homepage":53,"download_link":54,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"custom-logs","Custom Logs","1.1","Byron Jacobs","https:\u002F\u002Fprofiles.wordpress.org\u002Fheavyweightdigital\u002F","\u003Cp>Custom Logs is a powerful and user-friendly plugin designed to help WordPress developers and administrators manage debug logs efficiently. With a modern interface, it offers complete control over custom and WP_DEBUG logs, including custom directories, log levels, and real-time AJAX filtering.\u003C\u002Fp>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Custom Log Management\u003C\u002Fstrong>: Define custom log file names and directories within the uploads folder.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG Integration\u003C\u002Fstrong>: Capture and redirect WP_DEBUG logs to a custom file.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Log Levels\u003C\u002Fstrong>: Filter logs by severity (None, All, Errors, Warnings, Notices).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AJAX-Powered Log Viewer\u003C\u002Fstrong>: Dynamically filter log entries by file and type without page reloads.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Backup and Clear Logs\u003C\u002Fstrong>: Easily back up or clear logs with a single click.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Download Logs\u003C\u002Fstrong>: Download custom or WP_DEBUG logs directly from the admin panel.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sleek UI\u003C\u002Fstrong>: A modern, responsive design with uniform input heights for a polished experience.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This is the initial release (v1.0), providing a robust foundation for log management with advanced features like AJAX filtering built-in from the start.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Cstrong>Enable Logging\u003C\u002Fstrong>: Turn on custom logging and set a log level under “Custom Logging”.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Set Log Files\u003C\u002Fstrong>: Specify custom log file names and directories under “General” and “WP Debug Logging”.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>View Logs\u003C\u002Fstrong>: Use the Log Viewer to select a log file and filter by type (e.g., Errors, Info) with real-time AJAX updates.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Manage Logs\u003C\u002Fstrong>: Test, clear, back up, or delete logs from the “Management” section.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Download Logs\u003C\u002Fstrong>: Use the “Downloads” section to save logs locally.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>To log custom messages, use the \u003Ccode>custom_logs()\u003C\u002Fcode> function in your code:\u003Cbr \u002F>\n    `php\u003Cbr \u002F>\ncustomdebug_log(“This is a test message”, “info”);\u003C\u002Fp>\n","A sleek, modern plugin to manage WordPress debug logs with custom directories, levels, and advanced AJAX filtering.",10,475,"2025-05-27T11:47:00.000Z","6.8.5","4.8",[51,18,19,20,52],"admin-tools","wordpress-debug","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-logs.zip",100,{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":11,"downloaded":64,"rating":11,"num_ratings":11,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":16,"tags":68,"homepage":71,"download_link":72,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"msbd-logs","MSBD Logs","1.0.2","Shah Alom","https:\u002F\u002Fprofiles.wordpress.org\u002Fshahalom\u002F","\u003Ch3>MSBD Logs is a WordPress plugin that allows developers to review and manage log files generated by plugins and themes.\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>MSBD Logs\u003C\u002Fstrong> is a lightweight logging helper for WordPress plugin and theme developers.\u003C\u002Fp>\n\u003Cp>It provides a simple PHP API to write log messages and an admin interface to view, filter, and manage log files stored in the WordPress uploads directory.\u003C\u002Fp>\n\u003Cp>The plugin is designed to be minimal, dependency-free, and safe for use on production sites.\u003C\u002Fp>\n\u003Ch3>🎉 Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Simple logging function for developers\u003C\u002Fli>\n\u003Cli>Daily rotating log files\u003C\u002Fli>\n\u003Cli>Separate log types: \u003Ccode>debug\u003C\u002Fcode> and \u003Ccode>attention\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Debug logging can be enabled or disabled from admin\u003C\u002Fli>\n\u003Cli>Admin UI to view, and filter log files\u003C\u002Fli>\n\u003Cli>Secure file handling (capability and nonce protected)\u003C\u002Fli>\n\u003Cli>No database tables or external services\u003C\u002Fli>\n\u003Cli>Translation-ready\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Log Storage Location\u003C\u002Fh3>\n\u003Cp>All log files are stored in: \u003Ccode>wp-content\u002Fuploads\u002Flogs\u002F\u003C\u002Fcode>. \u003Ccode>logs\u003C\u002Fcode> folder is created in \u003Ccode>wp-content\u002Fuploads\u002F\u003C\u002Fcode> on activating the plugin. An \u003Ccode>index.html\u003C\u002Fcode> file is automatically created to prevent directory browsing.\u003C\u002Fp>\n\u003Ch3>Developer Usage\u003C\u002Fh3>\n\u003Cp>Use the following helper function anywhere in your plugin or theme code:\u003Cbr \u002F>\n* \u003Ccode>msbd_logs_create( 'Log something only when the debug mode is active' );\u003C\u002Fcode>\u003Cbr \u002F>\n* \u003Ccode>msbd_logs_create( 'Unexpected issue detected, always log', 'attention' );\u003C\u002Fcode>\u003Cbr \u002F>\n* \u003Ccode>debug\u003C\u002Fcode> logs are written only when debug mode is enabled\u003Cbr \u002F>\n* \u003Ccode>attention\u003C\u002Fcode> logs are always written\u003C\u002Fp>\n\u003Ch3>Admin Interface\u003C\u002Fh3>\n\u003Cp>After activation, a new menu item \u003Cstrong>“MSBD Logs”\u003C\u002Fstrong> appears in the WordPress admin dashboard.\u003C\u002Fp>\n\u003Cp>From this screen, administrators can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>View available log files\u003C\u002Fli>\n\u003Cli>Filter log files by filename\u003C\u002Fli>\n\u003Cli>Inspect log file contents\u003C\u002Fli>\n\u003Cli>Enable or disable debug logging\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Only users with the \u003Ccode>manage_options\u003C\u002Fcode> capability can access the interface.\u003C\u002Fp>\n\u003Ch3>Standalone & Compatible\u003C\u002Fh3>\n\u003Cp>MSBD Logs works fully as a standalone plugin.\u003C\u002Fp>\n\u003Cp>If other MSBD-related plugins are installed in the future, menu grouping can be handled automatically without affecting functionality.\u003C\u002Fp>\n","Simple logging helper for plugin and theme developers with an admin UI to view and manage log files.",135,"2026-01-27T19:43:00.000Z","6.9.4","5.5",[18,69,70,19,20],"debugging","error-log","https:\u002F\u002Fmicrosolutionsbd.com\u002Fwp-plugin-msbd-logs\u002F2026\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmsbd-logs.1.0.2.zip",{"slug":74,"name":75,"version":76,"author":77,"author_profile":78,"description":79,"short_description":80,"active_installs":81,"downloaded":82,"rating":55,"num_ratings":83,"last_updated":84,"tested_up_to":66,"requires_at_least":85,"requires_php":16,"tags":86,"homepage":89,"download_link":90,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"log-emails","Log Emails","1.5.0","webaware","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebaware\u002F","\u003Cp>Log emails to the WordPress database for later analysis. Access is restricted to administrators, and emails with WordPress passwords are obfuscated for security \u002F privacy. Useful for diagnosing lost email problems.\u003C\u002Fp>\n\u003Cp>Use this plugin with \u003Ca href=\"https:\u002F\u002Fshop.webaware.com.au\u002Fdownloads\u002Fdisable-emails\u002F\" rel=\"nofollow ugc\">Disable Emails\u003C\u002Fa> to divert all WordPress emails into logs, especially handy for developers.\u003C\u002Fp>\n\u003Cp>Logs are automatically purged after a defined period, set through a settings page in the WordPress admin. Setting the period to 0 prevents logs from being purged. Uninstalling the plugin purges all logs.\u003C\u002Fp>\n\u003Ch3>Translations\u003C\u002Fh3>\n\u003Cp>Many thanks to the generous efforts of our translators:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Czech (cs-CZ) — \u003Ca href=\"http:\u002F\u002Fwww.klusik.cz\u002F\" rel=\"nofollow ugc\">Rudolf Klusal\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>English (en_CA) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-ca\u002Fdefault\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">the English (Canadian) translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>English (en_GB) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-gb\u002Fdefault\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">the English (British) translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>French (fr-FR) — \u003Ca href=\"http:\u002F\u002Fwww.eticweb.ca\u002F\" rel=\"nofollow ugc\">Hugo Catellier\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Korean (ko_KR) — \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fko\u002Fdefault\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">the Korean translation team\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you’d like to help out by translating this plugin, please \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Flog-emails\" rel=\"nofollow ugc\">sign up for an account and dig in\u003C\u002Fa>.\u003C\u002Fp>\n","Log emails to the database, to enable email problem analysis",6000,55799,11,"2025-12-14T04:14:00.000Z","4.0",[87,88,19,20],"email","email-log","https:\u002F\u002Fshop.webaware.com.au\u002Fdownloads\u002Flog-emails\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flog-emails.1.5.0.zip",{"slug":92,"name":93,"version":94,"author":95,"author_profile":96,"description":97,"short_description":98,"active_installs":99,"downloaded":100,"rating":101,"num_ratings":102,"last_updated":103,"tested_up_to":104,"requires_at_least":105,"requires_php":106,"tags":107,"homepage":111,"download_link":112,"security_score":113,"vuln_count":114,"unpatched_count":11,"last_vuln_date":115,"fetched_at":27},"decalog","DecaLog","4.6.0","Pierre Lannoy","https:\u002F\u002Fprofiles.wordpress.org\u002Fpierrelannoy\u002F","\u003Cp>\u003Cstrong>Capture and log events, metrics and traces on your site. Make WordPress observable – finally!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>De-facto standard stack for WordPress observability, \u003Cstrong>DecaLog\u003C\u002Fstrong> provides reliable and powerful logging, monitoring and tracing features for WordPress core, PHP, database, plugins and themes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>DecaLog\u003C\u002Fstrong> captures events generated by WordPress core, PHP, database, plugins and themes, collates metrics and KPIs and follows traces of the full WordPress execution. It has the ability to enrich these events, metrics and traces with many details regarding their triggering, before storing them in WordPress database or passing them to external services.\u003C\u002Fp>\n\u003Cp>If you don’t want to use external services, \u003Cstrong>DecaLog\u003C\u002Fstrong> provides the tools to leverage all the benefits of observability right in the WordPress admin dashboard. It supports multisite logs delegation and contains many features to help to protect personal information (user pseudonymization, IP obfuscation, etc.).\u003C\u002Fp>\n\u003Cp>For a full list of supported – internal or third-party – services please, jump to the official \u003Ca href=\"https:\u002F\u002Fperfops.one\u002Fdecalog#services\" rel=\"nofollow ugc\">supported services list\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>DecaLog\u003C\u002Fstrong> can be used in dev\u002Fdebug phases or on production sites: it has nearly no resource impact on the server. It provides an extensive set of WP-CLI commands to help operations too.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>DecaLog\u003C\u002Fstrong> is part of \u003Ca href=\"https:\u002F\u002Fperfops.one\u002F\" rel=\"nofollow ugc\">PerfOps One\u003C\u002Fa>, a suite of free and open source WordPress plugins dedicated to observability and operations performance.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Developers\u003C\u002Fh4>\n\u003Cp>If you’re a plugins \u002F themes developer and want to take advantage of the logging features of DecaLog, there’s a \u003Ca href=\"https:\u002F\u002Fdecalog.io\u002F\" rel=\"nofollow ugc\">DecaLog SDK\u003C\u002Fa> for you.\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>This plugin is free and provided without warranty of any kind. Use it at your own risk, I’m not responsible for any improper use of this plugin, nor for any damage it might cause to your site. Always backup all your data before installing a new plugin.\u003C\u002Fp>\n\u003Cp>Anyway, I’ll be glad to help you if you encounter issues when using this plugin. Please read carefully the FAQ at the bottom of this page before requesting support.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin, as any piece of software, is neither compliant nor non-compliant with privacy laws and regulations. It is your responsibility to use it – by activating the corresponding options or services – with respect for the personal data of your users and applicable laws.\u003C\u002Fp>\n\u003Cp>This plugin doesn’t set any cookie in the user’s browser.\u003C\u002Fp>\n\u003Cp>This plugin may handle personally identifiable information (PII). If the GDPR or CCPA or similar regulation applies to your case, you must use the anonymization options embedded in the plugin and\u002For adapt your processes (consent management, security measure, treatment register, etc.).\u003C\u002Fp>\n\u003Ch4>Donation\u003C\u002Fh4>\n\u003Cp>If you like this plugin or find it useful and want to thank me for the work done, please consider making a donation to \u003Ca href=\"https:\u002F\u002Fwww.laquadrature.net\u002Fen\" rel=\"nofollow ugc\">La Quadrature Du Net\u003C\u002Fa> or the \u003Ca href=\"https:\u002F\u002Fwww.eff.org\u002F\" rel=\"nofollow ugc\">Electronic Frontier Foundation\u003C\u002Fa> which are advocacy groups defending the rights and freedoms of citizens on the Internet. By supporting them, you help the daily actions they perform to defend our fundamental freedoms!\u003C\u002Fp>\n","Capture and log events, metrics and traces on your site. Make WordPress observable - finally!",1000,49582,96,8,"2026-03-23T09:03:00.000Z","7.0","6.4","8.2",[108,19,20,109,110],"error-reporting","monitoring","tracing","https:\u002F\u002Fperfops.one\u002Fdecalog","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdecalog.4.6.0.zip",98,2,"2024-03-26 00:00:00",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":99,"downloaded":124,"rating":55,"num_ratings":45,"last_updated":125,"tested_up_to":126,"requires_at_least":127,"requires_php":53,"tags":128,"homepage":133,"download_link":134,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"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.",166286,"2021-06-25T14:17:00.000Z","5.8.13","3.0",[129,130,131,19,132],"admin","deprecated","e_notice","wp_debug","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Flog-deprecated-notices\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flog-deprecated-notices.0.4.1.zip",{"attackSurface":136,"codeSignals":148,"taintFlows":155,"riskAssessment":156,"analyzedAt":159},{"hooks":137,"ajaxHandlers":144,"restRoutes":145,"shortcodes":146,"cronEvents":147,"entryPointCount":11,"unprotectedCount":11},[138],{"type":139,"name":140,"callback":141,"file":142,"line":143},"action","plugins_loaded","WP_Debug_Logger\\set_default_constants","wp-debug-logger.php",17,[],[],[],[],{"dangerousFunctions":149,"sqlUsage":150,"outputEscaping":152,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":11,"bundledLibraries":154},[],{"prepared":11,"raw":11,"locations":151},[],{"escaped":11,"rawEcho":11,"locations":153},[],[],[],{"summary":157,"deductions":158},"The plugin 'debug-logger' v0.3.0 exhibits an exceptionally strong security posture based on the provided static analysis and vulnerability history. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events signifies a remarkably small and potentially well-secured attack surface. Furthermore, the code analysis reveals excellent security practices with no dangerous functions, all SQL queries utilizing prepared statements, and all output being properly escaped. The lack of file operations, external HTTP requests, and the absence of any taint flows with unsanitized paths further bolster this assessment.  The vulnerability history is equally pristine, with zero recorded CVEs of any severity. This indicates a consistent and long-standing commitment to security by the plugin's developers. While the lack of nonce and capability checks is noted, given the zero attack surface and zero vulnerabilities, this appears to be a consequence of the plugin's minimal functionality rather than a direct oversight.  Overall, this plugin presents a very low security risk.",[],"2026-03-17T05:54:48.193Z",{"wat":161,"direct":170},{"assetPaths":162,"generatorPatterns":165,"scriptPaths":166,"versionParams":167},[163,164],"\u002Fwp-content\u002Fplugins\u002Fdebug-logger\u002Fassets\u002Fcss\u002Fdebug-logger.css","\u002Fwp-content\u002Fplugins\u002Fdebug-logger\u002Fassets\u002Fjs\u002Fdebug-logger.js",[],[164],[168,169],"debug-logger\u002Fassets\u002Fcss\u002Fdebug-logger.css?ver=","debug-logger\u002Fassets\u002Fjs\u002Fdebug-logger.js?ver=",{"cssClasses":171,"htmlComments":172,"htmlAttributes":173,"restEndpoints":174,"jsGlobals":175,"shortcodeOutput":176},[],[],[],[],[],[],{"error":178,"url":179,"statusCode":180,"statusMessage":181,"message":181},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fdebug-logger\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":114,"versions":183},[184,190],{"version":6,"download_url":24,"svn_tag_url":185,"released_at":26,"has_diff":186,"diff_files_changed":187,"diff_lines":26,"trac_diff_url":188,"vulnerabilities":189,"is_current":178},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-logger\u002Ftags\u002F0.3.0\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-logger%2Ftags%2F0.2.0&new_path=%2Fdebug-logger%2Ftags%2F0.3.0",[],{"version":191,"download_url":192,"svn_tag_url":193,"released_at":26,"has_diff":186,"diff_files_changed":194,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":195,"is_current":186},"0.2.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-logger.0.2.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-logger\u002Ftags\u002F0.2.0\u002F",[],[]]