[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fJKhTa03tamzvhHf4lNH_oOzFaXCXloAeNrJyjijE8Tc":3,"$fC5yFHGWbeX2dzFuvnOsoWg8SdCgEcPi8J8u9L__3aIQ":201,"$fsE7LkKBId3sA8MgkVs_y5Bj7n1U-5P_tGPBll2jrxx4":206},{"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":23,"download_link":24,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":38,"analysis":143,"fingerprints":188},"hagakure","Hagakure – Yet Another Error Reporter","1.3.2","TAROSKY INC.","https:\u002F\u002Fprofiles.wordpress.org\u002Ftarosky\u002F","\u003Cp>Have you ever seen an error log like the one below?\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted (tried to allocate xxx bytes) in \u002Fvar\u002Fwww\u002Fwordpress\u002Fwp-includes\u002Fwp-db.php on line 2007\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>This means that \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fini.core.php#ini.memory-limit\" rel=\"nofollow ugc\">PHP memory limit\u003C\u002Fa> is exhausted while retrieving data from a database. In any case, this happens when your site has big data and makes insane loops inside.\u003C\u002Fp>\n\u003Cp>But we want to know that \u003Cstrong>which plugin tried to retrieve data?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Hagakure adds extra information to error.log file when \u003Ccode>wp-db.php\u003C\u002Fcode> causes memory limit error:\u003C\u002Fp>\n\u003Cpre>[08-May-2019 10:28:37 UTC] wpdb Error Backtrace:\n#1      Kunoichi\\Hagakure\\DbLogger->filter_query()      \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fclass-wp-hook.php       Line 286\n#2      WP_Hook->apply_filters()        \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fplugin.php      Line 208\n#3      apply_filters   \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fwp-db.php       Line 1871\n#4      wpdb->query()   \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fwp-db.php       Line 2579\n#5      wpdb->get_results()     \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fclass-wp-query.php      Line 2979\n#6      WP_Query->get_posts()   \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fclass-wp-query.php      Line 3387\n#7      WP_Query->query()       \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fpost.php        Line 1961\n#8      get_posts       \u002Fapp\u002Fpublic\u002Fwp-content\u002Fplugins\u002Fhagakure\u002Fhagakure.php    Line 34\n#9      {closure}       \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fclass-wp-hook.php       Line 286\n#10     WP_Hook->apply_filters()        \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fclass-wp-hook.php       Line 310\n#11     WP_Hook->do_action()    \u002Fapp\u002Fpublic\u002Fwp-includes\u002Fplugin.php      Line 465\n#12     do_action       \u002Fapp\u002Fpublic\u002Fwp-includes\u002Ftemplate-loader.php     Line 13\n#13     require_once    \u002Fapp\u002Fpublic\u002Fwp-blog-header.php  Line 19\n#14     require \u002Fapp\u002Fpublic\u002Findex.php   Line 17\n#15     URI: \u002F?p=1\u003C\u002Fpre>\n\u003Cp>This log will always follow the memory limit Fatal Error by \u003Ccode>wp-db.php\u003C\u002Fcode>. Now you can find \u003Ccode>#8\u003C\u002Fcode> calls \u003Ccode>get_posts\u003C\u002Fcode> repeatedly.\u003C\u002Fp>\n\u003Cp>We recommend watching logs with notification services like \u003Ca href=\"https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonCloudWatch\u002Flatest\u002Flogs\u002FWhatIsCloudWatchLogs.html\" rel=\"nofollow ugc\">CloudWatch Logs\u003C\u002Fa>.\u003Cbr \u002F>\nThis error occurs in the productional environment, and you may not have a chance to see it occurs.\u003Cbr \u002F>\nWe use Hagakure with our \u003Ca href=\"https:\u002F\u002Fhosting.kunoichiwp.com\u002F\" rel=\"nofollow ugc\">hosting service\u003C\u002Fa>, please look forward to seeing \u003Ca href=\"https:\u002F\u002Fkunoichiwp.com\u002Fblog\" rel=\"nofollow ugc\">our blog published\u003C\u002Fa> and describing the integration!\u003C\u002Fp>\n\u003Cp>This plugin also adds debug backtrace to error logs. To modify the error level to a detailed backtrace, define the constant in \u003Ccode>wp-config.php\u003C\u002Fcode> or somewhere else:\u003C\u002Fp>\n\u003Cpre>define( 'HAGAKURE_ERROR_LEVEL', E_NOTICE | E_USER_WARNING | E_WARNING | E_USER_ERROR );\u003C\u002Fpre>\n\u003Cp>Besides that, if \u003Ccode>SAVEQUERIES\u003C\u002Fcode> is set \u003Ccode>true\u003C\u002Fcode>, the slow query log will be logged with PHP debug backtrace. This helps you to debug.\u003C\u002Fp>\n\u003Ch3>Acknowledgements\u003C\u002Fh3>\n\u003Cp>The base text for dummy content is “Three Ghost Story” by Charles Dickens. The text file is modified the one of \u003Ca href=\"https:\u002F\u002Fwww.gutenberg.org\u002Febooks\u002F1289\" rel=\"nofollow ugc\">Project Gutenberg\u003C\u002Fa>.\u003C\u002Fp>\n","A WordPress plugin to clarify meaningless errors like \"Allowed memory size of xxxxxxxx bytes exhausted\".",30,2005,100,2,"2025-03-28T12:53:00.000Z","6.6.5","5.9","7.4",[20,21,22],"error","php","recovery","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.1.3.2.zip",92,0,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":35,"avg_patch_time_days":11,"trust_score":36,"computed_at":37},"tarosky",14,710,94,90,"2026-05-19T22:37:15.436Z",[39,64,88,109,128],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":18,"tags":54,"homepage":59,"download_link":60,"security_score":61,"vuln_count":62,"unpatched_count":26,"last_vuln_date":63,"fetched_at":28},"error-log-monitor","Error Log Monitor","1.7.12","Janis Elsts","https:\u002F\u002Fprofiles.wordpress.org\u002Fwhiteshadow\u002F","\u003Cp>This plugin adds a Dashboard widget that displays the latest messages from your PHP error log. It can also send you email notifications about newly logged errors.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Automatically detects error log location.\u003C\u002Fli>\n\u003Cli>Explains how to configure PHP error logging if it’s not enabled yet.\u003C\u002Fli>\n\u003Cli>The number of displayed log entries is configurable.\u003C\u002Fli>\n\u003Cli>Sends you email notifications about logged errors (optional).\u003C\u002Fli>\n\u003Cli>Configurable email address and frequency.\u003C\u002Fli>\n\u003Cli>You can easily clear the log file.\u003C\u002Fli>\n\u003Cli>The dashboard widget is only visible to administrators.\u003C\u002Fli>\n\u003Cli>Optimized to work well even with very large log files.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Usage\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Once you’ve installed the plugin, go to the Dashboard and enable the “PHP Error Log” widget through the “Screen Options” panel. The widget should automatically display the last 20 lines from your PHP error log. If you see an error message like “Error logging is disabled” instead, follow the displayed instructions to configure error logging.\u003C\u002Fp>\n\u003Cp>Email notifications are disabled by default. To enable them, click the “Configure” link in the top-right corner of the widget and enter your email address in the “Periodically email logged errors to:” box. If desired, you can also change email frequency by selecting the minimum time interval between emails from the “How often to send email” drop-down.\u003C\u002Fp>\n","Adds a Dashboard widget that displays the latest messages from your PHP error log. It can also send logged errors to email.",20000,633977,86,48,"2025-10-01T15:12:00.000Z","6.8.5","4.5",[55,56,57,58,21],"admin","administration","dashboard-widget","error-reporting","http:\u002F\u002Fw-shadow.com\u002Fblog\u002F2012\u002F07\u002F25\u002Ferror-log-monitor-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-log-monitor.1.7.12.zip",99,1,"2019-02-25 00:00:00",{"slug":65,"name":66,"version":67,"author":68,"author_profile":69,"description":70,"short_description":71,"active_installs":72,"downloaded":73,"rating":74,"num_ratings":75,"last_updated":76,"tested_up_to":77,"requires_at_least":78,"requires_php":23,"tags":79,"homepage":84,"download_link":85,"security_score":35,"vuln_count":86,"unpatched_count":26,"last_vuln_date":87,"fetched_at":28},"error-log-viewer","Error Log Viewer by BestWebSoft","1.1.8","bestwebsoft","https:\u002F\u002Fprofiles.wordpress.org\u002Fbestwebsoft\u002F","\u003Cp>Simple utility plugin that helps to find and view log files with errors right from your WordPress admin dashboard. Get access to all your log files from one place. View the latest activity, select logs by date, or view a full log file. Get email notifications about log changes.\u003C\u002Fp>\n\u003Cp>Get access to your website logs and troubleshoot issues faster!\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdemo-error-log-viewer\u002F?ref=readme\" rel=\"nofollow ugc\">View Demo\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F8LR0F4GgXhM?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Enable WordPress error logging with:\n\u003Cul>\n\u003Cli>.htaccess\u003C\u002Fli>\n\u003Cli>wp-config.php using \u003Ccode>inl_set\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>wp-config.php using \u003Ccode>WP_DEBUG\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Search and view error logs:\n\u003Cul>\n\u003Cli>PHP\u003C\u002Fli>\n\u003Cli>WordPress\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Configure email notifications about log changes:\n\u003Cul>\n\u003Cli>Set the email\u003C\u002Fli>\n\u003Cli>Change frequency\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Configure log monitor settings:\n\u003Cul>\n\u003Cli>Choose the log to be displayed\u003C\u002Fli>\n\u003Cli>Choose what to show in the log:\n\u003Cul>\n\u003Cli>Certain last lines in the file\u003C\u002Fli>\n\u003Cli>Log for a certain period of time\u003C\u002Fli>\n\u003Cli>Full file\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>View or save the part of PHP error logs as TXT file\u003C\u002Fli>\n\u003Cli>Compatible with latest WordPress version\u003C\u002Fli>\n\u003Cli>Incredibly simple settings for fast setup without modifying code\u003C\u002Fli>\n\u003Cli>Detailed step-by-step documentation and videos\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you have a feature suggestion or idea you’d like to see in the plugin, we’d love to hear about it! \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew\" rel=\"nofollow ugc\">Suggest a Feature\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Documentation & Videos\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdocumentation\u002Ferror-log-viewer\u002Ferror-log-viewer-user-guide\u002F\" rel=\"nofollow ugc\">[Doc] User Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdocumentation\u002Fhow-to-install-a-wordpress-product\u002Fhow-to-install-a-wordpress-plugin\u002F\" rel=\"nofollow ugc\">[Doc] Installation\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Help & Support\u003C\u002Fh4>\n\u003Cp>Visit our Help Center if you have any questions, our friendly Support Team is happy to help – \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fsupport.bestwebsoft.com\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Affiliate Program\u003C\u002Fh4>\n\u003Cp>Earn 20% commission by selling the premium WordPress plugins and themes by BestWebSoft — https:\u002F\u002Fbestwebsoft.com\u002Faffiliate\u002F\u003C\u002Fp>\n\u003Ch4>Translation\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Russian (ru_RU)\u003C\u002Fli>\n\u003Cli>Ukrainian (uk)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Some of these translations are not complete. We are constantly adding new features which should be translated. If you would like to create your own language pack or update the existing one, you can send \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FTranslating_WordPress\" rel=\"nofollow ugc\">the text of PO and MO files\u003C\u002Fa> to \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew\" rel=\"nofollow ugc\">BestWebSoft\u003C\u002Fa> and we’ll add it to the plugin. You can download the latest version of the program for work with PO and MO \u003Ca href=\"https:\u002F\u002Fwww.poedit.net\u002Fdownload.php\" rel=\"nofollow ugc\">files Poedit\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Recommended Plugins\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fproducts\u002Fwordpress\u002Fplugins\u002Fupdater\u002F?k=e2d89a7eca0a903ab58d99e7ffa3b510\" rel=\"nofollow ugc\">Updater\u003C\u002Fa> – Automatically check and update WordPress website core with all installed plugins and themes to the latest versions.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>This plugin incorporates a license verification mechanism to ensure the authenticity of your license key and provide access to premium features and updates. The verification process involves connecting securely to our external service hosted at BestWebSoft website \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u003C\u002Fa>. Privacy Policy \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fprivacy-policy\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u002Fprivacy-policy\u002F\u003C\u002Fa>. End user license agreement \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fend-user-license-agreement\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u002Fend-user-license-agreement\u002F\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n","Get latest error log messages to diagnose website problems. Define and fix issues faster.",6000,95464,96,9,"2025-12-03T11:15:00.000Z","6.9.4","6.2",[80,81,82,65,83],"add-debug-tool","debug-tool","error-log","php-error-log","https:\u002F\u002Fbestwebsoft.com\u002Fproducts\u002Fwordpress\u002Fplugins\u002Ferror-log-viewer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-log-viewer.1.1.8.zip",5,"2025-10-10 20:39:18",{"slug":89,"name":90,"version":91,"author":92,"author_profile":93,"description":94,"short_description":95,"active_installs":96,"downloaded":97,"rating":74,"num_ratings":98,"last_updated":99,"tested_up_to":100,"requires_at_least":101,"requires_php":23,"tags":102,"homepage":106,"download_link":107,"security_score":108,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"bugfu-console-debugger","BugFu Console Debugger","1.3.0","Federico Andrioli","https:\u002F\u002Fprofiles.wordpress.org\u002Ffedeandri\u002F","\u003Cp>Log\u002FDebug the PHP code in your Theme\u002FPlugin with your Browser Console (no extension needed). Made for themes and plugins developers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>HOW TO CHECK IF BUGFU IS WORKING\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Open your Browser Console, if you see this header, BugFu is working properly\u003C\u002Fp>\n\u003Cpre>\u003Ccode>################################\n#### BugFu Console Debugger ####\n################################\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>HOW TO OPEN YOUR BROWSER JAVASCRIPT CONSOLE\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you’ve never used the Browser JavaScript Console before, here’s how you open it:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Chrome PC shift+ctrl+j – Chrome Mac alt+cmd+j\u003C\u002Fli>\n\u003Cli>Firefox PC shift+ctrl+k – Firefox Mac alt+cmd+k\u003C\u002Fli>\n\u003Cli>Safari PC shift+ctrl+c – Safari Mac alt+cmd+c\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>HOW TO USE BUGFU WITH WORDPRESS\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Call the log static method from wherever you are within the WordPress PHP code\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php \u002F* WORDPRESS CODE HERE *\u002F\n\n\u002F* Call it with no arguments to only output some backtrace info *\u002F\nBugFu::log();\n\n\u002F* Call it with a string argument to output that string content *\u002F\nBugFu::log($my_string_content);\n\n\u002F* Call it with a non-string argument to output the structured\n   representation of that argument - it uses var_export() *\u002F\nBugFu::log($my_object-array-variable);\n\n\u002F* Call it with the second optional argument set to \"false\"\n   to turn off the backtrace info (which is on by default) *\u002F\nBugFu::log($my_content, false);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>DEVELOPERS\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Official Github repository:\u003Cbr \u002F>\nhttps:\u002F\u002Fgithub.com\u002Ffedeandri\u002Fbugfu-console-debugger\u003C\u002Fp>\n","Log\u002FDebug the PHP code in your Theme\u002FPlugin with your Browser Console (no extension needed)",300,10352,17,"2023-01-17T15:02:00.000Z","6.1.10","3.8",[103,104,20,105,21],"debug","debug-bar","log","https:\u002F\u002Fgithub.com\u002Ffedeandri\u002Fbugfu-console-debugger","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbugfu-console-debugger.1.3.zip",85,{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":13,"downloaded":117,"rating":13,"num_ratings":118,"last_updated":119,"tested_up_to":120,"requires_at_least":121,"requires_php":23,"tags":122,"homepage":126,"download_link":127,"security_score":108,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"display-wp-mail-error-messages","Display wp_mail Error Messages","1.0","WonderPlugin","https:\u002F\u002Fprofiles.wordpress.org\u002Fwonderplugin\u002F","\u003Cp>\u003Cstrong>Display wp_mail Error Messages\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Many plugins use the WordPress function \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Ffunctions\u002Fwp_mail\u002F\" rel=\"nofollow ugc\">wp_mail\u003C\u002Fa> to send emails. When an error happens, it’s hard to locate the problem. This plugin will catch the wp_mail error messages and display them.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Easy to use\u003C\u002Fli>\n\u003Cli>Automatically clear the log when it exceeds the defined maximum length limit.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>How to Use\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>After the plugin is installed and activated, in the WordPress backend, goto the left menu WP Error Messages -> Show Errors.\u003C\u002Fp>\n","Display wp_mail error messages",5895,3,"2023-12-05T23:35:00.000Z","6.4.8","3.6",[123,124,125],"error-messages","phpmailer","wp_mail","https:\u002F\u002Fwww.wonderplugin.com\u002Fdisplay-wordpress-error-messages\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisplay-wp-mail-error-messages.zip",{"slug":129,"name":130,"version":131,"author":132,"author_profile":133,"description":134,"short_description":135,"active_installs":13,"downloaded":136,"rating":137,"num_ratings":86,"last_updated":138,"tested_up_to":139,"requires_at_least":140,"requires_php":23,"tags":141,"homepage":23,"download_link":142,"security_score":108,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"safe-mode","Safe Mode","1.1.3","Uffe Fey","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpkonsulent\u002F","\u003Cp>This plugin enables safe mode for WordPress. This means:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>No plugins will be loaded.\u003C\u002Fli>\n\u003Cli>A default theme will be temporarily activated (if it is installed).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why is this useful?\u003C\u002Fh4>\n\u003Cp>Whenever something’s wrong with a WordPress site, the first rule of thumb is to disable plugins and revert to the default theme if possible. Depending on the nature of the error, that is not always an option. The back end (dashboard) may also be down or you may not have FTP access to manually disable plugins and themes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enter Safe Mode\u003C\u002Fstrong>. Safe Mode will completely disable all plugins and the active theme temporarily for a single page view – ultimately enabling you to log in and remove the offending plugin. (This is not guaranteed to work in all scenarios, please read the disclaimer)\u003C\u002Fp>\n\u003Ch4>How does it work?\u003C\u002Fh4>\n\u003Cp>If your site crashes due to an upsetting plugin or theme, all you have to do is add a querystring parameter to the URL. Doing that will temporarily disable all plugins for that single page view, as well as temporarily activate a default theme if one is installed.\u003C\u002Fp>\n\u003Cp>Let’s say you’re the owner of www.example.com. To enable safe mode for one particular page, you add this to the URL: “?safe_mode=1”.\u003C\u002Fp>\n\u003Cp>Bear in mind that you have to do this for every view. The querystring parameter isn’t carried on automatically. So, for instance:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If you need to log in, go to: www.example.com\u002Fwp-admin\u002F?safe_mode=1\u003C\u002Fli>\n\u003Cli>If you need to go to plugin management, go to: www.example.com\u002Fwp-admin\u002Fplugins.php?safe_mode=1\u003C\u002Fli>\n\u003Cli>If you need to go to theme management, go to: www.example.com\u002Fwp-admin\u002Fthemes.php?safe_mode=1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When you go to plugin management, all plugins will seem to be deactivated (due to the way Safe Mode works), but you’ll still be able to explicitly deactivate each plugin. Just use the “Deactivate (safe mode)” option.\u003C\u002Fp>\n\u003Ch4>What are default themes?\u003C\u002Fh4>\n\u003Cp>By default theme, I’m referring to the themes that ships with WordPress, you know, the Twenty “something” ones.\u003C\u002Fp>\n\u003Cp>The plugin checks if any of these themes are installed, and if so, activates the first theme it encounters. Thus I highly recommend that you keep one of those themes installed at all times. If you don’t, safe mode will keep your current active theme, and that theme may just be the offender – leaving safe mode useless. Keep this in mind.\u003C\u002Fp>\n\u003Ch4>Disclaimer\u003C\u002Fh4>\n\u003Cp>This plugin will be able to handle many scenarios, but not all. If your site’s crash is caused by a database crash, or something that simply brings down the PHP parser, like a call to an undefined function, Safe Mode won’t be able to do anything about that.\u003C\u002Fp>\n","Makes it possible to enable safe mode for WordPress. In safe mode, plugins will not be loaded and the default theme (if installed) will be activated.",7841,84,"2018-12-20T10:23:00.000Z","5.0.25","3.0.1",[103,20,22,129],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsafe-mode.zip",{"attackSurface":144,"codeSignals":162,"taintFlows":174,"riskAssessment":175,"analyzedAt":187},{"hooks":145,"ajaxHandlers":158,"restRoutes":159,"shortcodes":160,"cronEvents":161,"entryPointCount":26,"unprotectedCount":26},[146,152],{"type":147,"name":148,"callback":149,"file":150,"line":151},"filter","query","filter_query","src\u002FKunoichi\u002FHagakure\u002FDbLogger.php",24,{"type":147,"name":153,"callback":154,"priority":155,"file":156,"line":157},"log_query_custom_data","log_query",9999,"src\u002FKunoichi\u002FHagakure\u002FSlowQuery.php",26,[],[],[],[],{"dangerousFunctions":163,"sqlUsage":169,"outputEscaping":171,"fileOperations":62,"externalRequests":26,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":173},[164],{"fn":165,"file":166,"line":167,"context":168},"ini_set","src\u002FKunoichi\u002FHagakure\u002FCommand.php",60,"if ( false === ini_set( 'memory_limit', $limit ) ) {",{"prepared":26,"raw":26,"locations":170},[],{"escaped":26,"rawEcho":26,"locations":172},[],[],[],{"summary":176,"deductions":177},"The \"hagakure\" plugin version 1.3.2 presents a generally positive security posture with several strengths. The absence of known vulnerabilities, coupled with a clean taint analysis and a high percentage of SQL queries using prepared statements and output escaping, indicates good development practices in these critical areas. Furthermore, the plugin has no recorded history of vulnerabilities, which is a strong indicator of its historical stability. The static analysis also reveals a minimal attack surface with zero AJAX handlers, REST API routes, shortcodes, or cron events, and importantly, no unprotected entry points. This significantly reduces the potential for direct exploitation.\n\nHowever, there are a few areas that warrant attention. The presence of the `ini_set` function, while not inherently a vulnerability, can sometimes be misused or indicate less secure coding practices, especially if not used in a controlled environment. The static analysis also flags a file operation, which, without further context, could represent a risk if not handled with proper sanitization and permission checks. The lack of nonce checks and capability checks on any potential entry points is also a notable concern, as these are fundamental security measures for WordPress plugins to prevent cross-site request forgery (CSRF) and unauthorized actions. The absence of these checks, even with a currently small attack surface, leaves the plugin vulnerable if any new entry points are introduced in the future or if existing ones are not adequately secured by other means (which is not evident from the provided data).\n\nIn conclusion, the \"hagakure\" plugin has a strong foundation with excellent protection against common web vulnerabilities like SQL injection and XSS, and a negligible attack surface. Its vulnerability history is pristine. The main areas for improvement lie in implementing standard WordPress security checks such as nonces and capability checks, and careful scrutiny of the file operation and `ini_set` usage to ensure they are implemented securely and do not introduce unforeseen risks.",[178,181,183,185],{"reason":179,"points":180},"Missing nonce checks",10,{"reason":182,"points":180},"Missing capability checks",{"reason":184,"points":86},"Presence of dangerous function 'ini_set'",{"reason":186,"points":118},"File operations present","2026-04-16T11:19:41.177Z",{"wat":189,"direct":194},{"assetPaths":190,"generatorPatterns":191,"scriptPaths":192,"versionParams":193},[],[],[],[],{"cssClasses":195,"htmlComments":196,"htmlAttributes":197,"restEndpoints":198,"jsGlobals":199,"shortcodeOutput":200},[],[],[],[],[],[],{"error":202,"url":203,"statusCode":204,"statusMessage":205,"message":205},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fhagakure\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":207,"versions":208},8,[209,215,222,228,235,242,249,256],{"version":6,"download_url":24,"svn_tag_url":210,"released_at":27,"has_diff":211,"diff_files_changed":212,"diff_lines":27,"trac_diff_url":213,"vulnerabilities":214,"is_current":202},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F1.3.2\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhagakure%2Ftags%2F1.3.1&new_path=%2Fhagakure%2Ftags%2F1.3.2",[],{"version":216,"download_url":217,"svn_tag_url":218,"released_at":27,"has_diff":211,"diff_files_changed":219,"diff_lines":27,"trac_diff_url":220,"vulnerabilities":221,"is_current":211},"1.3.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.1.3.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F1.3.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhagakure%2Ftags%2F1.3.0&new_path=%2Fhagakure%2Ftags%2F1.3.1",[],{"version":91,"download_url":223,"svn_tag_url":224,"released_at":27,"has_diff":211,"diff_files_changed":225,"diff_lines":27,"trac_diff_url":226,"vulnerabilities":227,"is_current":211},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.1.3.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F1.3.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhagakure%2Ftags%2F1.2.0&new_path=%2Fhagakure%2Ftags%2F1.3.0",[],{"version":229,"download_url":230,"svn_tag_url":231,"released_at":27,"has_diff":211,"diff_files_changed":232,"diff_lines":27,"trac_diff_url":233,"vulnerabilities":234,"is_current":211},"1.2.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.1.2.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F1.2.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhagakure%2Ftags%2F1.1.0&new_path=%2Fhagakure%2Ftags%2F1.2.0",[],{"version":236,"download_url":237,"svn_tag_url":238,"released_at":27,"has_diff":211,"diff_files_changed":239,"diff_lines":27,"trac_diff_url":240,"vulnerabilities":241,"is_current":211},"1.1.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.1.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F1.1.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhagakure%2Ftags%2F1.0.4&new_path=%2Fhagakure%2Ftags%2F1.1.0",[],{"version":243,"download_url":244,"svn_tag_url":245,"released_at":27,"has_diff":211,"diff_files_changed":246,"diff_lines":27,"trac_diff_url":247,"vulnerabilities":248,"is_current":211},"1.0.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.1.0.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F1.0.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhagakure%2Ftags%2F1.0.3&new_path=%2Fhagakure%2Ftags%2F1.0.4",[],{"version":250,"download_url":251,"svn_tag_url":252,"released_at":27,"has_diff":211,"diff_files_changed":253,"diff_lines":27,"trac_diff_url":254,"vulnerabilities":255,"is_current":211},"1.0.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.1.0.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F1.0.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhagakure%2Ftags%2F0.8.0&new_path=%2Fhagakure%2Ftags%2F1.0.3",[],{"version":257,"download_url":258,"svn_tag_url":259,"released_at":27,"has_diff":211,"diff_files_changed":260,"diff_lines":27,"trac_diff_url":27,"vulnerabilities":261,"is_current":211},"0.8.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhagakure.0.8.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhagakure\u002Ftags\u002F0.8.0\u002F",[],[]]