[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcBZHohzvCHHKM9lgGkOHRIX5N4iHSAiLaaqbZjMjcow":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":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":34,"analysis":35,"fingerprints":69},"prepublish-checks-by-kgaurav","PrePublish Checks by Kgaurav","1.0.3","kgaurav6791","https:\u002F\u002Fprofiles.wordpress.org\u002Fkgaurav6791\u002F","\u003Cp>[Classic-Editor-Only] A simple plugin to enforce variety of checks before publishing any new post.Define minimum and maximum title length.\u003Cbr \u002F>\nMake presence of a featured image compulsory.\u003Cbr \u002F>\nSpecify the minimum\u002Fmaximum height and width for your featured images.\u003Cbr \u002F>\nBonus feature check for post slug to be in english.\u003C\u002Fp>\n\u003Cp>Do you own a multi-author website,who keeps publishing posts with too small or too big title?\u003Cbr \u002F>\nOr do you yourself keep forgetting to add featured image before clicking on that “publish” button?\u003Cbr \u002F>\nMaybe people keep making posts on your website with featured images of such small  resolution that they start looking blurry on your landing page?\u003C\u002Fp>\n\u003Cp>This plugin will ensure that you can set custom conditions that need to be met before someone could publish a post.\u003Cbr \u002F>\nIf anyone clicks on the ‘publish’ button and one of the conditions are not met(For eg-if publish button is clicked without adding a featured image.) then the publish event will be intercepted,post will be saved as a draft instead and user will get an appropriate error showing what they did wrong and how they can correct their mistake before publishing.\u003C\u002Fp>\n","A plugin that checks to ensure variety of conditions are being met before any new post can be published.Eg-Minimum Title length,Featured Image,etc.",0,901,"","6.9.4","4.1","7.4",[18,19,20,21,22],"checks-before-posting","checks-before-publishing","prepublish-checklist","prepublish-checks","prepublish-posts","https:\u002F\u002Fgithub.com\u002Fkgaurav6791\u002FPrePublish-Checks-by-Kgaurav","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fprepublish-checks-by-kgaurav.1.0.3.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},1,30,94,"2026-04-04T02:47:56.532Z",[],{"attackSurface":36,"codeSignals":56,"taintFlows":64,"riskAssessment":65,"analyzedAt":68},{"hooks":37,"ajaxHandlers":52,"restRoutes":53,"shortcodes":54,"cronEvents":55,"entryPointCount":11,"unprotectedCount":11},[38,44,48],{"type":39,"name":40,"callback":41,"file":42,"line":43},"action","transition_post_status","prepublish_checks_by_kgaurav","prepublish-checks-by-kgaurav.php",42,{"type":39,"name":45,"callback":46,"file":42,"line":47},"admin_init","prepublish_by_kgaurav_options_register",107,{"type":39,"name":49,"callback":50,"file":42,"line":51},"admin_menu","prepublish_by_kgaurav_add_page",108,[],[],[],[],{"dangerousFunctions":57,"sqlUsage":58,"outputEscaping":60,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":11,"bundledLibraries":63},[],{"prepared":11,"raw":11,"locations":59},[],{"escaped":61,"rawEcho":11,"locations":62},18,[],[],[],{"summary":66,"deductions":67},"The prepublish-checks-by-kgaurav plugin version 1.0.3 exhibits a strong security posture based on the provided static analysis. There are no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in a zero attack surface and no unprotected entry points. The code demonstrates excellent security practices with zero dangerous functions, all SQL queries utilizing prepared statements, and 100% proper output escaping. Furthermore, there are no file operations, external HTTP requests, or indications of missing nonce or capability checks, which are common areas for vulnerabilities.\n\nThe taint analysis also reveals no concerning flows, indicating that data is being handled securely within the plugin's codebase. The vulnerability history is equally impressive, with zero known CVEs and no past vulnerabilities recorded. This lack of historical issues, combined with the robust static analysis, suggests that the developers have a good understanding of secure coding principles.\n\nOverall, the plugin appears to be very secure. The absence of any identified vulnerabilities or insecure coding practices in the static analysis and taint flows, along with a clean vulnerability history, points to a low-risk plugin. The primary strength lies in its minimal attack surface and adherence to fundamental security best practices. There are no discernible weaknesses based on the data provided.",[],"2026-03-17T05:41:54.367Z",{"wat":70,"direct":75},{"assetPaths":71,"generatorPatterns":72,"scriptPaths":73,"versionParams":74},[],[],[],[],{"cssClasses":76,"htmlComments":77,"htmlAttributes":78,"restEndpoints":79,"jsGlobals":80,"shortcodeOutput":81},[],[],[],[],[],[]]