[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fd9_SQtTZwIysDEfu63aIJ8y3gEoaKzJRq6E8HWAXSZo":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":38,"analysis":146,"fingerprints":223},"kagg-compatibility","KAGG Compatibility","2.5.0","kaggdesign","https:\u002F\u002Fprofiles.wordpress.org\u002Fkaggdesign\u002F","\u003Cp>\u003Ca href=\"https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002Fhandbook\u002Freferences\u002Fphp-compatibility-and-wordpress-versions\u002F\" rel=\"nofollow ugc\">WordPress is not fully compatible with PHP 8.0-8.5\u003C\u002Fa>. The remaining known PHP 8.0+ issues are deprecation notices.\u003C\u002Fp>\n\u003Cp>The same is related to many popular plugins such as WooCommerce, Jetpack, Gravity Forms, and others. Mainly, they produce deprecation notices from the Action Scheduler library.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>The plugin blocks deprecation notices, user deprecation notices, notices, warnings, user notices, and user warnings.\u003C\u002Fli>\n\u003Cli>The list of folders from which errors are blocked can be filtered. This list may specify any WordPress Core, plugin, and theme folders.\u003C\u002Fli>\n\u003Cli>Plugin filters out errors from these folders only. Errors produced by other code are not blocked, which helps in debugging user code.\u003C\u002Fli>\n\u003Cli>During activation, the plugin installs a mu-plugin \u003Ccode>kagg-compatibility-error-handler.php\u003C\u002Fcode> into the \u003Ccode>\u002Fwp-content\u002Fmu-plugins\u002F\u003C\u002Fcode> folder. It contains the error handler, which loads earlier than any plugin or theme.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Plugin Support\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fkagg-compatibility\u002F\" rel=\"ugc\">Support Forum\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","The plugin blocks error messages of any level from WordPress core, plugins, and themes.",10,3538,100,2,"2026-03-03T19:10:00.000Z","6.9.4","6.0","7.4",[20,21,22,23,24],"compatibility","deprecated","development","notice","warning","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fkagg-compatibility\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkagg-compatibility.2.5.0.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},4,2230,98,30,93,"2026-04-04T15:30:00.461Z",[39,64,86,106,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":54,"tags":55,"homepage":59,"download_link":60,"security_score":61,"vuln_count":62,"unpatched_count":27,"last_vuln_date":63,"fetched_at":29},"wp-post-disclaimer","WP Post Disclaimer","1.0.4","Krunal Prajapati","https:\u002F\u002Fprofiles.wordpress.org\u002Fkrunalprajapati41\u002F","\u003Cp>Add a disclaimer\u002Fterms\u002Fwarnings about post\u002Fpage\u002Fcustom post type on top, bottom of content as well as inside post content\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Disclaimer on Post\u002FPage or Custom Post Type\u003C\u002Fli>\n\u003Cli>Customized Options\u003C\u002Fli>\n\u003Cli>Custom CSS Option\u003C\u002Fli>\n\u003Cli>Individual Post\u002FPage or Custom Post Type Options\u003C\u002Fli>\n\u003Cli>Font Awesome Icons\u003C\u002Fli>\n\u003Cli>Use with Shortcode\u003C\u002Fli>\n\u003C\u002Ful>\n","Add customizable disclaimers, terms, or warnings to the top, bottom, or within post, page, or custom post type content for WordPress",2000,17730,96,9,"2025-01-07T06:21:00.000Z","6.7.5","3.6","5.2.4",[56,57,23,58,24],"alert","dislaimer","post-disclaimer","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-post-disclaimer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-post-disclaimer.1.0.4.zip",92,1,"2024-03-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":13,"num_ratings":11,"last_updated":74,"tested_up_to":75,"requires_at_least":76,"requires_php":77,"tags":78,"homepage":83,"download_link":84,"security_score":85,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"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,165887,"2021-06-25T14:17:00.000Z","5.8.13","3.0","",[79,21,80,81,82],"admin","e_notice","logging","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",85,{"slug":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":72,"downloaded":94,"rating":61,"num_ratings":95,"last_updated":96,"tested_up_to":16,"requires_at_least":97,"requires_php":18,"tags":98,"homepage":102,"download_link":103,"security_score":104,"vuln_count":14,"unpatched_count":27,"last_vuln_date":105,"fetched_at":29},"wp-browser-update","WP BrowserUpdate","5.1.1","MacSteini","https:\u002F\u002Fprofiles.wordpress.org\u002Fmacsteini\u002F","\u003Cp>Many users still browse with outdated browsers, often unaware of the risks. Upgrading ensures better security and reliability. This plugin displays a subtle notification prompting visitors to update their browser. Activate the plugin, and it works seamlessly.\u003C\u002Fp>\n\u003Cp>Visit \u003Ca href=\"https:\u002F\u002Fbrowserupdate.org\u002F\" rel=\"nofollow ugc\">browserupdate.org\u003C\u002Fa> for more details.\u003C\u002Fp>\n\u003Cp>Want to help translate this plugin? Visit the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-browser-update\" rel=\"nofollow ugc\">WordPress Translation Project\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Important Notice\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Breaking Changes in Version 5.0.0\u003C\u002Fstrong>\u003Cbr \u002F>\n– Requires \u003Cstrong>PHP 7.4\u003C\u002Fstrong> or newer.\u003Cbr \u002F>\n– Ensure your hosting is updated to PHP 7.4 before upgrading to version 5.0.0 or newer.\u003Cbr \u002F>\n– Servers running older PHP versions are no longer supported.\u003Cbr \u002F>\n  – If your server is running an earlier PHP version, please download \u003Ca href=\"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-browser-update.4.8.1.zip\" title=\"Download WP BrowserUpdate from WordPress.org\" rel=\"nofollow ugc\">version 4.8.1\u003C\u002Fa>.\u003C\u002Fp>\n","This plugin notifies website visitors to update their outdated browser in a non-intrusive way.",131279,16,"2026-02-20T22:54:00.000Z","4.6",[99,23,100,101,24],"browser","outdated","update","https:\u002F\u002Fwpbu.steinbrecher.co\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-browser-update.5.1.1.zip",99,"2023-04-26 00:00:00",{"slug":107,"name":108,"version":109,"author":110,"author_profile":111,"description":112,"short_description":113,"active_installs":114,"downloaded":115,"rating":13,"num_ratings":116,"last_updated":117,"tested_up_to":118,"requires_at_least":119,"requires_php":77,"tags":120,"homepage":126,"download_link":127,"security_score":85,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"caspers-leave-notice","Casper’s Leave Notice","1.2.3","XAce90","https:\u002F\u002Fprofiles.wordpress.org\u002Fxace90\u002F","\u003Cp>Casper’s Leave Notice warns your users when they are about to leave your website. All you have to do is install and activate, and the plugin does the rest! You can edit the content that shows up in the pop up window to fine tune the message your users see. You can also add domain names to exclude from the pop up.\u003C\u002Fp>\n\u003Cp>For example, if a link sends your users to a third party tool – like a shopping cart – just add the domain to the exclusion list and your guests will be none the wiser.\u003C\u002Fp>\n","A quick, easy way to notify your users when they are leaving your site. You can edit the content and add domain exclusions.",300,4336,5,"2019-07-18T18:51:00.000Z","5.2.24","4.0",[121,122,123,124,125],"exit-warning","external-links","leaving-notification","pop-up-disclaimer","site-abandonment-notice","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcaspers-leave-notice\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcaspers-leave-notice.zip",{"slug":129,"name":130,"version":131,"author":132,"author_profile":133,"description":134,"short_description":135,"active_installs":13,"downloaded":136,"rating":13,"num_ratings":62,"last_updated":137,"tested_up_to":16,"requires_at_least":138,"requires_php":18,"tags":139,"homepage":144,"download_link":145,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"eli-php-compatibility-scanner","Eli's PHP Compatibility Scanner","1.1.1","Eli Hanna","https:\u002F\u002Fprofiles.wordpress.org\u002Feliehanna\u002F","\u003Cp>\u003Cstrong>⚠️ Important: Development Environment Only\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin is designed for development environments like LocalWP, XAMPP, or self-hosted servers. It will \u003Cstrong>not work\u003C\u002Fstrong> on most managed hosting providers (WP Engine, Kinsta, SiteGround, etc.) due to security restrictions that disable the \u003Ccode>exec()\u003C\u002Fcode> function and limit access to PHP binaries.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How It Works\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin leverages \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsquizlabs\u002FPHP_CodeSniffer\" rel=\"nofollow ugc\">PHP_CodeSniffer\u003C\u002Fa> with the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FPHPCompatibility\u002FPHPCompatibility\" rel=\"nofollow ugc\">PHPCompatibility\u003C\u002Fa> standard to perform deep static analysis of your PHP code.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Core Components:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Bundled Dependencies\u003C\u002Fstrong>: Includes PHP_CodeSniffer and PHPCompatibility ruleset\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Batch Processing\u003C\u002Fstrong>: Scans files in configurable batches (10-100 files) to manage memory usage\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Command Execution\u003C\u002Fstrong>: Executes PHPCS via PHP’s \u003Ccode>exec()\u003C\u002Fcode> function with specific parameters\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Server-Side State\u003C\u002Fstrong>: Stores file lists in WordPress options to optimize AJAX requests\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Progressive UI\u003C\u002Fstrong>: Real-time batch results with stop\u002Fstart controls\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>How to Use:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Navigate to \u003Cstrong>Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> PHP Compatibility Scanner\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Review the \u003Cstrong>System Check\u003C\u002Fstrong> section to ensure your environment is compatible\u003C\u002Fli>\n\u003Cli>Select the \u003Cstrong>plugins and\u002For themes\u003C\u002Fstrong> you want to scan by checking their boxes\u003C\u002Fli>\n\u003Cli>Configure your scan options:\n\u003Cul>\n\u003Cli>\u003Cstrong>Target PHP Version\u003C\u002Fstrong>: Choose the PHP version you want to test against (7.4 – 8.4)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Batch Size\u003C\u002Fstrong>: Select how many files to process at once (default: 50 files)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Skip Vendor Directory\u003C\u002Fstrong>: Keep checked to skip third-party dependencies\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Start Scan\u003C\u002Fstrong> to begin the compatibility check\u003C\u002Fli>\n\u003Cli>View results in real-time as each plugin\u002Ftheme is scanned\u003C\u002Fli>\n\u003Cli>Review any \u003Cstrong>errors\u003C\u002Fstrong> (❌) or \u003Cstrong>warnings\u003C\u002Fstrong> (⚠️) found in your code\u003C\u002Fli>\n\u003Cli>Click on any target to expand and see detailed compatibility issues\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Why It Requires Development Environments\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>exec()\u003C\u002Fcode> Function\u003C\u002Fstrong>: Required to run PHPCS binary – disabled on managed hosts\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PHP Binary Access\u003C\u002Fstrong>: Needs access to PHP executable – restricted on shared hosting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Composer Dependencies\u003C\u002Fstrong>: Requires vendor directory with PHPCS installation\u003C\u002Fli>\n\u003Cli>\u003Cstrong>File System Access\u003C\u002Fstrong>: Creates temporary files for batch processing\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Memory\u002FTime Limits\u003C\u002Fstrong>: Long-running scans need relaxed execution limits\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Supported Environments\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>LocalWP\u003C\u002Fstrong> (recommended)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>XAMPP\u002FMAMP\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Docker WordPress\u003C\u002Fstrong> setups\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Self-hosted\u003C\u002Fstrong> VPS\u002Fdedicated servers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Development\u003C\u002Fstrong> environments with shell access\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Unsupported Environments\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP Engine\u003C\u002Fstrong> (exec() disabled)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Kinsta\u003C\u002Fstrong> (security restrictions)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SiteGround\u003C\u002Fstrong> (managed hosting limitations)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>GoDaddy Managed WordPress\u003C\u002Fstrong> (function restrictions)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WordPress.com\u003C\u002Fstrong> (no plugin uploads)\u003C\u002Fli>\n\u003Cli>Most \u003Cstrong>shared hosting\u003C\u002Fstrong> providers\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Contributing\u003C\u002Fh3>\n\u003Cp>This plugin is actively developed for WordPress development environments. Contributions are welcome, especially:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Additional PHP version compatibility rules\u003C\u002Fli>\n\u003Cli>Performance optimizations\u003C\u002Fli>\n\u003Cli>UI\u002FUX improvements\u003C\u002Fli>\n\u003Cli>Hosted environment compatibility solutions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Technical Details\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Dependencies\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>PHP_CodeSniffer\u003C\u002Fstrong>: ^3.13 (static analysis engine)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PHPCompatibility\u003C\u002Fstrong>: dev-develop (compatibility ruleset)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>License\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>GPLv2 or later – same as WordPress core.\u003C\u002Fp>\n","A comprehensive WordPress plugin that scans your plugins and themes for PHP version compatibility issues using the  PHPCompatibility ruleset.",891,"2026-03-09T20:55:00.000Z","4.5",[140,20,141,142,143],"code-quality","phpcs","testing","wordpress-development","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feli-php-compatibility-scanner","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feli-php-compatibility-scanner.1.1.1.zip",{"attackSurface":147,"codeSignals":206,"taintFlows":214,"riskAssessment":215,"analyzedAt":222},{"hooks":148,"ajaxHandlers":202,"restRoutes":203,"shortcodes":204,"cronEvents":205,"entryPointCount":27,"unprotectedCount":27},[149,155,160,163,167,170,174,179,183,186,190,194,199],{"type":150,"name":151,"callback":152,"file":153,"line":154},"action","admin_notices","show_notices","src\\php\\AdminNotices.php",26,{"type":150,"name":156,"callback":156,"priority":157,"file":158,"line":159},"plugin_loaded",500,"src\\php\\kagg-compatibility-error-handler.php",125,{"type":150,"name":161,"callback":161,"priority":157,"file":158,"line":162},"plugins_loaded",126,{"type":150,"name":164,"callback":165,"priority":157,"file":158,"line":166},"action_scheduler_before_execute","set_error_handler",127,{"type":150,"name":168,"callback":168,"file":158,"line":169},"admin_head",134,{"type":150,"name":161,"callback":171,"file":172,"line":173},"load","src\\php\\Main.php",77,{"type":150,"name":175,"callback":176,"priority":50,"file":177,"line":178},"current_screen","setup_tabs_section","src\\php\\Settings\\Abstracts\\SettingsBase.php",197,{"type":150,"name":180,"callback":181,"file":177,"line":182},"admin_menu","add_settings_page",198,{"type":150,"name":175,"callback":184,"file":177,"line":185},"setup_fields",229,{"type":150,"name":175,"callback":187,"priority":188,"file":177,"line":189},"setup_sections",11,230,{"type":150,"name":191,"callback":192,"file":177,"line":193},"admin_enqueue_scripts","base_admin_enqueue_scripts",235,{"type":195,"name":196,"callback":196,"file":197,"line":198},"filter","admin_footer_text","src\\php\\Settings\\PluginSettingsBase.php",54,{"type":195,"name":200,"callback":200,"file":197,"line":201},"update_footer",55,[],[],[],[],{"dangerousFunctions":207,"sqlUsage":208,"outputEscaping":210,"fileOperations":14,"externalRequests":27,"nonceChecks":27,"capabilityChecks":27,"bundledLibraries":213},[],{"prepared":27,"raw":27,"locations":209},[],{"escaped":211,"rawEcho":27,"locations":212},79,[],[],[],{"summary":216,"deductions":217},"The \"kagg-compatibility\" plugin v2.5.0 exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points suggests a minimal attack surface. The code signals are also positive, with no dangerous functions, 100% of SQL queries using prepared statements, and all output properly escaped. The lack of external HTTP requests and file operations further contributes to its secure design.  The vulnerability history is also clear, with zero known CVEs, indicating a consistent track record of security. However, the complete absence of nonce checks and capability checks on all entry points, though currently not exploitable due to the lack of entry points, represents a potential future risk if functionality is added without proper security controls.  While the current state is highly secure, future development should prioritize robust authentication and authorization mechanisms to maintain this high standard.",[218,220],{"reason":219,"points":116},"Missing nonce checks",{"reason":221,"points":116},"Missing capability checks","2026-03-16T23:44:27.910Z",{"wat":224,"direct":233},{"assetPaths":225,"generatorPatterns":228,"scriptPaths":229,"versionParams":230},[226,227],"\u002Fwp-content\u002Fplugins\u002Fkagg-compatibility\u002Fsrc\u002Fcss\u002Fsettings.css","\u002Fwp-content\u002Fplugins\u002Fkagg-compatibility\u002Fsrc\u002Fjs\u002Fsettings.js",[],[227],[231,232],"kagg-compatibility\u002Fsrc\u002Fcss\u002Fsettings.css?ver=","kagg-compatibility\u002Fsrc\u002Fjs\u002Fsettings.js?ver=",{"cssClasses":234,"htmlComments":237,"htmlAttributes":238,"restEndpoints":240,"jsGlobals":241,"shortcodeOutput":243},[235,236],"kagg-settings-wrapper","kagg-settings-field-wrapper",[],[239],"data-kagg-settings-field-wrapper",[],[242],"KAGG_SETTINGS_BASE_HANDLE",[]]