[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f8-MR4bQhIq13h9T5daAXoRxguKyjvzhTED4Hd_qjg9g":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":35,"analysis":131,"fingerprints":165},"robots-txt-extender","Robots.txt Extender","1.0.0","bettoadami","https:\u002F\u002Fprofiles.wordpress.org\u002Fbettoadami\u002F","\u003Cp>A Multisite Network plugin that removes the automatic sitemap link (deprecated practice) and adds custom parameters\u002Flines at the end of the default Robots.txt whenever called. It will enable small adjustments for each site on the network – like pointing again to specific sitemaps if needed – without sacrificing the default conventions coded to WordPress’ core. To make the adjustments, look for a text area at the end of General Settings Page.\u003C\u002Fp>\n","Dynamic robots.txt for Multisite! Change parameters, or don't, for each site of your network without losing the defaults from WordPress Includes.",10,1035,0,"2020-08-22T19:22:00.000Z","5.0.25","5.0","7.0",[19,20,21,22,23],"crawler","robots","robots-txt","robotstxt","spiders","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frobots-txt-extender.1.0.0.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,84,"2026-04-04T22:30:52.169Z",[36,54,71,90,112],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":13,"num_ratings":13,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":24,"tags":49,"homepage":52,"download_link":53,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"robotswhiz","Robots Meta Whiz","1.2.0","Marat Nepomnyashy","https:\u002F\u002Fprofiles.wordpress.org\u002Fmaratbn\u002F","\u003Cp>Overview:\u003C\u002Fp>\n\u003Cp>At the time of this writing, the latest version of WordPress, version 4.7,\u003Cbr \u002F>\n  has functionality to discourage search engines from indexing the whole site,\u003Cbr \u002F>\n  but not functionality to discourage search engines from indexing only certain\u003Cbr \u002F>\n  specific pages and posts of the site.\u003C\u002Fp>\n\u003Cp>Robots Meta Whiz is a WordPress plugin that allows site administrators to\u003Cbr \u002F>\n  deploy custom meta robots tags to discourage search engines from indexing,\u003Cbr \u002F>\n  following links from, caching, indexing images from, and \u002F or have\u003Cbr \u002F>\n  additional custom restrictions on only for certain specifically-designated\u003Cbr \u002F>\n  pages and posts.\u003C\u002Fp>\n\u003Cp>It is an easy way to discourage search engines from indexing only specific\u003Cbr \u002F>\n  pages \u002F posts.\u003C\u002Fp>\n\u003Cp>This only applies to search engine robots, and will not effect the site’s\u003Cbr \u002F>\n  local search functionality.\u003C\u002Fp>\n\u003Cp>Technical summary:\u003C\u002Fp>\n\u003Cp>Plugin works by hooking-in special logic into the action ‘wp_head’ to inject\u003Cbr \u002F>\n  the tag \u003Ccode>\u003Cmeta name='robots' content='...'>\u003C\u002Fcode> with restriction directives for\u003Cbr \u002F>\n  the specified pages and posts.\u003C\u002Fp>\n\u003Cp>Official project URLs:\u003C\u002Fp>\n\u003Cp>https:\u002F\u002Fwordpress.org\u002Fplugins\u002Frobotswhiz\u003Cbr \u002F>\n  https:\u002F\u002Fgithub.com\u002Fmaratbn\u002FRobotsWhiz\u003C\u002Fp>\n","Easy way to discourage search engines from indexing only specific pages \u002F posts with custom meta tags.",100,4618,"2017-01-09T03:55:00.000Z","4.7.32","3.8.1",[50,20,21,51,23],"crawlers","search-engines","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Frobotswhiz","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frobotswhiz.1.2.0.zip",{"slug":55,"name":56,"version":57,"author":58,"author_profile":59,"description":60,"short_description":61,"active_installs":11,"downloaded":62,"rating":13,"num_ratings":13,"last_updated":63,"tested_up_to":64,"requires_at_least":65,"requires_php":24,"tags":66,"homepage":69,"download_link":70,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"ljpl-armored-robotstxt","LJPL Armored robots.txt","1.0","Lukasz Jasinski","https:\u002F\u002Fprofiles.wordpress.org\u002Fljasinskipl\u002F","\u003Cp>robots.txt is a file, which tell’s search engines, which parts of your site it can display publicly.\u003Cbr \u002F>\nThis plugin add’s some entries to this file, to make your site safer from some attacks, keeping all your stength in seo intact ex. allowing search engine robots to harvest pictures for image search. When preparing a new site in WordPress, it’s one of the first plugins I install.\u003C\u002Fp>\n","Add some directives to your robots.txt file to keep your site safer",3188,"2013-05-08T08:33:00.000Z","3.4.2","3.0",[50,21,67,68,23],"search-engine-robots","security","http:\u002F\u002Fwww.ljasinski.pl\u002Fportfolio\u002Fwordpress-plugins\u002Farmored-robots-txt\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fljpl-armored-robotstxt.1.0.zip",{"slug":72,"name":73,"version":74,"author":75,"author_profile":76,"description":77,"short_description":78,"active_installs":79,"downloaded":80,"rating":81,"num_ratings":82,"last_updated":83,"tested_up_to":84,"requires_at_least":85,"requires_php":86,"tags":87,"homepage":24,"download_link":89,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"robots-txt-editor","Robots.txt Editor","1.1.4","Processby","https:\u002F\u002Fprofiles.wordpress.org\u002Fprocessby\u002F","\u003Cp>The plugin allows you to create and edit the robots.txt file on your site.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Works with multisite network on Subdomains;\u003C\u002Fli>\n\u003Cli>An example of the correct file for WordPress;\u003C\u002Fli>\n\u003Cli>Works out of the box;\u003C\u002Fli>\n\u003Cli>Totally Free.\u003C\u002Fli>\n\u003C\u002Ful>\n","Robots.txt for WordPress",10000,111434,90,8,"2021-01-16T00:07:00.000Z","5.6.17","4.0","5.6",[19,20,21,88],"seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frobots-txt-editor.zip",{"slug":91,"name":92,"version":93,"author":94,"author_profile":95,"description":96,"short_description":97,"active_installs":98,"downloaded":99,"rating":81,"num_ratings":100,"last_updated":101,"tested_up_to":102,"requires_at_least":16,"requires_php":103,"tags":104,"homepage":24,"download_link":108,"security_score":109,"vuln_count":110,"unpatched_count":13,"last_vuln_date":111,"fetched_at":28},"better-robots-txt","Better Robots.txt – AI-Ready Crawl Control & Bot Governance","3.0.0","Pagup","https:\u002F\u002Fprofiles.wordpress.org\u002Fpagup\u002F","\u003Cp>Better Robots.txt replaces the default WordPress robots.txt workflow with a smarter, structured version you can configure and preview before publishing.\u003C\u002Fp>\n\u003Cp>Instead of a blank textarea, you get a guided wizard with presets, plain-language explanations, and a final Review & Save step so you can inspect the generated robots.txt before it goes live.\u003C\u002Fp>\n\u003Cp>Built for beginners and advanced users alike, Better Robots.txt helps you control how search engines, AI crawlers, SEO tools, archive bots, bad bots, social preview bots, and other automated agents interact with your site.\u003C\u002Fp>\n\u003Cp>Trusted by thousands of WordPress sites, Better Robots.txt is designed for the AI era without resorting to hype, vague promises, or hidden rules.\u003C\u002Fp>\n\u003Cp>Better Robots.txt is available in Free, Pro, and Premium editions. The free plugin covers the guided workflow and essential crawl control features, while Pro and Premium unlock additional governance, protection, and AI-ready modules. Some screenshots on the plugin page show features from all three editions.\u003C\u002Fp>\n\u003Ch3>A quick overview\u003C\u002Fh3>\n\u003Cp>\u003Ciframe loading=\"lazy\" title=\"Better robots.txt Video — AI-Ready Crawl Control for WordPress\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F1169756981?dnt=1&app_id=122963\" width=\"750\" height=\"372\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\">\u003C\u002Fiframe>\u003C\u002Fp>\n\u003Ch3>Why Better Robots.txt is different\u003C\u002Fh3>\n\u003Cp>Most robots.txt plugins fall into one of three categories:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Simple text editor\u003C\u002Fli>\n\u003Cli>Virtual robots.txt manager\u003C\u002Fli>\n\u003Cli>Single-purpose AI or policy add-on\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Better Robots.txt goes further.\u003C\u002Fp>\n\u003Cp>It gives you a complete, guided crawl control workflow so you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Choose a preset that matches your goals\u003C\u002Fli>\n\u003Cli>Control major crawler categories without writing everything by hand\u003C\u002Fli>\n\u003Cli>Keep core WordPress protection rules visible and editable\u003C\u002Fli>\n\u003Cli>Clean up low-value crawl paths that waste crawl budget\u003C\u002Fli>\n\u003Cli>Generate a cleaner robots.txt output\u003C\u002Fli>\n\u003Cli>Preview the final result before saving\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What you can control\u003C\u002Fh3>\n\u003Cp>Better Robots.txt helps you manage:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Search engine visibility\u003C\u002Fli>\n\u003Cli>AI and LLM crawler behavior\u003C\u002Fli>\n\u003Cli>AI usage signals such as search, ai-input, and ai-train preferences\u003C\u002Fli>\n\u003Cli>SEO tool crawlers\u003C\u002Fli>\n\u003Cli>Bad bots and abusive crawlers\u003C\u002Fli>\n\u003Cli>Archive and Wayback access\u003C\u002Fli>\n\u003Cli>Feed crawlers and crawl traps\u003C\u002Fli>\n\u003Cli>WooCommerce crawl cleanup\u003C\u002Fli>\n\u003Cli>CSS, JavaScript, and image crawling rules\u003C\u002Fli>\n\u003Cli>Social media preview crawlers\u003C\u002Fli>\n\u003Cli>ads.txt and app-ads.txt allowance\u003C\u002Fli>\n\u003Cli>llms.txt generation\u003C\u002Fli>\n\u003Cli>Advanced directives such as crawl-delay and custom rules\u003C\u002Fli>\n\u003Cli>Final review before publishing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Editions\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is available in three editions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Free – Includes the guided setup, the Essential preset, core crawl control features, and the final Review & Save workflow.\u003C\u002Fli>\n\u003Cli>Pro – Adds more advanced governance and protection modules, including additional AI, crawler, and cleanup controls.\u003C\u002Fli>\n\u003Cli>Premium – Unlocks the most restrictive and advanced protection options, including the Fortress preset and additional high-control modules.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Some options shown in the interface are marked Free, Pro, or Premium so users can immediately understand which modules belong to each edition.\u003C\u002Fp>\n\u003Ch3>Presets\u003C\u002Fh3>\n\u003Cp>Setup starts with four modes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Essential – A clean, practical configuration for most websites that want a better robots.txt without complexity.\u003C\u002Fli>\n\u003Cli>AI-First – For publishers and content sites that want AI-ready governance without shutting down discovery.\u003C\u002Fli>\n\u003Cli>Fortress – For websites that want stronger protection against scraping, archive capture, and unnecessary crawl activity.\u003C\u002Fli>\n\u003Cli>Custom – For users who prefer to configure each module manually.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For many sites, one preset plus a quick review is enough.\u003C\u002Fp>\n\u003Ch3>Built for beginners and experts\u003C\u002Fh3>\n\u003Cp>Beginners get:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A guided setup instead of a raw robots.txt box\u003C\u002Fli>\n\u003Cli>Preset-based configuration\u003C\u002Fli>\n\u003Cli>Plain-language explanations for important choices\u003C\u002Fli>\n\u003Cli>A safer workflow with a final preview step\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Advanced users get:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Editable core WordPress protection rules\u003C\u002Fli>\n\u003Cli>Fine-grained crawler controls by category\u003C\u002Fli>\n\u003Cli>WooCommerce-oriented cleanup options\u003C\u002Fli>\n\u003Cli>Consolidated output options\u003C\u002Fli>\n\u003Cli>Advanced directives and custom rules\u003C\u002Fli>\n\u003Cli>A final output they can inspect before publishing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>AI-ready, without hype\u003C\u002Fh3>\n\u003Cp>Better Robots.txt includes features for modern AI-related crawl governance, including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI crawler handling\u003C\u002Fli>\n\u003Cli>Optional llms.txt support\u003C\u002Fli>\n\u003Cli>AI usage signals for compliant systems\u003C\u002Fli>\n\u003Cli>Optional machine-readable governance signals for advanced use cases\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These features help you express how you want automated systems to use your content.\u003C\u002Fp>\n\u003Cp>However, Better Robots.txt does not claim to control AI by force. Like robots.txt itself, these signals are most useful with compliant systems and good-faith crawlers.\u003C\u002Fp>\n\u003Ch3>What Better Robots.txt is\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A robots.txt governance plugin for WordPress\u003C\u002Fli>\n\u003Cli>A guided configuration workflow instead of a raw text editor\u003C\u002Fli>\n\u003Cli>A crawl control layer to reduce wasteful crawling\u003C\u002Fli>\n\u003Cli>A practical bridge between SEO, crawl hygiene, and AI-era policy signaling\u003C\u002Fli>\n\u003Cli>A way to keep your crawl policy clearer for humans and machines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Technical reference for advanced users: Better Robots.txt also maintains a public \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FGautierDorval\u002Fbetter-robots-txt\" rel=\"nofollow noopener noreferrer ugc\">GitHub repository\u003C\u002Fa> with product definition, governance notes, and machine-readable artefacts.\u003C\u002Fp>\n\u003Ch3>What Better Robots.txt is not\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is not:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A firewall or Web Application Firewall (WAF)\u003C\u002Fli>\n\u003Cli>An anti-scraping enforcement engine\u003C\u002Fli>\n\u003Cli>A legal compliance engine\u003C\u002Fli>\n\u003Cli>A guarantee that every bot will obey your rules\u003C\u002Fli>\n\u003Cli>A replacement for server-level security or access control\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It helps you publish a clearer crawl policy.\u003C\u002Fp>\n\u003Cp>It does not replace infrastructure-level protection.\u003C\u002Fp>\n\u003Ch3>Typical use cases\u003C\u002Fh3>\n\u003Cp>Use Better Robots.txt if you want to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Clean up a weak or noisy default robots.txt\u003C\u002Fli>\n\u003Cli>Reduce crawl waste on WordPress or WooCommerce\u003C\u002Fli>\n\u003Cli>Keep major search engines allowed while restricting other bots\u003C\u002Fli>\n\u003Cli>Control whether archive bots can snapshot your site\u003C\u002Fli>\n\u003Cli>Publish AI usage preferences more clearly\u003C\u002Fli>\n\u003Cli>Keep social preview bots allowed while limiting scrapers\u003C\u002Fli>\n\u003Cli>Review the final file before making it live\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Guided step-by-step wizard\u003C\u002Fli>\n\u003Cli>Preset-based setup: Essential, AI-First, Fortress, Custom\u003C\u002Fli>\n\u003Cli>Search engine visibility controls\u003C\u002Fli>\n\u003Cli>AI and LLM crawler governance\u003C\u002Fli>\n\u003Cli>AI usage signals support\u003C\u002Fli>\n\u003Cli>SEO tool crawler controls\u003C\u002Fli>\n\u003Cli>Bad bot and abusive crawler options\u003C\u002Fli>\n\u003Cli>Archive and Wayback access controls\u003C\u002Fli>\n\u003Cli>Spam, feed, and crawl trap cleanup\u003C\u002Fli>\n\u003Cli>WooCommerce crawl cleanup options\u003C\u002Fli>\n\u003Cli>CSS, JavaScript, and image crawling rules\u003C\u002Fli>\n\u003Cli>Social media preview crawler controls\u003C\u002Fli>\n\u003Cli>ads.txt and app-ads.txt allowance\u003C\u002Fli>\n\u003Cli>Optional llms.txt generation\u003C\u002Fli>\n\u003Cli>Consolidated output option\u003C\u002Fli>\n\u003Cli>Core WordPress protection rules remain visible and editable\u003C\u002Fli>\n\u003Cli>Final Review & Save preview screen\u003C\u002Fli>\n\u003C\u002Ful>\n","Replace the default WordPress robots.txt workflow with a smarter, structured version you can preview before publishing, with Free, Pro, and Premium ed …",6000,305034,102,"2026-03-10T18:33:00.000Z","6.9.4","7.4",[105,106,107,21,88],"ai-crawlers","bot-blocker","llms-txt","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbetter-robots-txt.3.0.0.zip",99,2,"2023-02-14 00:00:00",{"slug":113,"name":114,"version":115,"author":116,"author_profile":117,"description":118,"short_description":119,"active_installs":120,"downloaded":121,"rating":122,"num_ratings":123,"last_updated":124,"tested_up_to":102,"requires_at_least":125,"requires_php":126,"tags":127,"homepage":24,"download_link":130,"security_score":44,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"block-ai-crawlers","Block AI Crawlers","1.5.6","lastsplash (a11n)","https:\u002F\u002Fprofiles.wordpress.org\u002Flastsplash\u002F","\u003Cp>Protect Your Content from AI Scraping\u003C\u002Fp>\n\u003Cp>This plugin helps you prevent AI crawlers from using your content as training data for their products. By updating your site’s \u003Ccode>robots.txt\u003C\u002Fcode>, it blocks common AI crawlers and scrapers, aiming to protect your content from being used in the training of Large Language Models (LLMs).\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Ch3>Blocks AI Crawlers\u003C\u002Fh3>\n\u003Cp>Includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>OpenAI\u003C\u002Fstrong> – Blocks crawlers used for ChatGPT\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Google\u003C\u002Fstrong> – Blocks crawlers used by Google’s Gemini AI products\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Facebook \u002F Meta\u003C\u002Fstrong> – Used for Facebook’s AI training\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anthropic AI\u003C\u002Fstrong> – Blocks crawlers used by Anthropic  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Perplexity\u003C\u002Fstrong> – Block crawlers used by Perplexity\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Applebot\u003C\u002Fstrong> – Blocks crawlers used by Apple\u003C\u002Fli>\n\u003Cli>… and more!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Experimental Meta Tags\u003C\u002Fh3>\n\u003Cp>The plugin adds the “noai, noimageai” directive to your site’s meta tags, instructing AI bots not to use your content in their datasets. Please note that these tags are experimental and have not been standardized.\u003C\u002Fp>\n\u003Ch3>Custom robots.txt Rules\u003C\u002Fh3>\n\u003Cp>Have custom entries for your robots.txt file? You can now add them directly through the plugin!\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>After activation, the plugin will automatically update your \u003Ccode>robots.txt\u003C\u002Fcode> and add the necessary meta tags. No further configuration is required, but you can check the settings page for a full list of blocked crawlers.\u003C\u002Fp>\n\u003Ch3>Limitations\u003C\u002Fh3>\n\u003Cp>While this plugin aims to block specified crawlers, it cannot guarantee complete protection against all forms of scraping, as some bots may disregard \u003Ccode>robots.txt\u003C\u002Fcode> directives.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>For questions or support, \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fblock-ai-crawlers\u002F\" rel=\"ugc\">please post on the forums\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fbobmatyas\u002Fwp-block-ai-crawlers\u002Fissues\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n","Tell AI (Artificial Intelligence) companies not to scrape your site for their AI products.",1000,13412,96,5,"2026-02-15T13:47:00.000Z","6.8","8.2",[128,129,50,21],"ai","chatgpt","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblock-ai-crawlers.1.5.6.zip",{"attackSurface":132,"codeSignals":148,"taintFlows":158,"riskAssessment":159,"analyzedAt":164},{"hooks":133,"ajaxHandlers":144,"restRoutes":145,"shortcodes":146,"cronEvents":147,"entryPointCount":13,"unprotectedCount":13},[134,140],{"type":135,"name":136,"callback":137,"file":138,"line":139},"action","admin_init","robotsTxtExtender__init","robots-txt-extender.php",98,{"type":141,"name":142,"callback":143,"priority":11,"file":138,"line":109},"filter","robots_txt","robotstxtextender_parameters",[],[],[],[],{"dangerousFunctions":149,"sqlUsage":150,"outputEscaping":152,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":157},[],{"prepared":13,"raw":13,"locations":151},[],{"escaped":13,"rawEcho":31,"locations":153},[154],{"file":138,"line":155,"context":156},72,"raw output",[],[],{"summary":160,"deductions":161},"The \"robots-txt-extender\" v1.0.0 plugin exhibits a strong security posture based on the provided static analysis. There are no identified entry points for external interaction such as AJAX handlers, REST API routes, or shortcodes, which significantly reduces the plugin's attack surface. Furthermore, the absence of dangerous functions, file operations, and external HTTP requests, coupled with the use of prepared statements for all SQL queries, suggests adherence to secure coding practices. The lack of any historical vulnerabilities also points to a history of responsible development and maintenance.\n\nHowever, a critical concern arises from the output escaping analysis, where 100% of outputs are not properly escaped. This indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities, as unsanitized data displayed to users could contain malicious scripts. While the plugin's limited attack surface and clean vulnerability history are positive, the lack of output escaping represents a significant security weakness that could be exploited. Developers should prioritize addressing this deficiency to mitigate potential XSS risks.",[162],{"reason":163,"points":82},"Outputs not properly escaped","2026-03-17T00:47:33.634Z",{"wat":166,"direct":171},{"assetPaths":167,"generatorPatterns":168,"scriptPaths":169,"versionParams":170},[],[],[],[],{"cssClasses":172,"htmlComments":174,"htmlAttributes":175,"restEndpoints":177,"jsGlobals":178,"shortcodeOutput":179},[173],"code",[],[176],"robotsTxtExtender_settingsCode",[],[],[]]