[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ff2v0TultvH3MBtL6huswGOEDNu8sHDOBIn0SpFc1p98":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":38,"analysis":133,"fingerprints":162},"wp-relative-url","Relative URLs","1.0.0","Guglielmo Pepe","https:\u002F\u002Fprofiles.wordpress.org\u002Fgpepe\u002F","\u003Cp>\u003Cem>By default, WordPress saves the content with local domain. If you want develop your blog in one domain and go live in another, you need  replace all URLs in the database.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Relative URLs replace all absolute URLs with relative URLs quickly. You can move from localhost to live domain with minimal effort, but this plugin never change links in database, so you can develop in stanging area or in a subdomain o in a sub-directory without worrying to replace URLs in the content.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Notice: This plugin SHOULD be used for local development only.\u003C\u002Fstrong>\u003Cbr \u002F>\n\u003Cstrong>Notice: This plugin may conflict with server based cache services (like nginx or Varnish).\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Benefits\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Go live in one domain, develop in another\u003C\u002Fli>\n\u003Cli>Move from one directory to another with minimal effort\u003C\u002Fli>\n\u003Cli>Never change links in database\u003C\u002Fli>\n\u003Cli>Switch between HTTP and HTTPS sites\u003C\u002Fli>\n\u003Cli>Backup a production site from one domain, restore for testing at another domain\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Removes the domain name on links for internal links\u003C\u002Fli>\n\u003Cli>Removes the domain name from on image sources for images located in the server\u003C\u002Fli>\n\u003Cli>Dont’t replace URLs in database\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin convert absolute URLs in relative URLs.",10,3333,0,"2021-05-09T18:32:00.000Z","5.7.15","5.2.3","7.2",[19,20,21,22,23],"https","relative-link","relative-url","seo","staging","https:\u002F\u002Fwww.guglielmopepe.com\u002F#wp-relative-url","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-relative-url.1.0.0.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"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},"gpepe",3,140,90,30,87,"2026-04-05T02:50:23.417Z",[39,61,86,103,118],{"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":49,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"hsts-ready","HSTS Ready","1.04","manu225","https:\u002F\u002Fprofiles.wordpress.org\u002Fmanu225\u002F","\u003Cp>Enable easily HSTS on your website.\u003Cbr \u002F>\nAnd see my others WordPress Pro plugin on \u003Ca href=\"https:\u002F\u002Fwww.info-d-74.com\u002Fen\u002Fshop\u002F\" rel=\"nofollow ugc\">my shop\u003C\u002Fa>\u003C\u002Fp>\n","Enable easily HSTS on your website.",3000,31199,100,4,"2025-12-02T14:53:00.000Z","6.9.4","3.5","5.6",[56,19,57,22,58],"hsts","security","strict-transport-security","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhsts-ready.1.04.zip",{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":69,"downloaded":70,"rating":71,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":54,"tags":76,"homepage":82,"download_link":83,"security_score":49,"vuln_count":84,"unpatched_count":13,"last_vuln_date":85,"fetched_at":28},"make-paths-relative","Make Paths Relative","2.1.0","Sami Ahmed Siddiqui","https:\u002F\u002Fprofiles.wordpress.org\u002Fsasiddiqui\u002F","\u003Cp>This powerful plugin simplifies website maintenance by automatically converting absolute paths (URLs) for resources like links, scripts, stylesheets, and images to relative paths. This ensures your website functions flawlessly regardless of its location on a server or domain.\u003C\u002Fp>\n\u003Ch3>Enhanced Efficiency and Flexibility\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Seamless Relocation:\u003C\u002Fstrong> Move your website with confidence, knowing all paths will adjust accordingly, preventing broken links and preserving a seamless user – experience.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Centralized Control:\u003C\u002Fstrong> Update paths once in a central location, eliminating the need for tedious, site-wide modifications.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Potential Performance Boost:\u003C\u002Fstrong> Relative paths can, in some cases, improve website loading times.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Whitelist Your Domains (Optional)\u003C\u002Fh3>\n\u003Cp>For extra control, you can specify a list of domains that will always be converted to relative paths. This ensures internal links are always optimized while allowing external resources to function properly.\u003C\u002Fp>\n\u003Ch3>Embrace a Streamlined Approach\u003C\u002Fh3>\n\u003Cp>This plugin empowers you to focus on creating exceptional content while eliminating the burden of managing absolute paths. Take control, optimize your workflow, and ensure your website’s continued success!\u003C\u002Fp>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Cp>If you want to make plugin works and all the paths relative without going to check\u002Fvisit Settings Page so, just add this line in your theme’s \u003Ccode>functions.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter( 'make_paths_relative_activate_all', '__return_true' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Note\u003C\u002Fstrong>: Make sure to check the settings Page.\u003C\u002Fp>\n\u003Ch3>Bug reports\u003C\u002Fh3>\n\u003Cp>Bug reports for \u003Cstrong>Make Paths Relative\u003C\u002Fstrong> are \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fyasglobal\u002Fmake-paths-relative\u002Fissues\u002F\" rel=\"nofollow ugc\">welcomed on GitHub\u003C\u002Fa>. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.\u003C\u002Fp>\n","Convert Absolute URLs to be relative in your fingertip.",2000,71499,82,15,"2025-07-22T14:32:00.000Z","6.8.5","2.6",[77,78,79,80,81],"migration","relative-links","relative-paths","remove-domain","seo-friendly-urls","https:\u002F\u002Fwww.yasglobal.com\u002Fweb-design-development\u002Fwordpress\u002Fmake-paths-relative\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmake-paths-relative.2.1.0.zip",1,"2023-08-14 00:00:00",{"slug":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":94,"downloaded":95,"rating":13,"num_ratings":13,"last_updated":96,"tested_up_to":52,"requires_at_least":97,"requires_php":98,"tags":99,"homepage":59,"download_link":102,"security_score":49,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"simple-ssl-redirects","Simple SSL Redirects","1.1.4","Blucube","https:\u002F\u002Fprofiles.wordpress.org\u002Fedhicks\u002F","\u003Cp>If your site has an SSL certificate you might find that you can access the site via both SSL (https) and non-SSL (http) URLs. This is a bad idea for security, and for SEO, as it can look like duplicate content on different URLs.\u003C\u002Fp>\n\u003Cp>The answer to this is to redirect requests to non-SSL (http) URLs over to their SSL (https) equivalents using something called a 301 redirect. This tells the client (and search engines) that the resource they are looking for should always be accessed over SSL.  This plugin offers two methods to achieve this:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>By intercepting WordPress pages at header time, and if they are not already being requested over HTTPS sending a 301 redirect header, or\u003C\u002Fli>\n\u003Cli>By adding mod_rewrite rules in the .htaccess file to redirect all requests to their HTTPS equivalents using 301 redirects.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Optionally, this plugin can also set \u003Ca href=\"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FHeaders\u002FStrict-Transport-Security\" rel=\"nofollow ugc\">HSTS\u003C\u002Fa> headers for you, and make sure that all requests use the same hostname (i.e. fixing the issue where many sites can be accessed using both www. and non-www. URLs).\u003C\u002Fp>\n","Lightweight plugin to ensure access via SSL\u002FHTTPS. Uses 301 (permanent) redirects for SEO benefits. Optionally sets HSTS and forces canonical domain.",200,2868,"2025-12-09T11:40:00.000Z","4.6","5.3",[19,100,57,22,101],"redirection","ssl","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-ssl-redirects.1.1.4.zip",{"slug":104,"name":105,"version":6,"author":106,"author_profile":107,"description":108,"short_description":109,"active_installs":35,"downloaded":110,"rating":49,"num_ratings":84,"last_updated":111,"tested_up_to":112,"requires_at_least":113,"requires_php":59,"tags":114,"homepage":116,"download_link":117,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"https-social-migration","HTTPS Social Migration","Cristian Worthington","https:\u002F\u002Fprofiles.wordpress.org\u002Fcrisworth\u002F","\u003Cp>Migrating a WordPress site from HTTP to HTTPS can be easily achieved with HTTPS Social Migration.This plugin checks to make sure your SSL Certificate is properly installed and makes the necessary changes to refer your incoming web traffic to HTTPS.\u003C\u002Fp>\n\u003Cp>This plugin contains a link to a Premium version of the plugin (HTTPS Social Migration Pro), which addresses a range of other problems that can occur when you migrate your site to HTTPS, including, loss of social media counts, loss of social credibility, problems with other plugins on your site and the need to turn HTTPS off on certain pages.\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FYML8Lao4l5U?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Premium Support\u003C\u002Fstrong>\u003Cbr \u002F>\n  MediaVidi provides support for HTTPS Social Migration Pro (our premium version), which you can access at https:\u002F\u002FMediaVidi.com\u002Fhttps\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Tags\u003C\u002Fh4>\n\u003Cp>seo, SEO, google, https, HTTPS, migrate https, social media, ssl, SSL, migrate ssl, migrate, counts, social media counts, social media shares, recover social media counts, social media counters\u003C\u002Fp>\n","Migrate your Wordpress site from HTTP to HTTPS with HTTPS Social Migration.",2673,"2016-03-03T23:29:00.000Z","4.4.34","4.0",[115,19,22],"google","https:\u002F\u002Fmediavidi.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhttps-social-migration.zip",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":13,"downloaded":126,"rating":13,"num_ratings":13,"last_updated":59,"tested_up_to":52,"requires_at_least":97,"requires_php":17,"tags":127,"homepage":59,"download_link":131,"security_score":49,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":132},"staging-bot-block","Staging Bot Block","1.0.1","Jared Pomranky","https:\u002F\u002Fprofiles.wordpress.org\u002Fjaredpomranky\u002F","\u003Cp>Staging sites often get accidentally indexed by Google or Bing, leading to duplicate content, keyword cannibalization, and production pages being outranked by staging domains. This plugin prevents that from happening.\u003C\u002Fp>\n\u003Cp>Staging Bot Block can:\u003Cbr \u002F>\n* Block search engine bots with a 403 response and proper X-Robots-Tag headers.\u003Cbr \u002F>\n* Redirect bots (or bots and users) to your production domain when needed.\u003Cbr \u002F>\n* Display a persistent warning banner inside the WordPress admin so developers never forget that staging protections are active.\u003Cbr \u002F>\n* Support additional user agents through an easy settings field.\u003C\u002Fp>\n\u003Ch3>Important Notes for Staging Environments\u003C\u002Fh3>\n\u003Cp>If your hosting platform or CDN uses full-page caching (such as Cloudflare APO, WP Rocket’s page cache, or server-level varnish), cached HTML may be served directly without loading WordPress. When this happens, Staging Bot Block cannot inspect user agents, block bots, or send redirect headers.\u003C\u002Fp>\n\u003Cp>To ensure correct behavior:\u003Cbr \u002F>\n* Disable Cloudflare APO or create a Cache Rule to bypass cache for the staging subdomain or for Googlebot\u002FBingbot.\u003Cbr \u002F>\n* Clear or disable caching plugins on staging.\u003Cbr \u002F>\n* Avoid server-level caching for staging domains.\u003C\u002Fp>\n\u003Cp>Once caching is disabled or bypassed, all HTML pages will properly return a 403 for blocked bots or a redirect when configured.\u003C\u002Fp>\n","Prevent search engines from indexing staging sites by blocking or redirecting bots, with a clear admin warning banner.",135,[128,129,130,22,23],"bot-block","redirects","robots","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fstaging-bot-block.1.0.1.zip","2026-03-15T10:48:56.248Z",{"attackSurface":134,"codeSignals":150,"taintFlows":157,"riskAssessment":158,"analyzedAt":161},{"hooks":135,"ajaxHandlers":146,"restRoutes":147,"shortcodes":148,"cronEvents":149,"entryPointCount":13,"unprotectedCount":13},[136,142],{"type":137,"name":138,"callback":139,"file":140,"line":141},"action","registered_taxonomy","wp_relative_url_buffer_start","wp-relative-url.php",35,{"type":137,"name":143,"callback":144,"file":140,"line":145},"shutdown","wp_relative_url_buffer_end",36,[],[],[],[],{"dangerousFunctions":151,"sqlUsage":152,"outputEscaping":154,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":156},[],{"prepared":13,"raw":13,"locations":153},[],{"escaped":84,"rawEcho":13,"locations":155},[],[],[],{"summary":159,"deductions":160},"The \"wp-relative-url\" plugin version 1.0.0 demonstrates a strong security posture based on the provided static analysis. The absence of any identified dangerous functions, file operations, external HTTP requests, and the complete reliance on prepared statements for SQL queries are excellent indicators of secure coding practices. The fact that all output is properly escaped further mitigates risks of cross-site scripting vulnerabilities. Furthermore, the plugin exhibits a very small attack surface, with no AJAX handlers, REST API routes, shortcodes, or cron events, and crucially, no unprotected entry points were detected.\n\nThe vulnerability history for this plugin is completely clean, with no recorded CVEs of any severity. This lack of past vulnerabilities, combined with the current analysis showing zero critical or high severity taint flows, suggests a stable and well-maintained codebase. This history implies that the developers are likely diligent in addressing security concerns or that the plugin's functionality is inherently simple, reducing the likelihood of complex vulnerabilities.\n\nOverall, the \"wp-relative-url\" plugin 1.0.0 appears to be a very secure option. The code analysis reveals no immediate or latent security flaws, and the lack of historical vulnerabilities reinforces this assessment. While the absence of capability checks and nonce checks could be a concern in plugins with a larger attack surface or more sensitive operations, for a plugin with zero identified entry points, this is not a significant risk. The plugin's minimal functionality and clean codebase are its primary security strengths.",[],"2026-03-16T23:42:51.460Z",{"wat":163,"direct":168},{"assetPaths":164,"generatorPatterns":165,"scriptPaths":166,"versionParams":167},[],[],[],[],{"cssClasses":169,"htmlComments":170,"htmlAttributes":171,"restEndpoints":172,"jsGlobals":173,"shortcodeOutput":174},[],[],[],[],[],[]]