[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$funrPRGn85s9g8SKY7b4sgg3vuHTtVEa7jXRRlkK8aDU":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":36,"analysis":61,"fingerprints":104},"disable-archive-pages","Disable Archive Pages","1.0.0","Kasper Knudsen","https:\u002F\u002Fprofiles.wordpress.org\u002Fkasper-knudsen\u002F","\u003Cp>This plugin allows you to disable public archive pages such as:\u003Cbr \u002F>\n– Category archives\u003Cbr \u002F>\n– Tag archives\u003Cbr \u002F>\n– Author archives\u003Cbr \u002F>\n– Date-based archives\u003Cbr \u002F>\n– Custom taxonomy archives\u003Cbr \u002F>\n– Custom post type archives\u003C\u002Fp>\n\u003Cp>Each disabled archive will:\u003Cbr \u002F>\n– Return a 404 error\u003Cbr \u002F>\n– Be excluded from XML sitemaps\u003C\u002Fp>\n\u003Cp>Useful for SEO and improving site clarity by removing thin or duplicate content.\u003C\u002Fp>\n","Disable unwanted archive pages like category, tag, author, date, and custom post type archives.",40,313,0,"2025-07-23T17:31:00.000Z","6.8.5","6.0","7.4",[19,20,21,22,23],"disable-archives","disable-author","disable-category","disable-tag","remove-archive-pages","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-archive-pages.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"kasper-knudsen",1,30,94,"2026-04-04T00:40:06.929Z",[37],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":58,"download_link":59,"security_score":60,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"smart-archive-page-remove","Smart Archive Page Remove","5.1.3","Peter Raschendorfer","https:\u002F\u002Fprofiles.wordpress.org\u002Fpetersplugins\u002F","\u003Cp>The Smart Archive Page Remove Plugin allows you to remove Archive Pages automatically generated by WordPress\u003C\u002Fp>\n\u003Ch3>Retired Plugin\u003C\u002Fh3>\n\u003Cp>Development, maintenance and support of this plugin has been retired in october 2023. You can use this plugin as long as is works for you.\u003C\u002Fp>\n\u003Cp>There will be no more updates and I won’t answer any support questions. Thanks for your understanding.\u003C\u002Fp>\n\u003Cp>Feel free to fork this plugin.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>WordPress automatically generates Author based, Category based, Tag based and Date based (daily, monthly and yearly) archives for your posts. Even if you do not want to use these Pages – e.g. you don’t want to have an author based archive page on a single author blog or you don’t want to have a daily archive because you don’t post several times a day – they exist and they can be accessed by their automated generated URL.\u003C\u002Fp>\n\u003Cp>The smart Archive Page Remove Plugin adds an item ‘Archive Pages’ in the ‘Settings’ section of your WordPress Admin. Here you can select which Archive Pages you want to \u003Cstrong>remove\u003C\u002Fstrong>. Removed Archive Pages are no longer accessible and cause a 404 page not found error. They can be restored anytime.\u003C\u002Fp>\n\u003Ch3>Plugin Privacy Information\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>This plugin does not set cookies\u003C\u002Fli>\n\u003Cli>This plugin does not collect or store any data\u003C\u002Fli>\n\u003Cli>This plugin does not send any data to external servers\u003C\u002Fli>\n\u003C\u002Ful>\n","Completely remove unwanted Archive Pages from your Blog",7000,95016,98,59,"2024-04-17T20:15:00.000Z","6.3.8","4.0","5.4",[54,55,56,57,23],"archive-page","archive-pages","delete-archive","remove-archive","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsmart-archive-page-remove\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsmart-archive-page-remove.5.1.3.zip",92,{"attackSurface":62,"codeSignals":91,"taintFlows":99,"riskAssessment":100,"analyzedAt":103},{"hooks":63,"ajaxHandlers":87,"restRoutes":88,"shortcodes":89,"cronEvents":90,"entryPointCount":13,"unprotectedCount":13},[64,70,73,77,82],{"type":65,"name":66,"callback":67,"file":68,"line":69},"action","admin_init","amgr_register_settings","disable-archive-pages.php",25,{"type":65,"name":71,"callback":72,"file":68,"line":11},"admin_menu","amgr_add_admin_menu",{"type":65,"name":74,"callback":75,"file":68,"line":76},"template_redirect","amgr_disable_archives",131,{"type":78,"name":79,"callback":80,"file":68,"line":81},"filter","template_include","closure",139,{"type":78,"name":83,"callback":84,"priority":85,"file":68,"line":86},"wp_sitemaps_add_provider","amgr_remove_archives_from_sitemap",10,161,[],[],[],[],{"dangerousFunctions":92,"sqlUsage":93,"outputEscaping":95,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":32,"bundledLibraries":98},[],{"prepared":13,"raw":13,"locations":94},[],{"escaped":96,"rawEcho":13,"locations":97},8,[],[],[],{"summary":101,"deductions":102},"The 'disable-archive-pages' plugin version 1.0.0 demonstrates an excellent security posture based on the provided static analysis. The complete absence of an attack surface in terms of AJAX handlers, REST API routes, shortcodes, and cron events significantly reduces the potential for external exploitation. The code itself adheres to strong security practices, with no dangerous functions identified, all SQL queries utilizing prepared statements, and all output properly escaped. The presence of a capability check is also a positive sign of secure coding, although the lack of nonce checks on AJAX endpoints would be a concern if any existed. The plugin's vulnerability history is also clean, with no recorded CVEs, suggesting a consistent history of secure development or limited exposure. Overall, this plugin appears to be very secure with no immediate exploitable vulnerabilities indicated by the static analysis. Its strengths lie in its minimal attack surface and adherence to secure coding standards. The only potential area for minor concern, which is not currently an issue due to the absence of specific entry points, would be the lack of nonce checks if AJAX functionalities were to be implemented in the future.",[],"2026-03-16T22:17:57.037Z",{"wat":105,"direct":110},{"assetPaths":106,"generatorPatterns":107,"scriptPaths":108,"versionParams":109},[],[],[],[],{"cssClasses":111,"htmlComments":112,"htmlAttributes":113,"restEndpoints":115,"jsGlobals":116,"shortcodeOutput":117},[],[],[114],"name=\"amgr_disabled_archives[]\"",[],[],[]]