[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fu5ZKBnoHWKYakUFUt2heiVsafEg4gQWViQWn3vtRwzQ":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":16,"requires_php":16,"tags":17,"homepage":18,"download_link":19,"security_score":20,"vuln_count":21,"unpatched_count":21,"last_vuln_date":22,"fetched_at":23,"vulnerabilities":24,"developer":25,"crawl_stats":22,"alternatives":32,"analysis":33,"fingerprints":58},"wp-sha1","WP SHA1","1.0","bruno.sousa","https:\u002F\u002Fprofiles.wordpress.org\u002Fbrunosousa-1\u002F","\u003Cp>Authenticate SHA1 passwords too.\u003C\u002Fp>\n","Authenticate SHA1 passwords too.",10,1483,100,1,"2012-05-24T02:03:00.000Z","",[],"http:\u002F\u002Fwww.brunosou.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-sha1.zip",85,0,null,"2026-03-15T14:54:45.397Z",[],{"slug":26,"display_name":7,"profile_url":8,"plugin_count":27,"total_installs":28,"avg_security_score":20,"avg_patch_time_days":29,"trust_score":30,"computed_at":31},"brunosousa-1",2,20,30,84,"2026-04-04T14:12:52.260Z",[],{"attackSurface":34,"codeSignals":46,"taintFlows":53,"riskAssessment":54,"analyzedAt":57},{"hooks":35,"ajaxHandlers":42,"restRoutes":43,"shortcodes":44,"cronEvents":45,"entryPointCount":21,"unprotectedCount":21},[36],{"type":37,"name":38,"callback":39,"priority":11,"file":40,"line":41},"filter","check_password","checkme","wpsha1.php",73,[],[],[],[],{"dangerousFunctions":47,"sqlUsage":48,"outputEscaping":50,"fileOperations":21,"externalRequests":21,"nonceChecks":21,"capabilityChecks":21,"bundledLibraries":52},[],{"prepared":21,"raw":21,"locations":49},[],{"escaped":21,"rawEcho":21,"locations":51},[],[],[],{"summary":55,"deductions":56},"The wp-sha1 plugin v1.0 exhibits an exceptionally strong security posture based on the provided static analysis data. The absence of any identified attack surface, dangerous functions, SQL queries (or 100% use of prepared statements), file operations, external HTTP requests, or taint flows indicates a meticulously crafted codebase that avoids common vulnerabilities. Furthermore, the plugin correctly implements output escaping and demonstrates no known historical vulnerabilities, suggesting a history of secure development and maintenance.  The plugin's strength lies in its apparent lack of functionality that would introduce typical WordPress plugin vulnerabilities.  While this is a highly positive sign, it also implies that the plugin likely has minimal features, which could be a trade-off for its security.  However, based solely on the provided data, the plugin is highly secure.",[],"2026-03-16T23:38:36.344Z",{"wat":59,"direct":64},{"assetPaths":60,"generatorPatterns":61,"scriptPaths":62,"versionParams":63},[],[],[],[],{"cssClasses":65,"htmlComments":66,"htmlAttributes":67,"restEndpoints":68,"jsGlobals":69,"shortcodeOutput":70},[],[],[],[],[],[]]