[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ftURYQ1YrxwaDi2jGMiIZMO9e0S_NABv0C9tbt3X1yZo":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":21,"download_link":22,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":34,"analysis":137,"fingerprints":205},"azurecurve-page-index","azurecurve Page Index","2.0.3","azurecurve","https:\u002F\u002Fprofiles.wordpress.org\u002Fazurecurve\u002F","\u003Cp>Shortcode which displays a simple tile based page index showing the child pages of the loaded page or of the supplied pageid or slug. This plugin is multisite compatible.\u003C\u002Fp>\n","Shortcode which displays a simple tile based page index showing the child pages of the loaded page or of the supplied pageid or slug.",10,2167,0,"2018-12-06T19:18:00.000Z","5.0.0","3.5","",[19,20],"index","page","http:\u002F\u002Fdevelopment.azurecurve.co.uk\u002Fplugins\u002Fpage-index","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fazurecurve-page-index.2.0.3.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":28,"total_installs":29,"avg_security_score":30,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},15,710,88,30,86,"2026-04-04T11:26:22.365Z",[35,56,80,98,120],{"slug":36,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":17,"tags":50,"homepage":54,"download_link":55,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"noindex-pages","Noindex Pages","1.0.1","radgh","https:\u002F\u002Fprofiles.wordpress.org\u002Fradgh\u002F","\u003Cp>This simple and lightweight plugin adds a “Hide from search engines” checkbox above the publish box to pages. By\u003Cbr \u002F>\nticking this box, a meta tag will be placed into the \u003Ccode>\u003Chead>\u003C\u002Fcode> section of your page specifying that robots should\u003Cbr \u002F>\nnot index the page.\u003C\u002Fp>\n\u003Cp>By default this only applies to pages. You may extend this functionality to posts or other custom post types with a small bit of code. See the FAQ’s tab for further instructions.\u003C\u002Fp>\n","Ask search engines not to index individual pages by checking an option in the publish post box.",2000,19891,90,6,"2016-02-03T18:38:00.000Z","4.4.34","3.2",[51,52,53],"noindex","pages","robots","http:\u002F\u002Fradgh.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnoindex-pages.1.0.1.zip",{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":43,"downloaded":64,"rating":65,"num_ratings":66,"last_updated":67,"tested_up_to":68,"requires_at_least":69,"requires_php":70,"tags":71,"homepage":17,"download_link":76,"security_score":77,"vuln_count":78,"unpatched_count":13,"last_vuln_date":79,"fetched_at":25},"simple-googlebot-visit","Simple Googlebot Visit","1.2.6","codents","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodents\u002F","\u003Cp>Simple Googlebot Visit is a plugin that lets you know at all times the last time that the googlebot visited any of your content. This is important because it is in charge of indexing all your pages and showing them in the search results of Google.\u003C\u002Fp>\n\u003Cp>Thanks to Simple Googlebot Visit you have this valuable information integrated into your WordPress administration panel, without having to integrate tools such as Search Console.\u003C\u002Fp>\n","Plugin to view the last visit of googlebot to your pages, entries and woocommerce products.",16794,96,16,"2025-06-28T15:21:00.000Z","6.8.5","3.0.1","5.5",[72,73,74,52,75],"google","googlebot","indexation","seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-googlebot-visit.zip",100,1,"2023-07-24 00:00:00",{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":45,"downloaded":88,"rating":13,"num_ratings":13,"last_updated":89,"tested_up_to":90,"requires_at_least":91,"requires_php":17,"tags":92,"homepage":96,"download_link":97,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"featured-posts","Featured Posts","0.2.1","impnerd","https:\u002F\u002Fprofiles.wordpress.org\u002Fimpnerd\u002F","\u003Cp>A simple featured posts plugin which allows for a full customizable display. Featured Posts allows you to display a post excerpt or custom excerpt along with an image anywhere outside the_loop.\u003C\u002Fp>\n","Display a featured post on your index.php or category pages.",17911,"2009-06-11T20:28:00.000Z","2.8","2.6",[93,94,19,95],"categories","homepage","post","http:\u002F\u002Fimpnerd.com\u002Ffeatured-posts","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffeatured-posts.0.2.1.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":13,"num_ratings":13,"last_updated":108,"tested_up_to":109,"requires_at_least":110,"requires_php":111,"tags":112,"homepage":117,"download_link":118,"security_score":119,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"index-pages","Index Pages","1.3.0.1","Doug Wollison","https:\u002F\u002Fprofiles.wordpress.org\u002Fdougwollison\u002F","\u003Cp>The Index Pages system allows you to designate pages as the index page for a particular post type.\u003C\u002Fp>\n\u003Cp>This allows you to have a custom title, text content, and other information displayed on your\u003Cbr \u002F>\npost type archives, should your current theme support it.\u003C\u002Fp>\n\u003Cp>For theme developers, the plugin offers some template functions for loading the post object for the\u003Cbr \u002F>\ncurrent index page (including the posts page), in a similar fashion to \u003Ccode>the_post();\u003C\u002Fcode>, to create things\u003Cbr \u002F>\nlike a customizable introductory banner that appears above the listing, using the index page’s data.\u003C\u002Fp>\n\u003Cp>Designated index pages are flagged as such in the Pages manager, for easy recognition.\u003C\u002Fp>\n\u003Ch3>Usage Documentation\u003C\u002Fh3>\n\u003Cp>The Index Page assignment interface can be found under Settings > Reading. By default, all post types\u003Cbr \u002F>\nregistered with the \u003Ccode>has_archive\u003C\u002Fcode> argument set to true will be available for assignment.\u003C\u002Fp>\n\u003Cp>For theme and plugin developers, you can register support for your custom post types like so:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>IndexPages\\Registry::add_post_types( $post_types ); \u002F\u002F a single post type or array of post types\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>When an index page is assigned, it’s permalink will point to the associated post type’s archive, with\u003Cbr \u002F>\nthe page title updated appropriately.\u003C\u002Fp>\n\u003Cp>For theme and plugin developers, you can access the index page’s post object with the following.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>the_index_page();\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This works exactly like \u003Ccode>the_post();\u003C\u002Fcode>, populating the \u003Ccode>$post\u003C\u002Fcode> variable with the index page’s data.\u003C\u002Fp>\n","Assign pages as the index page for WordPress custom post types, similar to the Posts Page.",60,2810,"2024-10-14T22:04:00.000Z","6.6.5","4.0.0","5.4.0",[113,114,115,116],"custom-index","custom-post-type","index-page","page-for-posts","https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Findex-pages","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Findex-pages.1.3.0.1.zip",92,{"slug":121,"name":122,"version":123,"author":124,"author_profile":125,"description":126,"short_description":127,"active_installs":128,"downloaded":129,"rating":13,"num_ratings":13,"last_updated":130,"tested_up_to":131,"requires_at_least":132,"requires_php":17,"tags":133,"homepage":17,"download_link":134,"security_score":135,"vuln_count":78,"unpatched_count":78,"last_vuln_date":136,"fetched_at":25},"noindex-by-path","Noindex by Path","1.0","Marcin Kijak","https:\u002F\u002Fprofiles.wordpress.org\u002Fmkijak\u002F","\u003Cp>After installation you can find “Noindex by path” option in the main menu. This allows you to simply add relative paths\u003Cbr \u002F>\nyou need to exclude from SERPs. Add a path (including slashes from begging and the end of the string) and save the\u003Cbr \u002F>\nchanges. Since this plugin is called to be “simple” you can add only one path at once, but the process is smooth\u003Cbr \u002F>\nand easy.\u003C\u002Fp>\n\u003Cp>Plugin will add “noindex” meta tag which is an instruction for search engines that this particular page should not be indexed.\u003Cbr \u002F>\nTechnically it modifies wp_head tag.\u003C\u002Fp>\n","Ask search engines not to index individual pages by a relative path - which means you can set every url no matter it is a page, category listing or an &hellip;",50,1761,"2017-05-31T07:04:00.000Z","4.7.32","4.0",[51,52,53],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnoindex-by-path.zip",63,"2025-12-31 00:00:00",{"attackSurface":138,"codeSignals":182,"taintFlows":197,"riskAssessment":198,"analyzedAt":204},{"hooks":139,"ajaxHandlers":175,"restRoutes":176,"shortcodes":177,"cronEvents":181,"entryPointCount":78,"unprotectedCount":13},[140,146,150,155,159,163,167,171],{"type":141,"name":142,"callback":143,"file":144,"line":145},"action","wp_enqueue_scripts","azc_pi_load_css","azurecurve-page-index.php",37,{"type":141,"name":147,"callback":148,"file":144,"line":149},"plugins_loaded","azc_pi_load_plugin_textdomain",47,{"type":151,"name":152,"callback":153,"priority":11,"file":144,"line":154},"filter","plugin_action_links","azc_pi_plugin_action_links",106,{"type":141,"name":156,"callback":157,"file":144,"line":158},"admin_post_save_azc_pi_options","process_azc_pi_options",189,{"type":141,"name":160,"callback":161,"file":144,"line":162},"admin_init","azc_pi_admin_init",191,{"type":141,"name":164,"callback":165,"file":144,"line":166},"admin_menu","azc_create_pi_plugin_menu",350,{"type":141,"name":164,"callback":168,"file":169,"line":170},"azc_create_plugin_menu","includes\\menu.php",29,{"type":141,"name":172,"callback":173,"file":169,"line":174},"admin_head","azc_plugin_index_load_css",36,[],[],[178],{"tag":179,"callback":180,"file":144,"line":174},"page-index","azc_display_page_index",[],{"dangerousFunctions":183,"sqlUsage":184,"outputEscaping":193,"fileOperations":13,"externalRequests":13,"nonceChecks":78,"capabilityChecks":185,"bundledLibraries":196},[],{"prepared":185,"raw":185,"locations":186},2,[187,190],{"file":144,"line":188,"context":189},62,"$wpdb->get_col() with variable interpolation",{"file":191,"line":192,"context":189},"uninstall.php",24,{"escaped":194,"rawEcho":13,"locations":195},20,[],[],[],{"summary":199,"deductions":200},"The azurecurve-page-index v2.0.3 plugin exhibits a strong security posture based on the provided static analysis. The absence of dangerous functions, 100% output escaping, and the presence of nonce and capability checks are commendable practices. Furthermore, the plugin has no known vulnerabilities (CVEs) and no recorded history of past issues, suggesting a mature and well-maintained codebase.\n\nThe static analysis reveals a very limited attack surface with only one shortcode and no unprotected AJAX handlers or REST API routes. The SQL queries, while present, show a reasonable usage of prepared statements, with 50% of them being prepared. Taint analysis found no vulnerabilities, which is a very positive sign.\n\nIn conclusion, this plugin appears to be securely developed. The limited attack surface, robust input sanitization and output escaping, and lack of historical vulnerabilities point to a low-risk component. The only minor area for consideration is that 50% of SQL queries are not prepared, which could be an area for future hardening, although in this context, it does not appear to introduce a significant risk.",[201],{"reason":202,"points":203},"SQL queries not using prepared statements",5,"2026-03-17T00:40:36.746Z",{"wat":206,"direct":213},{"assetPaths":207,"generatorPatterns":209,"scriptPaths":210,"versionParams":211},[208],"\u002Fwp-content\u002Fplugins\u002Fazurecurve-page-index\u002Fstyle.css",[],[],[212],"azurecurve-page-index\u002Fstyle.css?ver=",{"cssClasses":214,"htmlComments":215,"htmlAttributes":216,"restEndpoints":217,"jsGlobals":218,"shortcodeOutput":219},[],[],[],[],[],[]]