[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f78UMoEubQThU1vGKPzWsPl7HdZ9gSe2Oo74fmze72AY":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":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":40,"analysis":129,"fingerprints":175},"cs-remove-version-number-from-css-js","CS Remove Version Number From CSS & JS","1.0.1","Chetan Satasiya","https:\u002F\u002Fprofiles.wordpress.org\u002Fketuchetan\u002F","\u003Cp>This plugin will remove the version number from CSS and JS files.\u003C\u002Fp>\n","This plugin will remove the version number from CSS and JS files.",200,4930,100,1,"2022-01-27T04:59:00.000Z","5.9.13","3.0.1","",[20,21,22,23,24],"css","js","remove","remover-version-number","version","http:\u002F\u002Fchetansatasiya.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcs-remove-version-number-from-css-js.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":36,"avg_patch_time_days":37,"trust_score":38,"computed_at":39},"ketuchetan",5,290,88,30,86,"2026-04-04T11:06:01.188Z",[41,58,77,97,113],{"slug":42,"name":43,"version":6,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":13,"downloaded":48,"rating":13,"num_ratings":14,"last_updated":49,"tested_up_to":50,"requires_at_least":17,"requires_php":51,"tags":52,"homepage":55,"download_link":56,"security_score":57,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"manageremove-version-number-from-css-js","Manage\u002FRemove version number from CSS & JS","Chetan Vaghela","https:\u002F\u002Fprofiles.wordpress.org\u002Fthechetanvaghela\u002F","\u003Cp>The plugin allows you to manage or remove the version number from CSS and JS files.\u003C\u002Fp>\n","This plugin provide an option to manage or remove the version number from CSS and JS files.",2126,"2024-05-01T13:41:00.000Z","6.5.8","7.0",[53,54,22,24],"js-css","manage","https:\u002F\u002Fgithub.com\u002Fthechetanvaghela\u002Fmanage-remove-version-number-from-css-js","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmanageremove-version-number-from-css-js.zip",92,{"slug":59,"name":60,"version":61,"author":62,"author_profile":63,"description":64,"short_description":65,"active_installs":13,"downloaded":66,"rating":13,"num_ratings":14,"last_updated":67,"tested_up_to":68,"requires_at_least":69,"requires_php":18,"tags":70,"homepage":18,"download_link":76,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-version-tag-remover","WP Version Tag Remover","2.1","Arul Prasad J","https:\u002F\u002Fprofiles.wordpress.org\u002Farulprasadj\u002F","\u003Cp>This is a lightweight WordPress plugin that removes the WordPress, CSS and JS version information that gets appended to URLs from your website header.\u003C\u002Fp>\n\u003Cp>If you love this plugin, \u003Ca href=\"https:\u002F\u002Fpaypal.me\u002Farulprasadj?locale.x=en_GB\" rel=\"nofollow ugc\">buy me a cup of coffee\u003C\u002Fa>\u003C\u002Fp>\n\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\u002FpSYiwBlvONc?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>\n","This plugin will remove the WordPress, CSS and JS version from your website header.",4710,"2025-04-25T13:30:00.000Z","6.8.5","4.0",[71,72,73,74,75],"css-version","generator","generator-tag-remover","js-version","wordpress-version","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-version-tag-remover.2.1.zip",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":84,"active_installs":85,"downloaded":86,"rating":13,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":18,"requires_php":90,"tags":91,"homepage":95,"download_link":96,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"disable-css-js-cache","Disable CSS JS Cache","1.0.9","Umang Prajapati","https:\u002F\u002Fprofiles.wordpress.org\u002Fumangapps48\u002F","\u003Cp>WordPress has built-in caching mechanisms for CSS and JS files to improve website performance by reducing the load time. However, sometimes these caching mechanisms can cause issues such as outdated CSS or JS files being loaded, resulting in display issues on your website. For solution, we provide option to load page with updated css and js.\u003C\u002Fp>\n\u003Cp>We have also added static file cache option. This will help you to fix “Serve static assets with an efficient cache policy” error and improve perfomance of website.\u003C\u002Fp>\n\u003Cp>Say goodbye to the frustration of stale CSS and JS files causing display issues, and embrace the power to control cache settings with ease.\u003C\u002Fp>\n\u003Ch3>Core plugin Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Instantly Disable CSS and JS Cache:\u003C\u002Fstrong> The plugin provides a simple toggle switch to disable caching for CSS and JS files with just a single click. No coding or complex configurations required. This feature allows you to quickly bypass caching for these critical files and ensure seamless updates and changes reflect immediately.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Smart Cache Busting (New):\u003C\u002Fstrong> Choose between Force Refresh (timestamp) or Smart Refresh (file modification time). Smart Refresh only updates the version when the file is actually modified, which is better for performance.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Exclude Specific Paths (New):\u003C\u002Fstrong> You can now exclude specific files or paths from cache busting. Simply enter them in the settings page.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Prevent Display Issues:\u003C\u002Fstrong> When making changes to your website’s CSS or JS files, caching can often cause display issues where the changes don’t reflect in the user’s browser. “Disable CSS JS Cache” eliminates this problem, allowing you to make real-time updates and maintain a consistently smooth user experience.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Fine-Grained Control:\u003C\u002Fstrong> The plugin gives you the flexibility to choose which CSS and JS files you want to bypass caching for. You can disable cache for specific files or include\u002Fexclude entire directories, granting you granular control over caching behavior.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Compatibility with Caching Plugins:\u003C\u002Fstrong> Worried about conflicts with your existing caching plugins? Fear not! “Disable CSS JS Cache” is designed to work seamlessly with popular caching plugins, ensuring your website’s performance and caching settings remain optimized.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Easy to Use and Lightweight:\u003C\u002Fstrong> This plugin is built with simplicity in mind. Its intuitive user interface makes it effortless for anyone, regardless of technical expertise, to manage CSS and JS caching effectively. Additionally, the plugin is lightweight, ensuring it won’t slow down your website’s loading times.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>No Coding Required:\u003C\u002Fstrong> You don’t need to be a coding expert to leverage the power of this plugin. With a user-friendly interface and a focus on simplicity, “Disable CSS JS Cache” is accessible to all WordPress users, from beginners to advanced developers.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin helps prevent browser caching of CSS and JS files from theme in WordPress.",400,3941,2,"2026-02-16T17:55:00.000Z","6.9.4","7.2",[92,93,78,94],"clear-cache","disable-cache","remove-cache","https:\u002F\u002Fphptutorialpoints.in","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-css-js-cache.zip",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":11,"downloaded":105,"rating":13,"num_ratings":34,"last_updated":106,"tested_up_to":107,"requires_at_least":17,"requires_php":18,"tags":108,"homepage":111,"download_link":112,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"filename-based-asset-cache-busting","Filename based asset cache busting","1.4","benlumley","https:\u002F\u002Fprofiles.wordpress.org\u002Fbenlumley\u002F","\u003Cp>Filename based cache busting for WordPress scripts\u002Fstyles using last modified date.\u003C\u002Fp>\n\u003Cp>Stop telling clients or users to hard refresh \u002F shift refresh. The url to all of the css\u002Fjs files on your site will change automatically whenever the files are modified. You can set proper long cache lifetimes to help get top scores on Google Pagespeed without running into cached css\u002Fjavascript problems.\u003C\u002Fp>\n\u003Cp>Based on this gist https:\u002F\u002Fgist.github.com\u002Focean90\u002F1966227 from Dominik Schilling, I’ve enhanced it by automatically replacing the asset version with the files modification time and automatically editing htaccess – making it install + forget.\u003C\u002Fp>\n\u003Cp>Includes querystring option as a fallback – which works in more scenarios.\u003C\u002Fp>\n\u003Ch3>Webservers\u003C\u002Fh3>\n\u003Ch4>Apache\u003C\u002Fh4>\n\u003Cp>The plugin should add what it needs to your .htaccess file jsut like WP itself. But if for any reason that doesn’t work for you – here’s what it adds:\u003C\u002Fp>\n\u003Cpre>\u003Ccode># FBACB\n\u003CIfModule mod_rewrite.c>\n  RewriteEngine On\n  RewriteBase \u002F\n\n  RewriteCond %{REQUEST_FILENAME} !-f\n  RewriteCond %{REQUEST_FILENAME} !-d\n  RewriteRule ^(.+)\\.([0-9\\.]+)\\.(js|css)$ $1.$3 [L]\n\u003C\u002FIfModule>\n\n# still fbacb\n\u003CIfModule mod_expires.c>\n    ExpiresActive on\n    ExpiresByType text\u002Fcss                            \"access plus 1 year\"\n    ExpiresByType application\u002Fjavascript              \"access plus 1 year\"\n\u003C\u002FIfModule>\n# END FBACB\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>NGINX\u003C\u002Fh4>\n\u003Cpre>\u003Ccode> location ~* ^(.+)\\.(?:\\d+)\\.(min.js|min.css|js|css)($|\\?.*$) {\n   try_files $uri $1.$2;\n }\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Host specific notes\u003C\u002Fh3>\n\u003Cp>Some webhosts need a bit of custom config to get the filename based urls working.\u003C\u002Fp>\n\u003Ch4>WP Engine\u003C\u002Fh4>\n\u003Cp>To work on WP-Engine, you’ll need the following redirect added via my.wpengine -> installname -> Redirect rules\u003C\u002Fp>\n\u003Cpre>\u003Ccode> Source: ^(.+)\\.([0-9\\.]+)\\.(js|css)$\n Dest: $1.$3\n Type: break (this is under advanced)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>CloudWays\u003C\u002Fh4>\n\u003Cp>Just works.\u003C\u002Fp>\n\u003Ch4>Flywheel\u003C\u002Fh4>\n\u003Cp>Just works.\u003C\u002Fp>\n\u003Ch4>PHP Fallback\u003C\u002Fh4>\n\u003Cp>If your webserver is failing to serve assets using url rewriting, the plugin attempts to serve them itsef (ie: via PHP). Obviously this is slow\u002Fless than ideal in production (it’ll be much slower) – so you should configure your web server correctly to serve the files. If you see this HTTP header “FBACB-Php-Fallback: yes” on your assets, this applies to you.\u003C\u002Fp>\n\u003Cp>Note that hosts are increasingly configured to serve css\u002Fjs directly from disk and won’t fall back to PHP + WordPress error handling – this fallback then won’t work.\u003C\u002Fp>\n","Filename based cache busting for WordPress scripts\u002Fstyles using last modified date.",9968,"2020-04-27T21:47:00.000Z","5.4.19",[109,110,20,21,24],"asset","assets","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffilename-based-asset-cache-busting\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffilename-based-asset-cache-busting.zip",{"slug":114,"name":115,"version":116,"author":117,"author_profile":118,"description":119,"short_description":120,"active_installs":11,"downloaded":121,"rating":122,"num_ratings":87,"last_updated":123,"tested_up_to":68,"requires_at_least":17,"requires_php":18,"tags":124,"homepage":127,"download_link":128,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"remove-code-version-tags","No Version Tags","1.0","George Gkouvousis","https:\u002F\u002Fprofiles.wordpress.org\u002Fgkouvousisg\u002F","\u003Cp>Simple, \u003Cstrong>yet effective\u003C\u002Fstrong> plugin that once activated, it will \u003Cstrong>eliminate every CSS version tag\u003C\u002Fstrong> of WordPress plugins, core & themes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Bonus\u003C\u002Fstrong>: your website will receive a small boost of SEO, you will experience no CSS caching issues anymore and hackers wont be able to recognize your version numbers.\u003C\u002Fp>\n\u003Cp>Try its demo \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fapps.8web.gr\u002Fdemos\u002Fwordpress-remove-versions-from-code-plugin\u002F\" rel=\"nofollow ugc\">here\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n","Description: Upon activation, this plugin will automatically eliminate the annoying '?ver=x.x' signs from your perfect code :)",2957,90,"2025-04-08T04:57:00.000Z",[125,126,75],"css-versions","remove-version","http:\u002F\u002Fplugins.wordpress.org\u002Fno-version-tags","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-code-version-tags.zip",{"attackSurface":130,"codeSignals":159,"taintFlows":166,"riskAssessment":167,"analyzedAt":174},{"hooks":131,"ajaxHandlers":155,"restRoutes":156,"shortcodes":157,"cronEvents":158,"entryPointCount":28,"unprotectedCount":28},[132,138,141,143,146,148,152],{"type":133,"name":134,"callback":135,"file":136,"line":137},"action","plugins_loaded","anonymous","includes\\class-cs-remove-version-number-from-css-js.php",139,{"type":133,"name":139,"callback":135,"file":136,"line":140},"admin_enqueue_scripts",154,{"type":133,"name":139,"callback":135,"file":136,"line":142},155,{"type":133,"name":144,"callback":135,"file":136,"line":145},"wp_enqueue_scripts",170,{"type":133,"name":144,"callback":135,"file":136,"line":147},171,{"type":149,"name":150,"callback":135,"file":136,"line":151},"filter","style_loader_src",172,{"type":149,"name":153,"callback":135,"file":136,"line":154},"script_loader_src",173,[],[],[],[],{"dangerousFunctions":160,"sqlUsage":161,"outputEscaping":163,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":165},[],{"prepared":28,"raw":28,"locations":162},[],{"escaped":28,"rawEcho":28,"locations":164},[],[],[],{"summary":168,"deductions":169},"This plugin, \"cs-remove-version-number-from-css-js\" v1.0.1, exhibits a strong security posture based on the provided static analysis.  The absence of any identified dangerous functions, raw SQL queries, unescaped output, file operations, external HTTP requests, or taint analysis findings indicates a clean codebase with good security practices.  The zero-attack surface for entry points, including AJAX handlers and REST API routes, further reinforces this positive assessment. The vulnerability history being entirely clear suggests the developers have a good track record regarding security.\n\nHowever, the complete lack of nonce checks and capability checks across all potential interaction points (even though the attack surface is currently zero) represents a theoretical concern. If the plugin were to introduce new features or endpoints in the future, this absence of fundamental security controls could become a significant weakness. For its current functionality, which appears to be purely informational or passive, the risk is minimal. Nevertheless, it's a practice that warrants improvement for future development to ensure robustness against potential future vulnerabilities.",[170,172],{"reason":171,"points":34},"No nonce checks implemented",{"reason":173,"points":34},"No capability checks implemented","2026-03-16T20:24:42.017Z",{"wat":176,"direct":184},{"assetPaths":177,"generatorPatterns":180,"scriptPaths":181,"versionParams":183},[178,179],"\u002Fwp-content\u002Fplugins\u002Fcs-remove-version-number-from-css-js\u002Fcss\u002Fcs-remove-version-number-from-css-js-admin.css","\u002Fwp-content\u002Fplugins\u002Fcs-remove-version-number-from-css-js\u002Fjs\u002Fcs-remove-version-number-from-css-js-admin.js",[],[182],"js\u002Fcs-remove-version-number-from-css-js-admin.js",[],{"cssClasses":185,"htmlComments":186,"htmlAttributes":187,"restEndpoints":188,"jsGlobals":189,"shortcodeOutput":190},[],[],[],[],[],[]]