[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$faMjOeD56eDM4QhdYSAd5iWz_sJ_jLbthp3cOdktGCQY":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":36,"analysis":137,"fingerprints":199},"inquirer","Inquirer","0.1.0","Sergio Scabuzzo","https:\u002F\u002Fprofiles.wordpress.org\u002Fseedsca\u002F","\u003Cp>When running a an audit on a website (yours, a competiror, or client), you can often find yourself going to around ten or more websites to run tests (Inquiries).\u003Cbr \u002F>\nAt each of these you then paste the same URL and run it’s test and repeat for each one. Most of these services use the GET HTTP request method. You see these as the \u003Cstrong>?q=\u003C\u002Fstrong> part in \u003Ca href=\"https:\u002F\u002Fduckduckgo.com\u002F?q=ecotechie\" rel=\"nofollow ugc\">https:\u002F\u002Fduckduckgo.com\u002F?q=ecotechie\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>I decided to write this plugin so I could input a URL once and run all of these tests more easily. No need to hunt down the website addressses or even leave the WordPress admin dashboard!\u003C\u002Fp>\n\u003Cp>Features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Use any valid URL for testing, it doesn’t have to be the current site the plugin is installed on.\u003C\u002Fli>\n\u003Cli>Add or remove websites to use for tests (Inquirers).\u003C\u002Fli>\n\u003Cli>Sortable by filter types like SEO, Speed, Security, etc. Or create your own tags…\u003C\u002Fli>\n\u003C\u002Ful>\n","Run queries of an arbitrary URL on websites that can take these as query parameters.",0,1359,"2022-01-23T03:34:00.000Z","5.8.13","4.5","5.6",[18,19,20,21,22],"accessibility","audit","performance","queries","tests","https:\u002F\u002Fwww.ecotechie.io\u002Finquirer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Finquirer.0.1.0.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"seedsca",2,40,30,84,"2026-04-04T23:27:46.140Z",[37,56,77,100,119],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":11,"downloaded":45,"rating":11,"num_ratings":11,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":49,"download_link":54,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"sitelint","SiteLint – Web Audit Tools","1.5.24","ctomczyk","https:\u002F\u002Fprofiles.wordpress.org\u002Fctomczyk\u002F","\u003Cp>Audit your site today to improve engagement for your audiences! Let SiteLint identify Accessibility, SEO, Performance, Security, Privacy, Technical issues in one click!\u003C\u002Fp>\n","Client-side & real-time checker for Accessibility, SEO, Performance, Security, Privacy, Technical issues.",3026,"2026-02-25T10:42:00.000Z","6.9.4","4.7","",[18,51,52,20,53],"audits","automated","seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsitelint.1.5.24.zip",100,{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":66,"num_ratings":67,"last_updated":68,"tested_up_to":47,"requires_at_least":69,"requires_php":70,"tags":71,"homepage":75,"download_link":76,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"plugin-check","Plugin Check (PCP)","1.8.0","WordPress.org","https:\u002F\u002Fprofiles.wordpress.org\u002Fwordpressdotorg\u002F","\u003Cp>Plugin Check is a tool for testing whether your plugin meets the required standards for the WordPress.org plugin directory. With this plugin you will be able to run most of the checks used for new submissions, and check if your plugin meets the requirements.\u003C\u002Fp>\n\u003Cp>Additionally, the tool flags violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices.\u003C\u002Fp>\n\u003Cp>The checks can be run either using the WP Admin user interface or WP-CLI:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>To check a plugin using WP Admin, please navigate to the \u003Cem>Tools > Plugin Check\u003C\u002Fem> menu. You need to be able to manage plugins on your site in order to access that screen.\u003C\u002Fli>\n\u003Cli>To check a plugin using WP-CLI, please use the \u003Ccode>wp plugin check\u003C\u002Fcode> command. For example, to check the “Hello Dolly” plugin: \u003Ccode>wp plugin check hello.php\u003C\u002Fcode>\n\u003Cul>\n\u003Cli>Note that by default when using WP-CLI, only static checks can be executed. In order to also include runtime checks, a workaround is currently necessary using the \u003Ccode>--require\u003C\u002Fcode> argument of WP-CLI, to manually load the \u003Ccode>cli.php\u003C\u002Fcode> file within the plugin checker directory before WordPress is loaded. For example: \u003Ccode>wp plugin check hello.php --require=.\u002Fwp-content\u002Fplugins\u002Fplugin-check\u002Fcli.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>You could use arbitrary path or URL to check a plugin. For example, to check a plugin from a URL: \u003Ccode>wp plugin check https:\u002F\u002Fexample.com\u002Fplugin.zip\u003C\u002Fcode> or to check a plugin from a path: \u003Ccode>wp plugin check \u002Fpath\u002Fto\u002Fplugin\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The checks are grouped into several categories, so that you can customize which kinds of checks you would like to run on a plugin.\u003C\u002Fp>\n\u003Cp>Keep in mind that this plugin is not a replacement for the manual review process, but it will help you speed up the process of getting your plugin approved for the WordPress.org plugin repository, and it will also help you avoid some common mistakes.\u003C\u002Fp>\n\u003Cp>Even if you do not intend to host your plugin in the WordPress.org directory, you are encouraged to use Plugin Check so that your plugin follows the base requirements and best practices for WordPress plugins.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Plugin Namer Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Plugin Check now includes an AI-powered Plugin Namer tool (accessible via \u003Cem>Tools > Plugin Check Namer\u003C\u002Fem>) that helps plugin authors evaluate plugin names before submission. This tool checks for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Similarity to existing plugins in the WordPress.org directory\u003C\u002Fli>\n\u003Cli>Potential trademark conflicts with well-known brands\u003C\u002Fli>\n\u003Cli>Compliance with WordPress plugin naming guidelines\u003C\u002Fli>\n\u003Cli>Generic or overly broad naming issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The Plugin Namer provides instant feedback with actionable suggestions, helping you choose a clear, unique, and policy-compliant name that stands out in the plugin directory. This feature requires AI provider configuration in the settings.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important:\u003C\u002Fstrong> The Plugin Namer tool provides guidance only and is not definitive. All plugin name decisions are subject to final review and approval by the WordPress.org Plugins team reviewers.\u003C\u002Fp>\n","Plugin Check is a WordPress.org tool which provides checks to help plugins meet the directory requirements and follow various best practices.",7000,714618,90,31,"2025-12-28T11:57:00.000Z","6.3","7.4",[18,20,72,73,74],"plugin-best-practices","security","testing","https:\u002F\u002Fgithub.com\u002FWordPress\u002Fplugin-check","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-check.1.8.0.zip",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":84,"active_installs":85,"downloaded":86,"rating":55,"num_ratings":87,"last_updated":88,"tested_up_to":47,"requires_at_least":89,"requires_php":70,"tags":90,"homepage":95,"download_link":96,"security_score":97,"vuln_count":98,"unpatched_count":11,"last_vuln_date":99,"fetched_at":27},"wpgraphql-smart-cache","WPGraphQL Smart Cache","2.0.1","Jason Bahl","https:\u002F\u002Fprofiles.wordpress.org\u002Fjasonbahl\u002F","\u003Cp>Do you want your API data \u003Cem>fast\u003C\u002Fem> or \u003Cem>accurate\u003C\u002Fem>? With WPGraphQL Smart Cache, you can have both.\u003C\u002Fp>\n\u003Cp>WPGraphQL Smart Cache is a free, open-source WordPress plugin that provides support for caching and cache invalidation of WPGraphQL Queries.\u003C\u002Fp>\n\u003Cp>To get the most out of this plugin, we recommend using GET requests with Network Caching, which requires your WordPress install to be on a \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache\u002Fblob\u002Fmain\u002Fdocs\u002Fnetwork-cache.md#supported-hosts\" rel=\"nofollow ugc\">supported host\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>BREAKING CHANGES:\u003C\u002Fem> We may make breaking changes in the future to improve functionality and experience. If we do, we will use semver to do so. Pay attention to release notes and upgrade notices before updating.\u003C\u002Fp>\n\u003Ch3>Video Overview\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fyoutu.be\u002Ft_y6q02q7K4\" rel=\"nofollow ugc\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Docs\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache#overview\" rel=\"nofollow ugc\">Overview\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache#-quick-start\" rel=\"nofollow ugc\">Quick Start\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Features\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache\u002Fblob\u002Fmain\u002Fdocs\u002Fnetwork-cache.md\" rel=\"nofollow ugc\">Network Cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache\u002Fblob\u002Fmain\u002Fdocs\u002Fobject-cache.md\" rel=\"nofollow ugc\">Object Cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache\u002Fblob\u002Fmain\u002Fdocs\u002Fpersisted-queries.md\" rel=\"nofollow ugc\">Persisted Queries\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache\u002Fblob\u002Fmain\u002Fdocs\u002Fcache-invalidation.md\" rel=\"nofollow ugc\">Cache Invalidation\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache\u002Fblob\u002Fmain\u002Fdocs\u002Fextending.md\" rel=\"nofollow ugc\">Extending \u002F Customizing Functionality\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache#faq--troubleshooting\" rel=\"nofollow ugc\">FAQ and Troubleshooting\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache#known-issues\" rel=\"nofollow ugc\">Known Issues\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache#providing-feedback\" rel=\"nofollow ugc\">Providing Feedback\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Upgrading\u003C\u002Fh4>\n\u003Cp>It is recommended that anytime you want to update WPGraphQL Smart Cache that you get familiar with what’s changed in the release.\u003C\u002Fp>\n\u003Cp>WPGraphQL Smart Cache publishes \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache\u002Freleases\" rel=\"nofollow ugc\">release notes on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>WPGraphQL Smart Cache will follow Semver versioning.\u003C\u002Fp>\n\u003Cp>The summary of Semver versioning is as follows:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>MAJOR\u003C\u002Fem> version when you make incompatible API changes,\u003C\u002Fli>\n\u003Cli>\u003Cem>MINOR\u003C\u002Fem> version when you add functionality in a backwards compatible manner, and\u003C\u002Fli>\n\u003Cli>\u003Cem>PATCH\u003C\u002Fem> version when you make backwards compatible bug fixes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You can read more about the details of Semver at \u003Ca href=\"https:\u002F\u002Fsemver.org\" rel=\"nofollow ugc\">semver.org\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>WPGraphQL Smart Cache uses \u003Ca href=\"https:\u002F\u002Fappsero.com\" rel=\"nofollow ugc\">Appsero\u003C\u002Fa> SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster & make product improvements.\u003C\u002Fp>\n\u003Cp>Appsero SDK \u003Cstrong>does not gather any data by default.\u003C\u002Fstrong> The SDK only starts gathering basic telemetry data \u003Cstrong>when a user allows it via the admin notice\u003C\u002Fstrong>. We collect the data to ensure a great user experience for all our users.\u003C\u002Fp>\n\u003Cp>Integrating Appsero SDK \u003Cstrong>DOES NOT IMMEDIATELY\u003C\u002Fstrong> start gathering data, \u003Cstrong>without confirmation from users in any case.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Learn more about how \u003Ca href=\"https:\u002F\u002Fappsero.com\u002Fprivacy-policy\u002F\" rel=\"nofollow ugc\">Appsero collects and uses this data\u003C\u002Fa>.\u003C\u002Fp>\n","WPGraphQL Smart Cache is a WordPress plugin that provides fast, accurate API responses by intelligently caching and invalidating WPGraphQL queries.",6000,70323,4,"2025-12-12T01:06:00.000Z","6.0",[91,92,20,93,94],"api","cache","persisted-queries","wpgraphql","https:\u002F\u002Fgithub.com\u002Fwp-graphql\u002Fwp-graphql-smart-cache","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwpgraphql-smart-cache.2.0.1.zip",99,1,"2025-12-12 00:00:00",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":108,"downloaded":109,"rating":55,"num_ratings":98,"last_updated":110,"tested_up_to":111,"requires_at_least":112,"requires_php":113,"tags":114,"homepage":117,"download_link":118,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"auto-image-title-alt","Auto Image Title & Alt","2.3.1","Diego de Guindos","https:\u002F\u002Fprofiles.wordpress.org\u002Fdieguraa\u002F","\u003Cp>\u003Cstrong>This plugin automatically improves your SEO by adding Title and Alt Text tags to every new image uploaded to your media library. It cleans the file name from non-alphanumeric characters and uses it as the basis for these tags.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This repetitive manual task can now be fully automated.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>New features and improvements:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Choose which image fields to update: Title, Alt Text, Caption (Excerpt), and Description (Content).\u003C\u002Fli>\n\u003Cli>Select capitalization style for tags: Capitalized (default), lowercase, UPPERCASE, or leave text as-is.\u003C\u002Fli>\n\u003Cli>Rename uploaded files automatically by cleaning and formatting their names, with options to apply renaming to all files, only images, or disable it completely.\u003C\u002Fli>\n\u003Cli>Update image metadata instantly from the Media Library list or the individual image edit screen via a convenient button.\u003C\u002Fli>\n\u003Cli>Lightweight plugin with no impact on site performance.\u003C\u002Fli>\n\u003Cli>Simple settings page in WordPress admin for easy configuration.\u003C\u002Fli>\n\u003Cli>Enhances website accessibility and provides Google with better image context.\u003C\u002Fli>\n\u003Cli>Fully compatible with the latest WordPress versions.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Plugin features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Automatically generate clean, SEO-friendly image titles and alt text based on file names.\u003C\u002Fli>\n\u003Cli>Optionally update caption and description fields.\u003C\u002Fli>\n\u003Cli>Apply capitalization formatting based on your preferences.\u003C\u002Fli>\n\u003Cli>Automatically rename uploaded files with proper handling of accented and special characters.\u003C\u002Fli>\n\u003Cli>Choose to rename all files, only images, or skip renaming altogether.\u003C\u002Fli>\n\u003Cli>Manually trigger updates for existing images directly from the Media Library or image edit screen.\u003C\u002Fli>\n\u003Cli>Saves time by automating tedious manual updates.\u003C\u002Fli>\n\u003Cli>Zero impact on website speed or performance.\u003C\u002Fli>\n\u003C\u002Ful>\n","Automatically adds title and alt tags to new images in the media library, improving SEO and accessibility with customizable fields and capitalization.",400,4695,"2025-07-07T13:34:00.000Z","6.8.5","3.1","5.6.0",[18,115,20,53,116],"images","wpo","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fauto-image-title-alt","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fauto-image-title-alt.2.3.1.zip",{"slug":120,"name":121,"version":122,"author":123,"author_profile":124,"description":125,"short_description":126,"active_installs":127,"downloaded":128,"rating":55,"num_ratings":98,"last_updated":129,"tested_up_to":47,"requires_at_least":16,"requires_php":130,"tags":131,"homepage":135,"download_link":136,"security_score":55,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"sa11y","Sa11y, the accessibility quality assurance assistant | Accessibility Checker","1.2.7","Adam Chaboryk","https:\u002F\u002Fprofiles.wordpress.org\u002Fadamchaboryk\u002F","\u003Cp>Sa11y is an accessibility quality assurance tool that visually highlights common accessibility and usability issues. Geared towards content authors, Sa11y straightforwardly identifies errors or warnings at the source with a simple tooltip on how to fix them.\u003C\u002Fp>\n\u003Cp>Sa11y works in \u003Cstrong>Preview\u003C\u002Fstrong> mode.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Over 80 checks.\u003C\u002Fli>\n\u003Cli>Concise tooltips explain issues right at the source.\u003C\u002Fli>\n\u003Cli>Automatically checks content once the page has loaded.\u003C\u002Fli>\n\u003Cli>Highly customizable. Turn off or hide irrelevant checks.\u003C\u002Fli>\n\u003Cli>Content editors can temporarily dismiss warnings.\u003C\u002Fli>\n\u003Cli>100% free and open source.\u003C\u002Fli>\n\u003Cli>Available in English, French, Spanish, Polish, Ukrainian, German, Swedish, and many more languages through machine translations.\u003C\u002Fli>\n\u003Cli>Supports Multisite: create global settings and custom defaults for all websites on your network.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Visit the \u003Ca href=\"https:\u002F\u002Fsa11y.netlify.app\u002F\" rel=\"nofollow ugc\">project website\u003C\u002Fa> for a demo or to learn more!\u003C\u002Fp>\n","Geared towards content authors, Sa11y straightforwardly identifies accessibility issues at the source.",300,14570,"2025-12-18T21:05:00.000Z","7.2",[18,132,133,19,134],"accessibility-automated-testing","accessibility-checker","wcag","https:\u002F\u002Fsa11y.netlify.app\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsa11y.1.2.7.zip",{"attackSurface":138,"codeSignals":185,"taintFlows":194,"riskAssessment":195,"analyzedAt":198},{"hooks":139,"ajaxHandlers":181,"restRoutes":182,"shortcodes":183,"cronEvents":184,"entryPointCount":11,"unprotectedCount":11},[140,146,150,154,157,161,164,168,171,174,177],{"type":141,"name":142,"callback":143,"file":144,"line":145},"action","admin_menu","add_admin_menu","class-admin.php",34,{"type":141,"name":147,"callback":148,"file":144,"line":149},"admin_init","settings_init",35,{"type":141,"name":151,"callback":152,"file":144,"line":153},"init","get_instance",110,{"type":141,"name":151,"callback":152,"file":155,"line":156},"class-settings.php",358,{"type":141,"name":151,"callback":158,"file":159,"line":160},"load_plugin_textdomain","inquirer.php",56,{"type":141,"name":162,"callback":152,"file":159,"line":163},"plugins_loaded",146,{"type":141,"name":165,"callback":166,"file":159,"line":167},"admin_post_load_inquirers_action","update_url_for_query",147,{"type":141,"name":165,"callback":169,"file":159,"line":170},"use_inquirer",148,{"type":141,"name":165,"callback":172,"file":159,"line":173},"remove_inquirer",149,{"type":141,"name":165,"callback":175,"file":159,"line":176},"filter_inquirer_types",150,{"type":141,"name":178,"callback":179,"file":159,"line":180},"admin_post_add_inquirer_action","save_inquirer",151,[],[],[],[],{"dangerousFunctions":186,"sqlUsage":187,"outputEscaping":189,"fileOperations":31,"externalRequests":31,"nonceChecks":192,"capabilityChecks":11,"bundledLibraries":193},[],{"prepared":11,"raw":11,"locations":188},[],{"escaped":190,"rawEcho":11,"locations":191},38,[],5,[],[],{"summary":196,"deductions":197},"The \"inquirer\" v0.1.0 plugin exhibits a strong security posture based on the provided static analysis. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the potential attack surface. Furthermore, the code signals are overwhelmingly positive, with no dangerous functions identified, all SQL queries using prepared statements, and all output being properly escaped. The presence of nonce and capability checks, though limited in the latter, also suggests an awareness of basic security practices. The lack of any recorded vulnerabilities in its history further reinforces this positive assessment.",[],"2026-03-17T07:01:03.266Z",{"wat":200,"direct":206},{"assetPaths":201,"generatorPatterns":203,"scriptPaths":204,"versionParams":205},[202],"\u002Fwp-content\u002Fplugins\u002Finquirer\u002Fassets\u002Fstyle.css",[],[],[],{"cssClasses":207,"htmlComments":208,"htmlAttributes":210,"restEndpoints":215,"jsGlobals":216,"shortcodeOutput":217},[],[209],"\u003C!-- TODO:\n#Maybe use thickbox modal for info\u002Fwarnings: https:\u002F\u002Fcodex.wordpress.org\u002FThickBox\n#Use the help tab for info, like Core does. -->",[211,212,213,214],"data-inquirer-name","data-inquirer-url","data-inquirer-type","data-inquirer-testing-url",[],[],[]]