[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-ZYz3fp6xkkEPiUPJkuCwt0grYmT_L61K5pSbytrUwc":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":21,"download_link":22,"security_score":23,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":33,"analysis":34,"fingerprints":93},"wpost-still-fresh","WPost Still Fresh","1.1","Kapsule Corp","https:\u002F\u002Fprofiles.wordpress.org\u002Fgothamdev\u002F","\u003Cp>🇫🇷 FRENCH 🇫🇷 : Petit plugin ultra léger pour garder vos pages et posts toujours à jour pour notre ami GG. Paramétrez une tache CRON mensuelle\u002Fhebdomadaire (ou à la récurrence que vous voulez…) et paramétrez le nombre de jour précédents max que vous souhaitez. Le plugin mettra comme date de dernière modification de votre post\u002Fpage, une date aléatoire entre la date d’execution de votre tache CRON et le nombre de jour précédents max que vous avez paramétré.\u003C\u002Fp>\n\u003Cp>🇺🇸 ENGLISH 🇺🇸 : Ultra-light plugin to keep your pages and posts always up to date for our friend GG. Set up a monthly\u002Fweekly CRON task (or at the recurrence you want…) and set the maximum number of previous days that you want. The plugin will set as the last modification date of your post\u002Fpage, a random date between the execution date of your CRON task and the maximum number of previous days that you have configured\u003C\u002Fp>\n","Petit plugin ultra léger pour garder vos pages et posts toujours à jour pour notre ami GG.",0,475,"2025-12-05T10:28:00.000Z","6.9.4","6.0","7.4.0",[18,19,20],"randomize-date","shuffle-date","still-fresh-date","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwpost-still-fresh.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":23,"avg_patch_time_days":31,"trust_score":23,"computed_at":32},"gothamdev",7,200,2,"2026-04-04T18:42:23.497Z",[],{"attackSurface":35,"codeSignals":76,"taintFlows":86,"riskAssessment":87,"analyzedAt":92},{"hooks":36,"ajaxHandlers":65,"restRoutes":72,"shortcodes":73,"cronEvents":74,"entryPointCount":75,"unprotectedCount":11},[37,43,47,51,57,61],{"type":38,"name":39,"callback":40,"file":41,"line":42},"action","admin_menu","chron0striggeuss_settings_page","core.php",67,{"type":38,"name":44,"callback":45,"file":41,"line":46},"admin_enqueue_scripts","chron0striggeuss_enqueue_admin_scripts",82,{"type":38,"name":48,"callback":49,"file":41,"line":50},"admin_init","chron0striggeuss_register_settings",167,{"type":52,"name":53,"callback":54,"priority":55,"file":41,"line":56},"filter","wp_insert_post_data","closure",10,214,{"type":52,"name":58,"callback":59,"file":41,"line":60},"cron_schedules","chron0striggeuss_add_monthly_cron_schedule",257,{"type":38,"name":62,"callback":63,"file":41,"line":64},"init","chron0striggeuss_setup_monthly_cron_event",326,[66],{"action":67,"nopriv":68,"callback":69,"hasNonce":70,"hasCapCheck":68,"file":41,"line":71},"randomize_posts",false,"chron0striggeuss_randomize_posts_ajax",true,19,[],[],[],1,{"dangerousFunctions":77,"sqlUsage":78,"outputEscaping":80,"fileOperations":11,"externalRequests":11,"nonceChecks":75,"capabilityChecks":75,"bundledLibraries":85},[],{"prepared":11,"raw":11,"locations":79},[],{"escaped":29,"rawEcho":75,"locations":81},[82],{"file":41,"line":83,"context":84},29,"raw output",[],[],{"summary":88,"deductions":89},"The \"wpost-still-fresh\" v1.1 plugin exhibits a strong security posture based on the provided static analysis and vulnerability history.  The code appears to follow good security practices, with all identified entry points (AJAX handlers) being protected by nonce and capability checks.  Furthermore, there are no concerning code signals such as dangerous functions, raw SQL queries, or file operations. The taint analysis showing zero flows is also a positive indicator. The absence of any known historical vulnerabilities reinforces this favorable assessment.\n\nWhile the overall security is good, the analysis does not indicate any specific risks or vulnerabilities. The plugin appears well-secured against common attack vectors. The strengths lie in its limited attack surface and robust implementation of security checks. The only minor observation is that 12% of outputs are not properly escaped, which, while not a critical issue given the context, could be a point of improvement.  In conclusion, \"wpost-still-fresh\" v1.1 is a secure plugin with no immediate security concerns requiring urgent attention.",[90],{"reason":91,"points":31},"Outputs not properly escaped","2026-03-17T06:55:58.549Z",{"wat":94,"direct":100},{"assetPaths":95,"generatorPatterns":97,"scriptPaths":98,"versionParams":99},[96],"\u002Fwp-content\u002Fplugins\u002Fwpost-still-fresh\u002Fjs\u002Fchronocore.js",[],[96],[],{"cssClasses":101,"htmlComments":105,"htmlAttributes":106,"restEndpoints":120,"jsGlobals":122,"shortcodeOutput":124},[102,103,104],"posts-config","pages-config","randomize-posts-form",[],[107,108,109,110,111,112,113,114,115,116,117,118,119],"id=\"chron0striggeuss_active\"","name=\"chron0striggeuss_active\"","id=\"chron0striggeuss_posts_interval\"","name=\"chron0striggeuss_posts_interval\"","id=\"chron0striggeuss_posts_backdate\"","name=\"chron0striggeuss_posts_backdate\"","id=\"chron0striggeuss_pages_interval\"","name=\"chron0striggeuss_pages_interval\"","id=\"chron0striggeuss_pages_backdate\"","name=\"chron0striggeuss_pages_backdate\"","id=\"randomize_posts_nonce\"","name=\"nonce\"","id=\"message-container\"",[121],"\u002Fwp-json\u002Fwp\u002Fv2\u002Fposts",[123],"chron0striggeussParams",[]]