[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fa2i0wmRDmWpRiG-XUbY9azBDoNqWrlU3Mles8xdndx8":3,"$frd9axcMMSGBsRj_50nS-62FZrHpoIR3nNw-TBIuExBw":188,"$f-FaOTH-Y4Ot7usoAHC97jo4uaZqtkcX4LeTnd0QHdKk":193},{"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,"discovery_status":31,"vulnerabilities":32,"developer":33,"crawl_stats":29,"alternatives":40,"analysis":149,"fingerprints":174},"evolution-footer-scripts","AH Footer Scripts","1.0.2","Andreas Hecht","https:\u002F\u002Fprofiles.wordpress.org\u002Fahecht\u002F","\u003Cp>This small plugin moves all scripts (including jQuery) to the footer to help speed up page load times, while keep stylesheets in the header. Note that this only works if you have plugins and a theme that utilizes wp_enqueue_scripts correctly.\u003C\u002Fp>\n","This small plugin moves all scripts (including jQuery) to the footer to help speed up page load times, while keep stylesheets in the header.",10,3454,100,2,"2017-09-23T17:00:00.000Z","4.8.28","4.7.0","",[20,21,22,23,24],"footer","javascript","jquery","performance","speed","https:\u002F\u002Fandreas-hecht.com\u002Fah-footer-scripts\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fevolution-footer-scripts.1.0.2.zip",85,0,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":34,"display_name":7,"profile_url":8,"plugin_count":35,"total_installs":36,"avg_security_score":27,"avg_patch_time_days":37,"trust_score":38,"computed_at":39},"ahecht",8,9820,30,84,"2026-05-20T02:19:51.378Z",[41,62,83,103,122],{"slug":42,"name":43,"version":44,"author":45,"author_profile":46,"description":47,"short_description":48,"active_installs":49,"downloaded":50,"rating":51,"num_ratings":52,"last_updated":53,"tested_up_to":54,"requires_at_least":55,"requires_php":56,"tags":57,"homepage":59,"download_link":60,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":61},"scripts-to-footerphp","Scripts To Footer","0.7.3","Joshua David Nelson","https:\u002F\u002Fprofiles.wordpress.org\u002Fjoshuadnelson\u002F","\u003Cp>This small plugin moves scripts to the footer. Note that this only works if you have plugins and a theme that utilizes \u003Ccode>wp_enqueue_scripts\u003C\u002Fcode> correctly.\u003C\u002Fp>\n\u003Cp>You can disable the plugin on specific pages and posts directly via the post\u002Fpage edit screen metabox.\u003C\u002Fp>\n\u003Cp>You can disable the plugin on specific archive pages (blog page, search page, post type and taxonomy archives) via the settings page.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Everything Broken?\u003C\u002Fstrong> Try placing jQuery back into the header via Settings > Scripts to Footer, “Keep jQuery in the Header” checkbox. If that doesn’t work, refer to the walkthrough below for using the \u003Ccode>stf_exclude_scripts\u003C\u002Fcode> filter for the script that is causing the issue.\u003C\u002Fp>\n\u003Cp>Check out the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjoshuadavidnelson\u002Fscripts-to-footer\u002Fwiki\" rel=\"nofollow ugc\">documentation\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjoshuadavidnelson\u002Fscripts-to-footer\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> or some quick walkthroughs below.\u003C\u002Fp>\n\u003Ch4>Keeping specific Scripts in the Header\u003C\u002Fh4>\n\u003Cp>As of version 0.6 you can now keep specific scripts in the header. Note: this will print any scripts they depend on as well (if you want to keep \u003Ccode>jquery-effects-core\u003C\u002Fcode> in the header, you’ll also get \u003Ccode>jQuery\u003C\u002Fcode> in the header, so no need to add both).\u003C\u002Fp>\n\u003Cp>Specifically for jQuery, see the settings page option, as it is a common request we’ve built it into the settings.\u003C\u002Fp>\n\u003Cp>For any other scripts, use this filter:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter( 'stf_exclude_scripts', 'jdn_header_scripts', 10, 1 );\nfunction jdn_header_scripts( $scripts ) {\n\n    $scripts[] = 'backbone'; \u002F\u002F Replace 'backbone' with the script slug\n\n    return $scripts;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You will need the correct script slug, which is used when the script is registered, and the script will only be printed into the header \u003Cem>if it’s enqueued\u003C\u002Fem>. Check out the scripts that come registered \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_enqueue_script#Default_Scripts_Included_and_Registered_by_WordPress\" rel=\"nofollow ugc\">out-of-the-box with WordPress\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> As of version 0.6.3, \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FConditional_Tags\" rel=\"nofollow ugc\">conditional tags\u003C\u002Fa> will work with the \u003Ccode>stf_exclude_scripts\u003C\u002Fcode> filter.\u003C\u002Fp>\n\u003Ch4>Custom Post Type Support\u003C\u002Fh4>\n\u003Cp>If you’re comfortable with code you can use the \u003Ccode>scripts_to_footer_post_types\u003C\u002Fcode> filter to change the post types this applies to (it only applies to pages and posts by default). For example, if you have a custom post type called “project” you could add support for this metabox via the post type filter like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function stf_add_cpt_support( $post_types ) {\n\n    $post_types[] = 'project';\n\n    return $post_types;\n}\nadd_filter( 'scripts_to_footer_post_types', 'stf_add_cpt_support' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Excluding Pages\u002FPosts\u002FTemplates Via Filter\u003C\u002Fh4>\n\u003Cp>You can either use the checkbox option to disable the plugin’s action on a specific page\u002Fpost, or you can utilize a filter. The filter also passes the post\u002Fpage id, if there is one (archive templates don’t have ids!).\u003C\u002Fp>\n\u003Cp>For example, for the “page” post type:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function stf_exclude_my_page( $exclude_page, $post_id ) {\n\n    if ( is_front_page() ) {\n        $exclude_page = 'on'; \u002F\u002F this turns on the \"exclude\" option\n    }\n\n    return $exclude_page;\n}\nadd_filter( 'stf_page', 'stf_exclude_my_page' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Replace \u003Ccode>stf_page\u003C\u002Fcode> with \u003Ccode>stf_post\u003C\u002Fcode> for posts, or the slug of your custom post type. For instance, a post type called “project” can be filtered with \u003Ccode>stf_project\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>More Documentation\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjoshuadavidnelson\u002Fscripts-to-footer\u002Fwiki\" rel=\"nofollow ugc\">See the plugin’s wiki\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Development \u002F Contributing\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjoshuadavidnelson\u002Fscripts-to-footer\" rel=\"nofollow ugc\">View this plugin on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>Please feel free to open a \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjoshuadavidnelson\u002Fscripts-to-footer\u002Fissues\" rel=\"nofollow ugc\">Github Issue\u003C\u002Fa> to report conflicts or goto \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fscripts-to-footerphp\" rel=\"ugc\">the WP.org support forum\u003C\u002Fa>. If there is something wrong with Scripts-to-Footer, we’ll update it. However, if it’s a another plugin or theme we can only contact the developer with the issue to attempt to resolve it.\u003C\u002Fp>\n","Move your scripts to the footer to help speed up perceived page load times and improve user experience.",8000,253977,94,37,"2025-11-17T02:54:00.000Z","6.8.5","5.3","7.4",[20,58,21,23,24],"head","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fscripts-to-footerphp\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fscripts-to-footerphp.0.7.3.zip","2026-04-16T10:56:18.058Z",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":51,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":18,"tags":76,"homepage":80,"download_link":81,"security_score":38,"vuln_count":14,"unpatched_count":28,"last_vuln_date":82,"fetched_at":61},"async-javascript","Async JavaScript","2.21.08.31","David Clough","https:\u002F\u002Fprofiles.wordpress.org\u002Fcloughit\u002F","\u003Cp>Eliminate Render-blocking Javascript in above-the-fold content with Async Javascript.\u003C\u002Fp>\n\u003Cp>Render-blocking Javascript prevents above-the-fold content on your page from being rendered until the javascript has finished loading. This can impact on your page speed and ultimately your ranking within search engines. It can also impact your user’s experience.\u003C\u002Fp>\n\u003Cp>Async JavaScript gives you full control of which scripts to add an ‘async’ or ‘defer’ attribute to or to exclude to help increase the performance of your WordPress website.\u003C\u002Fp>\n","Async Javascript lets you add 'async' or 'defer' attribute to scripts to exclude to help increase the performance of your WordPres …",70000,2050702,102,"2023-06-22T08:00:00.000Z","6.2.9","4.6",[77,21,78,23,79],"async","pagespeed","render-blocking","https:\u002F\u002Fautoptimize.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fasync-javascript.2.21.08.31.zip","2021-06-13 00:00:00",{"slug":84,"name":85,"version":86,"author":87,"author_profile":88,"description":89,"short_description":90,"active_installs":91,"downloaded":92,"rating":93,"num_ratings":94,"last_updated":95,"tested_up_to":96,"requires_at_least":97,"requires_php":18,"tags":98,"homepage":101,"download_link":102,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":61},"use-google-libraries","Use Google Libraries","1.6.2.3","Jason Penney","https:\u002F\u002Fprofiles.wordpress.org\u002Fjczorkmid\u002F","\u003Cp>A number of the javascript libraries distributed with WordPress are also\u003Cbr \u002F>\nhosted on Google’s \u003Ca href=\"http:\u002F\u002Fcode.google.com\u002Fapis\u002Fajaxlibs\u002F\" rel=\"nofollow ugc\">AJAX Libraries API\u003C\u002Fa>.\u003Cbr \u002F>\nThis plugin allows your WordPress site to use the content distribution\u003Cbr \u002F>\nnetwork side of Google’s AJAX Library API, rather than serving these files from your WordPress install directly.\u003C\u002Fp>\n\u003Cp>This provides numerous potential performance benefits:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>increases the chance that a user already has these files cached\u003C\u002Fli>\n\u003Cli>takes load off your server\u003C\u002Fli>\n\u003Cli>uses compressed versions of the libraries (where available)\u003C\u002Fli>\n\u003Cli>Google’s servers are set up to negotiate HTTP compression with the requesting browser\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For a more detailed look see Dave Ward’s \u003Ca href=\"https:\u002F\u002Fweb-beta.archive.org\u002Fweb\u002F20101216143500\u002Fencosia.com\u002F2008\u002F12\u002F10\u002F3-reasons-why-you-should-let-google-host-jquery-for-you\u002F\" rel=\"nofollow ugc\">3 reasons why you should let\u003Cbr \u002F>\nGoogle host jQuery for\u003Cbr \u002F>\nyou\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Supported Libraries and Components\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fdojotoolkit.org\u002F\" rel=\"nofollow ugc\">Dojo\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fjquery.com\u002F\" rel=\"nofollow ugc\">jQuery\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fui.jquery.com\u002F\" rel=\"nofollow ugc\">jQuery UI\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fmootools.net\u002F\" rel=\"nofollow ugc\">MooTools\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fwww.prototypejs.org\u002F\" rel=\"nofollow ugc\">Prototype\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fscript.aculo.us\u002F\" rel=\"nofollow ugc\">script.aculo.us\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fcode.google.com\u002Fp\u002Fswfobject\u002F\" rel=\"nofollow ugc\">swfobject\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Links\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fjasonpenney.net\u002Fwordpress-plugins\u002Fuse-google-libraries\u002F\" rel=\"nofollow ugc\">Use Google Libraries Home\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fgithub.com\u002Fjpenney\u002Fuse-google-libraries\u002Fissues\" rel=\"nofollow ugc\">Issue Tracker\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fgithub.com\u002Fjpenney\u002Fuse-google-libraries\" rel=\"nofollow ugc\">GitHub Repository\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fuse-google-libraries\" rel=\"ugc\">Support Forum\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Incompatible Plugins\u003C\u002Fh3>\n\u003Ch4>Better WordPress Minify\u003C\u002Fh4>\n\u003Cp>Better WordPress Minify version 1.2.2 does not yet support\u003Cbr \u002F>\nprotocol-relative URLs, but \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fconflict-with-use-google-libraries-152\" rel=\"ugc\">the next release is supposed to correct\u003Cbr \u002F>\nthis\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Gravity Forms\u003C\u002Fh4>\n\u003Cp>I’ve had reports of Gravity Forms breaking UGL, but I don’t have\u003Cbr \u002F>\naccess to Gravity Forms, so I’m not sure what’s going on.  If you need\u003Cbr \u002F>\nGravity Forms you might need to disable UGL, or it might be fine, I’m\u003Cbr \u002F>\nnot really sure.\u003C\u002Fp>\n\u003Ch4>WP-Minify\u003C\u002Fh4>\n\u003Cp>WP-Minify doesn’t yet support protocol-relative URLs.  Add\u003Cbr \u002F>\n‘\u002F\u002Fajax.googleapis.com\u002F’ as a JS and CSS exclusion.\u003C\u002Fp>\n\u003Ch3>Incompatible Themes\u003C\u002Fh3>\n\u003Ch4>K2\u003C\u002Fh4>\n\u003Cp>I’ve had scattered reports that UGL is stepping out of the way when\u003Cbr \u002F>\nusing K2.\u003C\u002Fp>\n\u003Ch3>A Request\u003C\u002Fh3>\n\u003Cp>If you’re going to flag the plugin as “broken” in the WordPress Plugin\u003Cbr \u002F>\nDirectory, please try and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Ftags\u002Fuse-google-libraries?forum_id=10\" rel=\"ugc\">let me know \u003Cem>what\u003C\u002Fem> is\u003Cbr \u002F>\nbroken\u003C\u002Fa>.\u003Cbr \u002F>\nI’m not a mind reader.\u003C\u002Fp>\n\u003Ch3>Technical Details\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Use Google Libraries\u003C\u002Fstrong> uses the following hooks (each with a priority of 1000).\u003C\u002Fp>\n\u003Ch4>wp_default_scripts\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Use Google Libraries\u003C\u002Fstrong> compares it’s list of supported scripts to those\u003Cbr \u002F>\nregistered, and replaces the standard registrations \u003Ccode>src\u003C\u002Fcode> with ones that\u003Cbr \u002F>\npoint to Google’s servers.  Other attributes (like dependencies) are left\u003Cbr \u002F>\nintact.\u003C\u002Fp>\n\u003Ch4>script_loader_src\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Use Google Libraries\u003C\u002Fstrong> removes the \u003Ccode>ver=x.y.z\u003C\u002Fcode> query string from the URL\u003Cbr \u002F>\nused to load the requested library \u003Cem>if\u003C\u002Fem> it is going to load the library from\u003Cbr \u002F>\n    ajax.googleapis.com.  Otherwise the URL is left unaltered.  This both\u003Cbr \u002F>\nimproves the chances of the given URL already being cached, and prevents\u003Cbr \u002F>\n\u003Cstrong>script.aculo.us\u003C\u002Fstrong> from including scripts multiple times.\u003C\u002Fp>\n\u003Cp>If jQuery is enqued \u003Cstrong>Use Google Libraries\u003C\u002Fstrong> will inject a bit of\u003Cbr \u002F>\njavascript before the next enqueued script enabling jQuery’s \u003Ca href=\"http:\u002F\u002Fdocs.jquery.com\u002FCore\u002FjQuery.noConflict\" rel=\"nofollow ugc\">noConflict mode\u003C\u002Fa> as it would\u003Cbr \u002F>\nwith the standard WordPress version.\u003C\u002Fp>\n\u003Ch3>References\u003C\u002Fh3>\n\u003Cp>Parts of this plugin (specificly, the dropping of the micro number,\u003Cbr \u002F>\nwhich has since been removed for better caching performance) were\u003Cbr \u002F>\ninspired by John Blackbourn’s\u003Cbr \u002F>\n\u003Cstrong>\u003Ca href=\"http:\u002F\u002Flud.icro.us\u002Fwordpress-plugin-google-ajax-libraries\u002F\" rel=\"nofollow ugc\">Google AJAX Libraries\u003C\u002Fa>\u003C\u002Fstrong>,\u003Cbr \u002F>\nwhich has very similar goals to this plugin.\u003C\u002Fp>\n\u003Ch3>Future Plans\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>add ability to disable protocol relative URLs\u003C\u002Fli>\n\u003Cli>add ability to disable on frontend and\u002For admin\u003C\u002Fli>\n\u003C\u002Ful>\n","Allows your site to use common javascript libraries from Google's AJAX Libraries CDN, rather than from WordPress's own copies.",10000,748306,88,47,"2017-11-28T05:16:00.000Z","4.7.33","3.4",[99,100,21,22,23],"cdn","google","http:\u002F\u002Fjasonpenney.net\u002Fwordpress-plugins\u002Fuse-google-libraries\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fuse-google-libraries.zip",{"slug":104,"name":105,"version":106,"author":107,"author_profile":108,"description":109,"short_description":110,"active_installs":111,"downloaded":112,"rating":13,"num_ratings":35,"last_updated":113,"tested_up_to":114,"requires_at_least":115,"requires_php":116,"tags":117,"homepage":120,"download_link":121,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":61},"javascript-autoloader","Smart JavaScript Auto Loader","5.0.3","Peter Raschendorfer","https:\u002F\u002Fprofiles.wordpress.org\u002Fpetersplugins\u002F","\u003Cp>The Smart JavaScript Auto Loader Plugin allows you to load additional JavaScript files without the need to change files in the theme directory\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>To load additional JavaScript files just put them into a directory named \u003Cstrong>jsautoload\u003C\u002Fstrong>. This directory can be placed in three different locations that are loaded in the following order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Child Theme dependent (if using a Child Theme) : in the Child Theme’s directory\u003C\u002Fli>\n\u003Cli>Theme dependent : in the Theme’s directory\u003C\u002Fli>\n\u003Cli>Theme independent : in the wp-content directory\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Only files with extension .js are added, all other files are ignored. Subdirectories can be used and will also be scanned. To ignore a complete directory (including all subdirectories) name the directory beginning with an underscore (_). The files are added in alphabetical order. Directories always are added \u003Cstrong>after\u003C\u002Fstrong> files.\u003C\u002Fp>\n\u003Cp>To load one ore more JavaScript files at the end of your HTML file just place them into a directory named \u003Cstrong>footer\u003C\u002Fstrong>. To add the files to the footer of your theme it is required to call wp_footer() in your footer.php.\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","Load JavaScript files without coding",400,24613,"2024-04-17T20:13:00.000Z","6.3.8","4.0","5.4",[20,118,21,22,119],"header","wp_enqueue_script","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjavascript-autoloader\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjavascript-autoloader.5.0.3.zip",{"slug":123,"name":124,"version":125,"author":126,"author_profile":127,"description":128,"short_description":129,"active_installs":11,"downloaded":130,"rating":13,"num_ratings":131,"last_updated":132,"tested_up_to":133,"requires_at_least":134,"requires_php":18,"tags":135,"homepage":147,"download_link":148,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"admin-menu-slide","Admin Menu Slide","1.0","Maciej Krawczyk","https:\u002F\u002Fprofiles.wordpress.org\u002Fhelium-3\u002F","\u003Cp>Admin Menu Slide is a simple plugin that adds a feature to hide admin menu and make it slide when hovering on the edge of the screen. Works exactly like WordPress collapse menu – you can toggle the feature on\u002Foff by clicking a button, which is at the bottom of admin menu. When enabled, admin pages have full screen width.\u003C\u002Fp>\n","Adds a feature to hide admin menu and make it slide when hovering on the edge of the screen.",2404,1,"2015-07-30T13:50:00.000Z","4.3.34","3.8",[136,137,138,139,140,21,22,141,142,143,144,23,145,146],"admin","administration","backend","dashboard","free","menu","mobile","navigation","page","plugins","sidebar","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadmin-menu-slide","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadmin-menu-slide.1.0.zip",{"attackSurface":150,"codeSignals":162,"taintFlows":169,"riskAssessment":170,"analyzedAt":173},{"hooks":151,"ajaxHandlers":158,"restRoutes":159,"shortcodes":160,"cronEvents":161,"entryPointCount":28,"unprotectedCount":28},[152],{"type":153,"name":154,"callback":155,"file":156,"line":157},"action","wp_enqueue_scripts","evolution_footer_scripts","evolution-footer-scripts.php",40,[],[],[],[],{"dangerousFunctions":163,"sqlUsage":164,"outputEscaping":166,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":168},[],{"prepared":28,"raw":28,"locations":165},[],{"escaped":28,"rawEcho":28,"locations":167},[],[],[],{"summary":171,"deductions":172},"The \"evolution-footer-scripts\" plugin v1.0.2 exhibits an excellent security posture based on the provided static analysis. The code analysis reveals a complete absence of dangerous functions, SQL queries, file operations, external HTTP requests, and indications of inadequate security checks like nonces and capability checks. Taint analysis also shows no identified flows with unsanitized paths, reinforcing the impression of secure coding practices. The plugin also has no recorded vulnerability history, further bolstering confidence in its current security. This lack of identified weaknesses suggests a well-developed and secure plugin.",[],"2026-03-17T00:21:10.299Z",{"wat":175,"direct":181},{"assetPaths":176,"generatorPatterns":178,"scriptPaths":179,"versionParams":180},[177],"\u002Fwp-content\u002Fplugins\u002Fevolution-footer-scripts\u002Fevolution-footer-scripts.php",[],[],[],{"cssClasses":182,"htmlComments":183,"htmlAttributes":184,"restEndpoints":185,"jsGlobals":186,"shortcodeOutput":187},[],[],[],[],[],[],{"error":189,"url":190,"statusCode":191,"statusMessage":192,"message":192},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fevolution-footer-scripts\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":14,"versions":194},[195,201],{"version":6,"download_url":26,"svn_tag_url":196,"released_at":29,"has_diff":197,"diff_files_changed":198,"diff_lines":29,"trac_diff_url":199,"vulnerabilities":200,"is_current":189},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fevolution-footer-scripts\u002Ftags\u002F1.0.2\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fevolution-footer-scripts%2Ftags%2F1.0.1&new_path=%2Fevolution-footer-scripts%2Ftags%2F1.0.2",[],{"version":202,"download_url":203,"svn_tag_url":204,"released_at":29,"has_diff":197,"diff_files_changed":205,"diff_lines":29,"trac_diff_url":29,"vulnerabilities":206,"is_current":197},"1.0.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fevolution-footer-scripts.1.0.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fevolution-footer-scripts\u002Ftags\u002F1.0.1\u002F",[],[]]