[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fBXRskGZTak8HgiwN38Qorf0uJiATLeY55LMNG5DcC9w":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":35,"analysis":132,"fingerprints":230},"logmate","LogMate","1.0.0","Yoyal Limbu","https:\u002F\u002Fprofiles.wordpress.org\u002Fy0000el\u002F","\u003Cp>LogMate provides a modern interface for managing and exporting WordPress error and PHP\u002FJS logs. Monitor, filter, purge, and export your logs efficiently.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Modern admin interface\u003C\u002Fli>\n\u003Cli>Real-time log viewing with auto-refresh\u003C\u002Fli>\n\u003Cli>Advanced filtering and search capabilities\u003C\u002Fli>\n\u003Cli>Group duplicate errors with occurrence counts\u003C\u002Fli>\n\u003Cli>Identify error sources (Core\u002FPlugin\u002FTheme)\u003C\u002Fli>\n\u003Cli>Log purging by date or keep last N days\u002Fweeks\u002Fmonths\u003C\u002Fli>\n\u003Cli>Export logs with date range filtering\u003C\u002Fli>\n\u003Cli>Toggle debug logging with one click\u003C\u002Fli>\n\u003Cli>JavaScript error logging support\u003C\u002Fli>\n\u003Cli>Secure log file location\u003C\u002Fli>\n\u003C\u002Ful>\n","Modern log management and export for WordPress with purging, filtering, and export. by BruteFort",0,136,"2026-02-16T05:00:00.000Z","6.9.4","5.0","7.4",[18,19,20,21,22],"debug","developer","errors","export","logging","https:\u002F\u002Fbrutefort.com\u002F#\u002Fproducts\u002Flogmate","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flogmate.1.0.0.zip",100,null,"2026-03-15T14:54:45.397Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"y0000el",2,30,94,"2026-04-05T18:05:03.003Z",[36,56,77,99,117],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":11,"num_ratings":11,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":52,"download_link":53,"security_score":54,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":55},"wp-developers-toolbox","WP Developer's Toolbox","1.0.1","James-Read","https:\u002F\u002Fprofiles.wordpress.org\u002Fjames-read-1\u002F","\u003Cp>This handy plugin speeds up some debugging actions; when developing web applications, websites and plugins with WordPress.\u003C\u002Fp>\n\u003Cp>For more information visit : https:\u002F\u002Freadwebtechnology.com\u002Fwp-developers-tool-box\u002F\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Toggle error reporting messages on and off from the dashboard and the WP Admin bar\u003C\u002Fli>\n\u003Cli>Hide and turn off error messages\u003C\u002Fli>\n\u003Cli>Toggle error logging on and off from the dashboard\u003C\u002Fli>\n\u003Cli>Display errors only to logged in Administrators\u003C\u002Fli>\n\u003Cli>Display errors only to visitors from a whitelisted IP address\u003C\u002Fli>\n\u003Cli>Quickly and safely rename the “\u002Fplugins” directory from the dashboard; to ascertain if the error is in a plugin, or not\u003C\u002Fli>\n\u003Cli>Toggle the WP Admin bar to display on or off, from the WP Admin bar and dashboard\u003C\u002Fli>\n\u003Cli>Show System information using phpinfo\u003C\u002Fli>\n\u003Cli>Quickly export the active database, with a conditional drop statement; to a .htaccess protected directory\u003C\u002Fli>\n\u003C\u002Ful>\n","\"Great for turning DEBUG mode on and off - quickly!\" * Hide or show error notifications - globally or conditionally!",10,1473,"2016-05-05T21:48:00.000Z","4.5.33","3.0.1","",[51],"developer-tools-error-logging-hide-errors-system-info-php-export-database","https:\u002F\u002Freadwebtechnology.com\u002Fwp-developers-tool-box\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-developers-toolbox.zip",85,"2026-03-15T15:16:48.613Z",{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":25,"num_ratings":66,"last_updated":67,"tested_up_to":68,"requires_at_least":69,"requires_php":70,"tags":71,"homepage":72,"download_link":73,"security_score":74,"vuln_count":75,"unpatched_count":11,"last_vuln_date":76,"fetched_at":55},"debug-log-manager","Debug Log Manager – Conveniently Monitor and Inspect Errors","2.4.3","Bowo","https:\u002F\u002Fprofiles.wordpress.org\u002Fqriouslad\u002F","\u003Cp>Debug Log Manager allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Farticle\u002Fdebugging-in-wordpress\u002F\" rel=\"ugc\">WP_DEBUG\u003C\u002Fa> with one click to log PHP, database and JavaScript errors\u003C\u002Fstrong> when you need to, and disable it when you’re done. No need to manually edit wp-config.php file. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create the debug.log file for you\u003C\u002Fstrong> in a non-default location with a custom file name for enhanced security. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Copy the content of the default \u002F existing debug.log file\u003C\u002Fstrong> into the custom debug.log file, and delete the default \u002F existing debug.log file. So there is continuation in logging and enhanced security going forward.\u003C\u002Fli>\n\u003Cli>Parse the debug.log file and \u003Cstrong>view distinct errors and when they last occurred\u003C\u002Fstrong>, which is better than looking at the raw log file (potentially) full of repetitive errors. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quickly find and filter more specific errors\u003C\u002Fstrong> for your debugging work.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Make error details easier to read\u003C\u002Fstrong> by identifying error source (core \u002F plugin \u002F theme) and separating file path and line number.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Easily view files where PHP errors occurred\u003C\u002Fstrong>. This includes WordPress core, plugin and theme files.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enable auto-refresh\u003C\u002Fstrong> to automatically load new log entries. No need to manually reload the browser tab, or to \u003Ccode>tail -f\u003C\u002Fcode> the log file on the command line.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Easily clear the debug.log file\u003C\u002Fstrong> to save disk space and more easily observe newly occurring errors on your site.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Show an indicator on the admin bar\u003C\u002Fstrong> when error logging is enabled.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add a dashboard widget\u003C\u002Fstrong> showing the latest errors logged.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use \u003Ccode>error_log()\u003C\u002Fcode>\u003C\u002Fstrong> to output error info into your debug log. e.g. \u003Ccode>error_log( $error_message )\u003C\u002Fcode> for simple, string-based error message, or \u003Ccode>error_log( json_encode( $error ) )\u003C\u002Fcode> when inspecting a more complex error info, e.g. array or object.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A simpler and more compact version of Debug Log Manager is included as part of the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsystem-dashboard\u002F\" rel=\"ugc\">System Dashboard plugin\u003C\u002Fa>, should you prefer a single plugin that does more.\u003C\u002Fp>\n\u003Ch3>What Users Say\u003C\u002Fh3>\n\u003Cp>\u003Cem>“This is \u003Cstrong>a great plugin for dev\u003C\u002Fstrong> especially for people who tinker in the code.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fgreat-for-dev\u002F\" rel=\"ugc\">PK Son\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“I have used a couple of other logger plugins and \u003Cstrong>this is by far the best one\u003C\u002Fstrong>.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fmust-have-plugin-485\u002F\" rel=\"ugc\">Brian Henry\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“\u003Cstrong>Another massive time-saving tool.\u003C\u002Fstrong>“\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fdigwp.com\u002F2023\u002F06\u002Fplugins-troubleshoot-debug-wordpress\u002F\" rel=\"nofollow ugc\">Jeff Starr\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Give Back\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Freview-dlm\" rel=\"nofollow ugc\">A nice review\u003C\u002Fa> would be great!\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Ffeedback-dlm\" rel=\"nofollow ugc\">Give feedback\u003C\u002Fa> and help improve future versions.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdebug-log-manager\u002F\" rel=\"nofollow ugc\">Help translate\u003C\u002Fa> into your language.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fgithub-dlm\" rel=\"nofollow ugc\">Github repo\u003C\u002Fa> to contribute code.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fdotorg-sponsor-dlm\" rel=\"nofollow ugc\">Sponsor\u003C\u002Fa> my work.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Check These Out Too\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsystem-dashboard\u002F\" rel=\"ugc\">System Dashboard\u003C\u002Fa>: Central dashboard to monitor various WordPress components, processes and data, including the server.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fvariable-inspector\u002F\" rel=\"ugc\">Variable Inspector\u003C\u002Fa>: Inspect PHP variables on a central dashboard in wp-admin for convenient debugging.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadmin-site-enhancements\u002F\" rel=\"ugc\">Admin and Site Enhancements\u003C\u002Fa> helps you to easily enhance various admin workflows and site aspects while replacing multiple plugins doing it.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.wpnewsboard.com\u002F\" rel=\"nofollow ugc\">WordPress Newsboard\u003C\u002Fa>: The latest news, articles, podcasts and videos from 100+ WordPress-focused sources.\u003C\u002Fli>\n\u003C\u002Ful>\n","Log PHP, database and JavaScript errors via WP_DEBUG with one click. Conveniently create, view, filter and clear the debug.log file.",10000,116535,24,"2025-09-24T02:30:00.000Z","6.8.5","4.6","5.6",[18,19,20],"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-log-manager\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-manager.2.4.3.zip",91,7,"2025-04-18 00:00:00",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":84,"active_installs":85,"downloaded":86,"rating":11,"num_ratings":11,"last_updated":87,"tested_up_to":88,"requires_at_least":89,"requires_php":49,"tags":90,"homepage":94,"download_link":95,"security_score":96,"vuln_count":97,"unpatched_count":11,"last_vuln_date":98,"fetched_at":55},"developer-loggers-for-simple-history","Developer Loggers for Simple History","0.5.1","Pär Thernström","https:\u002F\u002Fprofiles.wordpress.org\u002Feskapism\u002F","\u003Cp>Bring more loggers to \u003Ca href=\"https:\u002F\u002Fsimple-history.com\" rel=\"nofollow ugc\">WordPress user history plugin Simple History\u003C\u002Fa>.\u003Cbr \u002F>\nThat are useful for developers during development of a site or to maintain a live site.\u003C\u002Fp>\n\u003Ch3>Important\u003C\u002Fh3>\n\u003Cp>Please note that this plugin is no longer actively maintained and only receives security fixes.\u003C\u002Fp>\n\u003Ch3>Modern and up to date alternatives\u003C\u002Fh3>\n\u003Cp>For an up to date alternative please see the \u003Ca href=\"https:\u002F\u002Fsimple-history.com\u002Fadd-ons\u002Fdebug-and-monitor\u002F\" rel=\"nofollow ugc\">Debug & Monitor add-on\u003C\u002Fa> which logs WP REST API requests, sent emails, HTTP API requests, and WP cron jobs.\u003C\u002Fp>\n\u003Ch3>Get more features with Simple History Premium\u003C\u002Fh3>\n\u003Cp>Need advanced WordPress audit logging capabilities? Simple History Premium extends your site monitoring with powerful features:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enhanced WordPress Activity Logging:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Advanced Analytics Dashboard\u003C\u002Fstrong> – Comprehensive stats and visual activity tracking\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Event Logging\u003C\u002Fstrong> – Add manual entries and notifications to your audit trail\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stealth Mode\u003C\u002Fstrong> – Control user access with granular permissions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Flexible Log Retention\u003C\u002Fstrong> – Configure automatic cleanup or keep logs indefinitely\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Export Tools\u003C\u002Fstrong> – Export logs in CSV\u002FJSON format for analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Features\u003C\u002Fstrong> – IP anonymization and login attempt location tracking\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fsimple-history.com\u002Fpremium\u002F\" rel=\"nofollow ugc\">» \u003Cstrong>Get Simple History Premium\u003C\u002Fstrong>\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Included loggers and plugins\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Post to Slack\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>All your events is posted to a \u003Ca href=\"https:\u002F\u002Fslack.com\u002F\" rel=\"nofollow ugc\">Slack\u003C\u002Fa> channel of your choice, using an \u003Ca href=\"https:\u002F\u002Fapi.slack.com\u002Fincoming-webhooks\" rel=\"nofollow ugc\">incoming webhook\u003C\u002Fa>. Yes, with this plugin enabled\u003Cbr \u002F>\nthere is no need what so ever to ever leave Slack to see what’s happening on your site or the site of your\u003Cbr \u002F>\nclients or… well, on any site where you have Simple Histor and this plugin enabled.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_Mail-logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>See all mails sent with wp_mail(), no matter what the recipient address is.\u003Cbr \u002F>\nchangelog\u003C\u002Fp>\n\u003Cp>\u003Cstrong>404 logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>View page visits that load the 404 template.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>JavaScript error logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>See what JavaScript errors users that visit your site is getting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SystemLog logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Log all messages from Simple History to the syslog on the server. With this logger enabled there is no need to use the beautiful GUI of Simple History ;).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>HTTP API logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Log all usage of HTTP calls from functions like wp_remote_post() and wp_remote_get().\u003C\u002Fp>\n\u003Cp>You can the URL requested, the arguments posted and the full returned result, including server headers.\u003C\u002Fp>\n\u003Cp>The time for the request to complete is also logged. Great for debugging!\u003C\u002Fp>\n","Useful loggers for SimpleHistory for developers during development of a site or to maintain a live site.",400,7569,"2025-09-15T07:32:00.000Z","6.4.8","4.4",[91,19,92,22,93],"debugging","email","simple-history","https:\u002F\u002Fgithub.com\u002Fbonny\u002FDeveloper-Loggers-for-Simple-History","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-loggers-for-simple-history.0.5.1.zip",99,1,"2025-09-16 00:00:00",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":107,"downloaded":108,"rating":25,"num_ratings":97,"last_updated":109,"tested_up_to":14,"requires_at_least":110,"requires_php":16,"tags":111,"homepage":115,"download_link":116,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":55},"error-logs-emailer-for-woocommerce","Error Logs Emailer for WooCommerce","1.2.4","Michal Slepko","https:\u002F\u002Fprofiles.wordpress.org\u002Fmslepko\u002F","\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frootscopeltd\u002Fwc-error-logs-emailer\" rel=\"nofollow ugc\">Error Logs Emailer for WooCommerce\u003C\u002Fa> is a free plugin to send fatal error logged by WooCommerce\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Know what errors are happening on your site without constantly checking the logs\u003C\u002Fli>\n\u003Cli>Set the email where error logs should be sent if it’s not a site admin\u003C\u002Fli>\n\u003Cli>Add multiple email addresses\u003C\u002Fli>\n\u003Cli>Emails are sent at 5AM\u003C\u002Fli>\n\u003C\u002Ful>\n","Sends the previous day's WooCommerce fatal error log to specified email(s) using Action Scheduler.",20,1254,"2026-01-22T00:01:00.000Z","6.0",[18,112,113,20,114],"developers","error-log","woocommerce","https:\u002F\u002Fgithub.com\u002Frootscopeltd\u002Fwc-error-logs-emailer","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-logs-emailer-for-woocommerce.1.2.4.zip",{"slug":118,"name":119,"version":120,"author":121,"author_profile":122,"description":123,"short_description":124,"active_installs":11,"downloaded":125,"rating":11,"num_ratings":11,"last_updated":126,"tested_up_to":68,"requires_at_least":49,"requires_php":127,"tags":128,"homepage":130,"download_link":131,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":55},"debug-console-php","Debug Console for PHP","3.5","Brad Kent","https:\u002F\u002Fprofiles.wordpress.org\u002Fbkdotcom\u002F","\u003Cp>Adds debug \u002F logging output that by default shows query, cache, and other helpful debugging information.\u003C\u002Fp>\n\u003Cp>WebSite:   https:\u002F\u002Fbradkent.com\u002Fphp\u002Fdebug\u003C\u002Fp>\n\u003Cp>Adds helpful logging methods and utilties\u003C\u002Fp>\n\u003Cp>Logging methods:\u003Cbr \u002F>\n – log\u003Cbr \u002F>\n – info\u003Cbr \u002F>\n – warn\u003Cbr \u002F>\n – error\u003Cbr \u002F>\n – group\u003Cbr \u002F>\n – groupCollapsed\u003Cbr \u002F>\n – assert\u003Cbr \u002F>\n – count\u003Cbr \u002F>\n – table\u003Cbr \u002F>\n – trace\u003Cbr \u002F>\n – time\u003C\u002Fp>\n\u003Cp>inspect values (objects, methods, properties, constants, etc)\u003C\u002Fp>\n\u003Cp>Send error notifications to email \u002F discord \u002F slack \u002F teams\u003C\u002Fp>\n\u003Cp>Other output options\u003Cbr \u002F>\n – log file,\u003Cbr \u002F>\n – javascript (browser console),\u003Cbr \u002F>\n – ServerLog (browser extension),\u003Cbr \u002F>\n – ChromeLogger (browser extension)\u003Cbr \u002F>\n – FirePHP (browser extension)\u003C\u002Fp>\n","Log, Debug, Inspect (\"Debug Bar\" on steroids)",210,"2025-08-20T04:02:00.000Z","7.0",[129],"debug-logging-developer","https:\u002F\u002Fbradkent.com\u002Fphp\u002Fdebug","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-console-php.3.5.zip",{"attackSurface":133,"codeSignals":169,"taintFlows":181,"riskAssessment":223,"analyzedAt":229},{"hooks":134,"ajaxHandlers":165,"restRoutes":166,"shortcodes":167,"cronEvents":168,"entryPointCount":11,"unprotectedCount":11},[135,140,145,148,152,156,162],{"type":136,"name":137,"callback":138,"file":139,"line":66},"action","rest_api_init","register_rest_routes","includes\\Routes\\Routes.php",{"type":136,"name":141,"callback":142,"file":143,"line":144},"admin_menu","register_menu","includes\\Settings.php",23,{"type":136,"name":146,"callback":147,"file":143,"line":66},"admin_enqueue_scripts","enqueue_assets",{"type":136,"name":149,"callback":150,"file":143,"line":151},"wp_enqueue_scripts","enqueue_public_assets",25,{"type":136,"name":153,"callback":154,"file":143,"line":155},"admin_init","redirect_after_activation",26,{"type":157,"name":158,"callback":159,"priority":44,"file":160,"line":161},"filter","doing_it_wrong_trigger_error","filter_doing_it_wrong","logmate.php",66,{"type":136,"name":163,"callback":163,"priority":11,"file":160,"line":164},"init",156,[],[],[],[],{"dangerousFunctions":170,"sqlUsage":171,"outputEscaping":173,"fileOperations":144,"externalRequests":11,"nonceChecks":31,"capabilityChecks":31,"bundledLibraries":180},[],{"prepared":11,"raw":11,"locations":172},[],{"escaped":174,"rawEcho":97,"locations":175},16,[176],{"file":177,"line":178,"context":179},"includes\\Controllers\\DebugLogController.php",343,"raw output",[],[182,210],{"entryPoint":183,"graph":184,"unsanitizedCount":208,"severity":209},"create_log_file (includes\\Settings.php:291)",{"nodes":185,"edges":204},[186,191,197,199],{"id":187,"type":188,"label":189,"file":143,"line":190},"n0","source","$_SERVER (x2)",306,{"id":192,"type":193,"label":194,"file":143,"line":195,"wp_function":196},"n1","sink","update_option() [Settings Manipulation]",312,"update_option",{"id":198,"type":188,"label":189,"file":143,"line":190},"n2",{"id":200,"type":193,"label":201,"file":143,"line":202,"wp_function":203},"n3","file_put_contents() [File Write]",322,"file_put_contents",[205,207],{"from":187,"to":192,"sanitized":206},false,{"from":198,"to":200,"sanitized":206},4,"medium",{"entryPoint":211,"graph":212,"unsanitizedCount":11,"severity":222},"\u003CSettings> (includes\\Settings.php:0)",{"nodes":213,"edges":218},[214,215,216,217],{"id":187,"type":188,"label":189,"file":143,"line":190},{"id":192,"type":193,"label":194,"file":143,"line":195,"wp_function":196},{"id":198,"type":188,"label":189,"file":143,"line":190},{"id":200,"type":193,"label":201,"file":143,"line":202,"wp_function":203},[219,221],{"from":187,"to":192,"sanitized":220},true,{"from":198,"to":200,"sanitized":220},"low",{"summary":224,"deductions":225},"The plugin \"logmate\" v1.0.0 demonstrates a strong security posture with no known CVEs and a complete absence of critical or high-severity findings in the static and taint analysis. The code adheres to good security practices by utilizing prepared statements for all SQL queries, implementing nonce checks, and performing capability checks for its limited entry points. The high percentage of properly escaped output further indicates a diligent approach to preventing cross-site scripting vulnerabilities.  The plugin's attack surface is minimal, with no apparent AJAX handlers, REST API routes, shortcodes, or cron events, significantly reducing the potential for unauthorized access or manipulation.  The single flow with an unsanitized path, while not flagged as critical or high severity, warrants attention as it represents a potential area for improvement in input validation, particularly if it involves file operations.  Overall, \"logmate\" v1.0.0 appears to be a securely developed plugin, with its vulnerability history being completely clear, suggesting a commitment to security by its developers.",[226],{"reason":227,"points":228},"Flow with unsanitized path detected",5,"2026-03-17T06:09:21.118Z",{"wat":231,"direct":240},{"assetPaths":232,"generatorPatterns":235,"scriptPaths":236,"versionParams":237},[233,234],"\u002Fwp-content\u002Fplugins\u002Flogmate\u002Fdist\u002Fassets\u002Findex.js","\u002Fwp-content\u002Fplugins\u002Flogmate\u002Fdist\u002Fassets\u002Fvendor.js",[],[233,234],[238,239],"logmate\u002Fdist\u002Fassets\u002Findex.js?ver=","logmate\u002Fdist\u002Fassets\u002Fvendor.js?ver=",{"cssClasses":241,"htmlComments":243,"htmlAttributes":244,"restEndpoints":247,"jsGlobals":249,"shortcodeOutput":251},[242],"logmate-admin-app",[],[245,246],"data-logmate-url","data-logmate-nonce",[248],"\u002Fwp-json\u002Flogmate\u002F",[250],"logmate_vars",[]]