[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fdG_xLEr0OAXRDX28IKojmx41inDnQizc6Q4W9OmISNg":3,"$fHAABG6XsaO7YU1aqVmNeE1X_wDMEFLjp0s4T-KbNrBA":113,"$fHS6OQWLFgwnPzAh2NnO-PQNMa4rvEdGtKMn7plXIQZ8":118},{"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":16,"requires_php":17,"tags":18,"homepage":22,"download_link":23,"security_score":24,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":26,"discovery_status":27,"vulnerabilities":28,"developer":29,"crawl_stats":25,"alternatives":35,"analysis":36,"fingerprints":83},"scheduled-stickiness","Scheduled stickiness","0.2","Magnus Karlsson","https:\u002F\u002Fprofiles.wordpress.org\u002Fmagnus_kson\u002F","\u003Cp>Sometimes you like a post to be sticky during a time interval in the future and not immediately when publishing. This plugin lets you specify when the stickiness should begin and end.\u003Cbr \u002F>\nOnce you have set the start and end dates, you don’t have to change the stickiness manually on a certain day. The plugin uses WordPress’s cron job to automaticallay set and unset stickiness.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When writing a post that needs scheduled stickiness, enter the dates for start and stop (inclusive) and update your post.\u003C\u002Fli>\n\u003Cli>Dates are entered using the date picker. Date format is according to your local settings.\u003C\u002Fli>\n\u003Cli>The stickiness is updated hourly so changes may need up to one hour to take effect.\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin makes a post sticky and unsticky on dates you specify in advance.",10,1884,0,"2025-03-02T09:27:00.000Z","6.7.5","2.7","",[19,4,20,21],"preset-sticky-post","scheduled-sticky-posts","set-sticky-post","http:\u002F\u002Fmagnus-karlsson.nu\u002Fprogram\u002Fscheduled-stickiness\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fscheduled-stickiness.zip",92,null,"2026-03-15T15:16:48.613Z","no_bundle",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":24,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"magnus_kson",1,30,88,"2026-05-20T02:36:52.459Z",[],{"attackSurface":37,"codeSignals":59,"taintFlows":72,"riskAssessment":73,"analyzedAt":82},{"hooks":38,"ajaxHandlers":53,"restRoutes":54,"shortcodes":55,"cronEvents":56,"entryPointCount":13,"unprotectedCount":13},[39,45,49],{"type":40,"name":41,"callback":42,"file":43,"line":44},"action","mknu_stickiness_event","mknu_stickiness_cron","scheduled-stickiness.php",20,{"type":40,"name":46,"callback":47,"file":43,"line":48},"add_meta_boxes","mknu_scheduled_stickiness_meta",52,{"type":40,"name":50,"callback":51,"file":43,"line":52},"save_post","mknu_scheduled_stickiness_save",97,[],[],[],[57],{"hook":41,"callback":41,"file":43,"line":58},24,{"dangerousFunctions":60,"sqlUsage":61,"outputEscaping":63,"fileOperations":13,"externalRequests":13,"nonceChecks":31,"capabilityChecks":13,"bundledLibraries":71},[],{"prepared":13,"raw":13,"locations":62},[],{"escaped":64,"rawEcho":64,"locations":65},2,[66,69],{"file":43,"line":67,"context":68},63,"raw output",{"file":43,"line":70,"context":68},67,[],[],{"summary":74,"deductions":75},"The plugin 'scheduled-stickiness' v0.2 exhibits a generally strong security posture based on the provided static analysis.  It demonstrates good practices by avoiding dangerous functions, using prepared statements for all SQL queries, and not performing file operations or external HTTP requests. The absence of any recorded vulnerabilities, including critical or high severity ones, further indicates a robust development approach.  However, there are areas for improvement. Notably, only 50% of the total output is properly escaped, presenting a potential for cross-site scripting (XSS) vulnerabilities if the unescaped outputs involve user-supplied data. Additionally, the lack of capability checks on any entry points is a concern, as it means any authenticated user, regardless of their role, could potentially interact with the plugin's functionality, which might not be intended.",[76,79],{"reason":77,"points":78},"50% of output not properly escaped",8,{"reason":80,"points":81},"No capability checks on entry points",5,"2026-03-16T23:47:50.885Z",{"wat":84,"direct":89},{"assetPaths":85,"generatorPatterns":86,"scriptPaths":87,"versionParams":88},[],[],[],[],{"cssClasses":90,"htmlComments":91,"htmlAttributes":104,"restEndpoints":110,"jsGlobals":111,"shortcodeOutput":112},[],[92,93,94,95,96,97,98,99,100,101,102,103],"\u003C!-- security -->","\u003C!-- Plugin activated -->","\u003C!-- Plugin deactivated -->","\u003C!-- cron -->","\u003C!-- Based on http:\u002F\u002Fthemefoundation.com\u002Fwordpress-meta-boxes-guide\u002F -->","\u003C!-- Thanks! -->","\u003C!--Adds a meta box to the post editing screen-->","\u003C!-- Outputs the content of the meta box -->","\u003C!-- Saves the custom meta input -->","\u003C!-- UI -->","\u003C!-- DO PSEUDO CRON JOB set\u002Funset STICKINESS -->","\u003C!-- debug output -->",[105,106,107,108,109],"name=\"mknu_sticky_date\"","id=\"mknu_sticky_date\"","name=\"mknu_unsticky_date\"","id=\"mknu_unsticky_date\"","name=\"mknu_nonce\"",[],[],[],{"error":114,"url":115,"statusCode":116,"statusMessage":117,"message":117},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fscheduled-stickiness\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":13,"versions":119},[]]