[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fG0nS2K4YhlnBk0vTJdGGSD5Q5P6DgXxjX1zci1DNjiA":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":15,"requires_php":16,"tags":17,"homepage":19,"download_link":20,"security_score":21,"vuln_count":13,"unpatched_count":13,"last_vuln_date":22,"fetched_at":23,"vulnerabilities":24,"developer":25,"crawl_stats":22,"alternatives":30,"analysis":31,"fingerprints":61},"remove-admin-bar-menu","Remove Admin Bar Menu","1.1","rounitmorya","https:\u002F\u002Fprofiles.wordpress.org\u002Frounitmorya\u002F","\u003Cp>Easily remove Admin Bar Menu from front End\u003C\u002Fp>\n","Easily remove Admin Bar Menu from front End",30,4219,0,"2011-11-11T06:35:00.000Z","3.2.1","",[18],"admin-bar-menu","http:\u002F\u002Fwordpress.opensourcedevelopers.net\u002Fdownloads\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-admin-bar-menu.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":26,"total_installs":27,"avg_security_score":21,"avg_patch_time_days":11,"trust_score":28,"computed_at":29},3,410,84,"2026-04-04T14:39:58.906Z",[],{"attackSurface":32,"codeSignals":44,"taintFlows":51,"riskAssessment":52,"analyzedAt":60},{"hooks":33,"ajaxHandlers":40,"restRoutes":41,"shortcodes":42,"cronEvents":43,"entryPointCount":13,"unprotectedCount":13},[34],{"type":35,"name":36,"callback":37,"file":38,"line":39},"filter","show_admin_bar","hide_admin_bar_from_front_end","remove-adminbar-frontend.php",16,[],[],[],[],{"dangerousFunctions":45,"sqlUsage":46,"outputEscaping":48,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":50},[],{"prepared":13,"raw":13,"locations":47},[],{"escaped":13,"rawEcho":13,"locations":49},[],[],[],{"summary":53,"deductions":54},"The 'remove-admin-bar-menu' plugin v1.1 exhibits a strong security posture based on the provided static analysis. The absence of any identified dangerous functions, SQL queries executed without prepared statements, and fully escaped output are all positive indicators of good coding practices.  Furthermore, the plugin has no recorded vulnerability history, including no known CVEs, which suggests a history of secure development and maintenance.\n\nWhile the static analysis reveals a remarkably clean codebase with no apparent vulnerabilities such as unsanitized taint flows or unprotected entry points, a significant concern arises from the complete lack of capability checks and nonce checks. This means that even though the plugin doesn't expose direct entry points that are *currently* vulnerable in this specific version, it does not implement fundamental WordPress security mechanisms for potential future extensions or interactions.  The absence of these checks, combined with a zero-entry-point count in this static analysis, could be interpreted as either an extremely specialized and limited plugin or a missed opportunity to implement more robust, future-proof security for any potential interactions.\n\nIn conclusion, the plugin appears secure in its current version and functionality due to its clean code and lack of historical vulnerabilities. However, the complete omission of capability and nonce checks represents a weakness in its overall security architecture, making it less resilient against potential future threats or extensions that might introduce new functionalities.  It is advisable to consider adding these standard security checks to fortify the plugin further.",[55,58],{"reason":56,"points":57},"Missing capability checks",15,{"reason":59,"points":57},"Missing nonce checks","2026-03-16T22:32:19.415Z",{"wat":62,"direct":67},{"assetPaths":63,"generatorPatterns":64,"scriptPaths":65,"versionParams":66},[],[],[],[],{"cssClasses":68,"htmlComments":69,"htmlAttributes":70,"restEndpoints":71,"jsGlobals":72,"shortcodeOutput":73},[],[],[],[],[],[]]