[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fBPF_InNvJJ6SzwRn5q4xegYmIXBnnJFnGzA6JQR1t_k":3,"$f60OhmCM39lIuGW_zy1V2LoRi130hIQVjF-hpT8cutoI":119,"$f3iRbQHzY4L1Sb3iX_i8MakrCJx-NSwd5i4JNpo4i5BU":124},{"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":20,"download_link":21,"security_score":22,"vuln_count":23,"unpatched_count":23,"last_vuln_date":24,"fetched_at":25,"discovery_status":26,"vulnerabilities":27,"developer":28,"crawl_stats":24,"alternatives":36,"analysis":37,"fingerprints":84},"hc-privacy-compactor","Compact Privacy Pages","1.1.0","Marius L. J.","https:\u002F\u002Fprofiles.wordpress.org\u002Fclorith\u002F","\u003Cp>Privacy pages often include a lot of text, making it hard to keep track of what is going on, and what sections you really want to look up.\u003C\u002Fp>\n\u003Cp>This plugin will split up your Privacy Page into an accordion, revealing headings by default and allowing the reader to toggle which section they wish to look into at any given time.\u003C\u002Fp>\n\u003Cp>It will pick up any \u003Ccode>\u003Ch2>\u003C\u002Fcode> tags (or \u003Ccode>Heading 2\u003C\u002Fcode> in the WordPress editor), and puts any text following these in a collapsed state.\u003C\u002Fp>\n\u003Cp>Any text you wish to have always displayed, for example contact information, should be put early on in your page, before you start introducing any section headers.\u003C\u002Fp>\n\u003Cp>Prior to WordPress 4.9.6, a meta box is on the side of your pages where you can mark a Privacy Page, after 4.9.6 is released the plugin will automatically use the option chosen under \u003Ccode>Tools > Privacy\u003C\u002Fcode>.\u003C\u002Fp>\n","Privacy pages often include a lot of text, making it hard to keep track of what is going on, and what sections you really want to look up.",20,2098,100,1,"2020-08-01T11:04:00.000Z","5.5.18","4.6","",[],"https:\u002F\u002Fwww.hjelseth.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhc-privacy-compactor.1.1.0.zip",85,0,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"clorith",6,80410,88,30,86,"2026-05-20T01:13:24.309Z",[],{"attackSurface":38,"codeSignals":72,"taintFlows":79,"riskAssessment":80,"analyzedAt":83},{"hooks":39,"ajaxHandlers":68,"restRoutes":69,"shortcodes":70,"cronEvents":71,"entryPointCount":23,"unprotectedCount":23},[40,47,52,56,59,62,66],{"type":41,"name":42,"callback":43,"priority":44,"file":45,"line":46},"filter","the_content","format_privacy_page",10,"inc\\class-hc-privacy-compactor.php",21,{"type":48,"name":49,"callback":50,"file":45,"line":51},"action","wp_enqueue_scripts","enqueue_scripts",23,{"type":48,"name":53,"callback":53,"priority":44,"file":54,"line":55},"customize_register","inc\\class-hc-privacy-customizer.php",15,{"type":48,"name":57,"callback":50,"file":54,"line":58},"customize_controls_enqueue_scripts",17,{"type":48,"name":49,"callback":60,"priority":11,"file":54,"line":61},"enqueue_styles",19,{"type":48,"name":63,"callback":63,"file":64,"line":65},"add_meta_boxes","inc\\class-hc-privacy-meta.php",9,{"type":48,"name":67,"callback":67,"file":64,"line":44},"save_post",[],[],[],[],{"dangerousFunctions":73,"sqlUsage":74,"outputEscaping":76,"fileOperations":23,"externalRequests":23,"nonceChecks":14,"capabilityChecks":14,"bundledLibraries":78},[],{"prepared":23,"raw":23,"locations":75},[],{"escaped":23,"rawEcho":23,"locations":77},[],[],[],{"summary":81,"deductions":82},"The hc-privacy-compactor v1.1.0 plugin exhibits a very strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface. Furthermore, the code analysis shows no dangerous functions, all SQL queries are properly prepared, and all output is correctly escaped. The presence of a nonce check and a capability check indicates good practice for securing any potential (though currently non-existent) entry points.\n\nTaint analysis reveals no identified flows with unsanitized paths, further reinforcing the plugin's apparent security. The vulnerability history is also entirely clean, with no recorded CVEs of any severity. This suggests a well-developed and maintained plugin with a commitment to security.\n\nOverall, this plugin presents a minimal security risk. The lack of any identified vulnerabilities or exploitable code patterns, combined with robust security practices like prepared statements and output escaping, indicates a highly secure piece of software. The only potential area for future consideration would be if the plugin's functionality were to expand, requiring new entry points, which would then necessitate continued vigilance in applying the same security standards.",[],"2026-03-16T22:45:16.015Z",{"wat":85,"direct":96},{"assetPaths":86,"generatorPatterns":90,"scriptPaths":91,"versionParams":92},[87,88,89],"\u002Fwp-content\u002Fplugins\u002Fhc-privacy-compactor\u002Fassets\u002Fcss\u002Fstyle.css","\u002Fwp-content\u002Fplugins\u002Fhc-privacy-compactor\u002Fassets\u002Fjs\u002Fhc-privacy-compactor.js","\u002Fwp-content\u002Fplugins\u002Fhc-privacy-compactor\u002Fassets\u002Fjs\u002Fbackend.js",[],[88,89],[93,94,95],"hc-privacy-compactor\u002Fstyle.css?ver=","hc-privacy-compactor.js?ver=","backend.js?ver=",{"cssClasses":97,"htmlComments":101,"htmlAttributes":102,"restEndpoints":115,"jsGlobals":116,"shortcodeOutput":118},[98,99,100],"hc-accordion","hc-accordion-trigger","hc-accordion-panel",[],[103,104,105,106,107,108,109,110,111,112,113,114],"aria-expanded","aria-controls","id=\"hc-accordion-heading-","aria-level","role=\"heading\"","type=\"button\"","aria-labelledby","role=\"region\"","hidden=\"hidden\"","class=\"hc-accordion-trigger\"","class=\"hc-accordion-panel\"","class=\"hc-accordion\"",[],[117],"hc_privacy_compactor",[],{"error":120,"url":121,"statusCode":122,"statusMessage":123,"message":123},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fhc-privacy-compactor\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":125,"versions":126},2,[127,133],{"version":6,"download_url":21,"svn_tag_url":128,"released_at":24,"has_diff":129,"diff_files_changed":130,"diff_lines":24,"trac_diff_url":131,"vulnerabilities":132,"is_current":120},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhc-privacy-compactor\u002Ftags\u002F1.1.0\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhc-privacy-compactor%2Ftags%2F1.0.0&new_path=%2Fhc-privacy-compactor%2Ftags%2F1.1.0",[],{"version":134,"download_url":135,"svn_tag_url":136,"released_at":24,"has_diff":129,"diff_files_changed":137,"diff_lines":24,"trac_diff_url":24,"vulnerabilities":138,"is_current":129},"1.0.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhc-privacy-compactor.1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhc-privacy-compactor\u002Ftags\u002F1.0.0\u002F",[],[]]