[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fws6ub5wOFTaeiZ1fVSNlGsHKl5hIO6zg42ccZC5hLAI":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":35,"analysis":83,"fingerprints":171},"content-freshness","Content Freshness","1.1","Luis Reginaldo Medilo","https:\u002F\u002Fprofiles.wordpress.org\u002Floythegreat\u002F","\u003Cp>Updating your articles is important to keep them fresh and to help maintain their rankings in Google and other search engines. But if you have a large site with hundreds of posts, it may be hard to keep track of all your articles and when they were last updated.\u003C\u002Fp>\n\u003Cp>With Content Freshness, you can easily see which articles are in need of an update. You will see the dates when they were last modified, so that you can update them accordingly. You can select the timeframe for content updating – whether 3 months, 6 months, or 1 year (the default is 6 months).\u003C\u002Fp>\n\u003Cp>If your website is already added to Google Search Console, you can choose to activate the GSC Performance option. Use it to check your individual post’s search results performance in Google Search Console before you update your articles.\u003C\u002Fp>\n","Keep your content fresh and up to date! Content Freshness plugin shows a list of posts that have not been updated for a set period of time.",0,1728,"2024-11-20T07:49:00.000Z","6.7.5","4.9","",[18,19,20],"modify-posts","update-articles","update-posts","https:\u002F\u002Ftechpilipinas.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-freshness.1.1.zip",92,null,"2026-03-15T15:16:48.613Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":31,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"loythegreat",2,600,96,30,91,"2026-04-05T18:45:03.174Z",[36,62],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":57,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":11,"last_vuln_date":61,"fetched_at":25},"post-expirator","Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories","4.9.4","PublishPress","https:\u002F\u002Fprofiles.wordpress.org\u002Fpublishpress\u002F","\u003Cp>The PublishPress Future plugin allows you to schedule changes to posts, pages and other content types. With this plugin you can create automatic actions to unpublish, delete, trash, move a post to a new status and more. With the Pro version you can update your content using custom workflows with multiple steps and schedules.\u003C\u002Fp>\n\u003Cp>Here’s an overview of what you can do with PublishPress Future:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Select future action dates in the right sidebar when you are editing a post. This makes it very easy to schedule changes to your content.\u003C\u002Fli>\n\u003Cli>Receive email notifications when Future makes changes to your content.\u003C\u002Fli>\n\u003Cli>Build Action Workflows that allow you to update your content using custom workflows with multiple steps and schedules (available in the Pro version).\u003C\u002Fli>\n\u003Cli>Control post changes via integrations with Advanced Custom Fields and other plugins (available in the Pro version).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>PublishPress Future Pro\u003C\u002Fh3>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Upgrade to PublishPress Future Pro\u003C\u002Fstrong>\u003Cbr \u002F>\n  This plugin is the free version of the PublishPress Future plugin. The Pro version comes with all the features you need to schedule changes to your WordPress content. \u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Ffuture\" title=\"PublishPress Future Pro\" rel=\"nofollow ugc\">Click here to purchase the best plugin for scheduling WordPress content updates!\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>Options for Future Actions on Posts\u003C\u002Fh3>\n\u003Cp>With PublishPress Future, you can configure actions that will happen automatically to your content. Here are the changes you can choose for your posts:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Change the status to “Draft”.\u003C\u002Fli>\n\u003Cli>Delete the post.\u003C\u002Fli>\n\u003Cli>Send the post to the Trash.\u003C\u002Fli>\n\u003Cli>Change the status to “Private”.\u003C\u002Fli>\n\u003Cli>Enable the “Stick to the top of the blog” option.\u003C\u002Fli>\n\u003Cli>Disable the “Stick to the top of the blog” option.\u003C\u002Fli>\n\u003Cli>Remove all existing categories, and add new categories.\u003C\u002Fli>\n\u003Cli>Keep all existing categories, and add new categories.\u003C\u002Fli>\n\u003Cli>Keep all existing categories, except for those specified in this change.\u003C\u002Fli>\n\u003Cli>Move the post to a custom status (available in the Pro version)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Fways-to-expire-posts\u002F\" rel=\"nofollow ugc\">Click here for details on scheduling post changes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Custom Workflows to Schedule Content Changes\u003C\u002Fh3>\n\u003Cp>With PublishPress Future Pro, you can build Action Workflows. These allow you to update your content using custom workflows with multiple steps and schedules. Here are some examples of what you can do with Action Workflows:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Email the site admin when a post is updated.\u003C\u002Fli>\n\u003Cli>Change the post status to “Trash” a week after it was published.\u003C\u002Fli>\n\u003Cli>15 days after the post is published, move the post to the “Draft” status and add a new category.\u003C\u002Fli>\n\u003Cli>1 year after a post is published, send an email to the author asking them to check the content.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Fworkflows\u002F\" rel=\"nofollow ugc\">Click here for details on workflows for changes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Display the Action Date in Your Content\u003C\u002Fh3>\n\u003Cp>PublishPress Future allows you to place automatically show the expiry or action date inside your articles. The date will be added at the bottom of your post.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Ffooter-display\u002F\" rel=\"nofollow ugc\">Click here to see the Footer Display options\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>You can use shortcodes to show the expiration date inside your posts. You can customize the shortcode output with several formatting options.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Fshortcodes-to-show-expiration-date\u002F\" rel=\"nofollow ugc\">Click here to see the shortcode options\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Choose Actions Defaults for Post Types\u003C\u002Fh3>\n\u003Cp>PublishPress Future can support any post type in WordPress. Go to Settings > PublishPress Future > Defaults and you can choose default actions for each post type.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Fdefaults-for-post-types\u002F\" rel=\"nofollow ugc\">Click here to see the default options\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>PublishPress Future Email Notifications\u003C\u002Fh3>\n\u003Cp>The PublishPress Future plugin can send you email notifications when your content is changed. You can control the emails by going to Settings > PublishPress Future > General Settings.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Femail-notifications\u002F\" rel=\"nofollow ugc\">Click here to see the notification options\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Integrations With Other Plugins\u003C\u002Fh3>\n\u003Cp>In PublishPress Future Pro it is possible to schedule changes to your posts based on metadata. This makes it possible to integrate PublishPress Future with other plugins.  For example, you can create a date field in the Advanced Custom Fields plugin and use that to control the date for Future Actions.\u003C\u002Fp>\n\u003Cp>When you are using an integration, there are five types of data that you can update in PublishPress Future:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Action Status: This field specifies if the action should be enabled.\u003C\u002Fli>\n\u003Cli>Action Date: This field stores the scheduled date for the action.\u003C\u002Fli>\n\u003Cli>Action Type: This field stores the type of action that will be executed.\u003C\u002Fli>\n\u003Cli>Taxonomy Name: The taxonomy name for being used when selecting terms.\u003C\u002Fli>\n\u003Cli>Taxonomy Terms: A list of term’s IDs for being used by the action.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Fmetadata-scheduling\u002F\" rel=\"nofollow ugc\">Click here to see how to integrate Future with other plugins\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Import the Future Actions\u003C\u002Fh3>\n\u003Cp>PublishPress Future Pro supports imports from external data sources. You can import posts and automatically create Future Actions associated with those posts.\u003C\u002Fp>\n\u003Cp>The best approach is to use the Metadata Scheduling feature. If you’re using a plugin such as WP All Import, you can match up the import tables with the fields you have selected in the Metadata Scheduling feature.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Fimports-and-metadata-scheduling\u002F\" rel=\"nofollow ugc\">Click here to see how to import data for Future Actions\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Details on How Post Changes Works\u003C\u002Fh3>\n\u003Cp>For each expiration event, a custom cron job is scheduled. This can help reduce server overhead for busy sites. This plugin REQUIRES that WP-CRON is setup and functional on your webhost.  Some hosts do not support this, so please check and confirm if you run into issues using the plugin.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Fscheduling-cron-jobs\u002F\" rel=\"nofollow ugc\">Click here to see the technical details for this plugin\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Logs for All Your Post Changes\u003C\u002Fh3>\n\u003Cp>PublishPress Future Pro allows you to keep a detailed record of all the post updates. PublishPress Future records several key data points for all actions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The post that the action was performed on.\u003C\u002Fli>\n\u003Cli>Details of the post update.\u003C\u002Fli>\n\u003Cli>When the change was made to the post.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fknowledge-base\u002Faction-logs\u002F\" rel=\"nofollow ugc\">Click here to see more about the logs feature\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Join PublishPress and get the Pro plugins\u003C\u002Fh3>\n\u003Cp>The Pro versions of the PublishPress plugins are well worth your investment. The Pro versions have extra features and faster support. \u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fpricing\u002F\" rel=\"nofollow ugc\">Click here to join PublishPress\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Join PublishPress and you’ll get access to these nine Pro plugins:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fauthors\" rel=\"nofollow ugc\">PublishPress Authors Pro\u003C\u002Fa> allows you to add multiple authors and guest authors to WordPress posts.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fblocks\" rel=\"nofollow ugc\">PublishPress Blocks Pro\u003C\u002Fa> has everything you need to build professional websites with the WordPress block editor.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fcapabilities\" rel=\"nofollow ugc\">PublishPress Capabilities Pro\u003C\u002Fa> is the plugin to manage your WordPress user roles, permissions, and capabilities.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fchecklists\" rel=\"nofollow ugc\">PublishPress Checklists Pro\u003C\u002Fa> enables you to define tasks that must be completed before content is published.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Ffuture\" rel=\"nofollow ugc\">PublishPress Future Pro\u003C\u002Fa>  is the plugin for scheduling changes to your posts.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fpermissions\" rel=\"nofollow ugc\">PublishPress Permissions Pro\u003C\u002Fa>  is the plugin for advanced WordPress permissions.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fpublishpress\" rel=\"nofollow ugc\">PublishPress Planner Pro\u003C\u002Fa> is the plugin for managing and scheduling WordPress content.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Frevisions\" rel=\"nofollow ugc\">PublishPress Revisions Pro\u003C\u002Fa> allows you to update your published pages with teamwork and precision.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpublishpress.com\u002Fseries\" rel=\"nofollow ugc\">PublishPress Series Pro\u003C\u002Fa> enables you to group content together into a series\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Together, these plugins are a suite of powerful publishing tools for WordPress. If you need to create a professional workflow in WordPress, with moderation, revisions, permissions and more… then you should try PublishPress.\u003C\u002Fp>\n\u003Ch4>Bug Reports\u003C\u002Fh4>\n\u003Cp>Bug reports for PublishPress Future are welcomed in our \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpublishpress\u002Fpublishpress-future\" rel=\"nofollow ugc\">repository on GitHub\u003C\u002Fa>. Please note that GitHub is not a support forum, and that issues that are not properly qualified as bugs will be closed.\u003C\u002Fp>\n","PublishPress Future can make scheduled changes to your content. You can unpublish posts, move posts to a new status, update the categories, and more.",100000,3997676,90,172,"2025-12-22T14:19:00.000Z","6.9.4","6.7","7.4",[53,54,55,20,56],"automatic-changes","schedule-changes","unpublish-posts","workflows","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fpost-expirator\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpost-expirator.4.9.4.zip",95,5,"2026-01-11 00:00:00",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":46,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":16,"tags":76,"homepage":80,"download_link":81,"security_score":82,"vuln_count":11,"unpatched_count":11,"last_vuln_date":24,"fetched_at":25},"gravity-forms-post-updates","Gravity Forms: Post Updates","1.2.23","Jupitercow","https:\u002F\u002Fprofiles.wordpress.org\u002Fjcow\u002F","\u003Cp>\u003Cstrong>Requires PHP 5.3 or greater\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Allows you to use Gravity Forms to update any post on the front end. If you use the “Gravity Forms + Custom Post Types”, you can even update custom post types and use custom taxonomies.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Supports custom field file uploading and deletion with thumbnails or mime type icons for existing items.\u003C\u002Fli>\n\u003Cli>Fixed a bugs on multi selects and checkboxes.\u003C\u002Fli>\n\u003Cli>Fixed bug on Categories.\u003C\u002Fli>\n\u003Cli>Completely removed the ability to delete posts.\u003C\u002Fli>\n\u003Cli>There are some filters to customize things now.\u003C\u002Fli>\n\u003Cli>Adds non-query-var template method to setup a form.\u003C\u002Fli>\n\u003Cli>Adds a really basic shortcode to setup a form (UPDATE: This is still supported, but it is better to use the addition, below, to the gravityform shortcode).\u003C\u002Fli>\n\u003Cli>Adds an additional attribute to the gravityform shortcode: “update”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>SHORTCODE\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>[gravityform id=\"1\" update] \u002F\u002F Loads current post for editing\n\n[gravityform id=\"1\" update=\"34\"] \u002F\u002F Loads post where ID=34 for editing\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>We worked with Rocketgenius, makers of Gravity Forms, to get a small upgrade added that allows us to extend their shortcode, so now you can simply add the “update” attribute to the normal “gravityform” shortcode. If you only add “update”, it will load the current post in to update. If you add an integer to the update attribute, it will use that to load a post by its ID.\u003C\u002Fp>\n\u003Ch4>URL QUERY VARIABLE\u003C\u002Fh4>\n\u003Col>\n\u003Cli>At the heart, it is pretty similar to how it was, but now there is a nonce required to activate it.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>So you should use the action to create your links.\u003C\u002Fp>\n\u003Cp>do_action(‘gform_update_post\u002Fedit_link’);\u003C\u002Fp>\n\u003Cp>do_action(‘gform_update_post\u002Fedit_link’, array(\u003Cbr \u002F>\n    ‘post_id’ => $post->ID,\u003Cbr \u002F>\n    ‘url’     => home_url(‘\u002Fedit_post\u002F’),\u003Cbr \u002F>\n) );\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Arguments (query string or array)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>post_id\u003C\u002Fcode> (int) (optional) The id of the post you want to edit. Default: global $post->ID\u003C\u002Fli>\n\u003Cli>\u003Ccode>url\u003C\u002Fcode> (string|int) (optional) Either the full url of the page where your edit form resides, or an id for the page\u002Fpost where the edit form resides. Default: get_permalink()\u003C\u002Fli>\n\u003Cli>\u003Ccode>text\u003C\u002Fcode> (string) (optional) The link text. Default: “Edit Post”\u003C\u002Fli>\n\u003Cli>\u003Ccode>title\u003C\u002Fcode> (string) (optional) The title attribute of the anchor tag. Default: (text) parameter\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Get just the URL\u003C\u002Fh3>\n\u003Cp>This will return a basic edit url\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters('gform_update_post\u002Fedit_url', '');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Specify post to edit (post_id) and post that holds the edit form (url)\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters('gform_update_post\u002Fedit_url', 1, home_url('\u002Fedit_post\u002F'));\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Shortcode to show the edit link\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>[gform_update_post_edit_link]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Specify post to edit (post_id) and post that holds the edit form (url)\u003Cbr \u002F>\n    [gform_update_post_edit_link post_id=1 url=6]\u003C\u002Fp>\n\u003Ch4>IN TEMPLATE\u003C\u002Fh4>\n\u003Cp>You can use the action to force a form show a specific post:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>do_action('gform_update_post\u002Fsetup_form');\n\ndo_action('gform_update_post\u002Fsetup_form', $post->ID);\n\ndo_action('gform_update_post\u002Fsetup_form', array('post_id' => $post->ID, 'form_id' => $form_id));\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Parameters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>post_id\u003C\u002Fcode> (int|array) (optional) The id of the post you want to edit or an array with post id and\u002For form id. This allows you to specify the form id, so that update functionality does not get applied to other forms on the page. Default: global $post->ID\u003C\u002Fli>\n\u003C\u002Ful>\n","Allows you to use Gravity Forms to update any post on the front end.",300,14969,13,"2015-07-02T20:53:00.000Z","4.2.39","3.6.1",[77,78,79,20],"front-end","frontend","gravity-forms","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fgravity-forms-post-updates\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgravity-forms-post-updates.1.2.23.zip",85,{"attackSurface":84,"codeSignals":104,"taintFlows":159,"riskAssessment":160,"analyzedAt":170},{"hooks":85,"ajaxHandlers":100,"restRoutes":101,"shortcodes":102,"cronEvents":103,"entryPointCount":11,"unprotectedCount":11},[86,92,96],{"type":87,"name":88,"callback":89,"file":90,"line":91},"action","admin_menu","content_freshness_add_admin_menu","content-freshness.php",34,{"type":87,"name":93,"callback":94,"file":90,"line":95},"admin_init","content_freshness_settings_init",35,{"type":87,"name":97,"callback":98,"file":90,"line":99},"admin_enqueue_scripts","content_freshness_enqueue_styles",36,[],[],[],[],{"dangerousFunctions":105,"sqlUsage":106,"outputEscaping":108,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":11,"bundledLibraries":158},[],{"prepared":11,"raw":11,"locations":107},[],{"escaped":109,"rawEcho":110,"locations":111},46,23,[112,114,116,118,120,122,124,126,128,130,132,134,136,138,140,142,144,146,148,150,152,154,156],{"file":90,"line":23,"context":113},"raw output",{"file":90,"line":115,"context":113},99,{"file":90,"line":117,"context":113},147,{"file":90,"line":119,"context":113},148,{"file":90,"line":121,"context":113},152,{"file":90,"line":123,"context":113},153,{"file":90,"line":125,"context":113},154,{"file":90,"line":127,"context":113},156,{"file":90,"line":129,"context":113},174,{"file":90,"line":131,"context":113},176,{"file":90,"line":133,"context":113},185,{"file":90,"line":135,"context":113},194,{"file":90,"line":137,"context":113},239,{"file":90,"line":139,"context":113},240,{"file":90,"line":141,"context":113},244,{"file":90,"line":143,"context":113},245,{"file":90,"line":145,"context":113},246,{"file":90,"line":147,"context":113},248,{"file":90,"line":149,"context":113},266,{"file":90,"line":151,"context":113},268,{"file":90,"line":153,"context":113},277,{"file":90,"line":155,"context":113},286,{"file":90,"line":157,"context":113},315,[],[],{"summary":161,"deductions":162},"The \"content-freshness\" v1.1 plugin exhibits a generally positive security posture based on the provided static analysis.  The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the plugin's attack surface.  Furthermore, the code analysis indicates no dangerous functions, no raw SQL queries, and no external HTTP requests, which are all strong security indicators.  The vulnerability history is also clean, with no known CVEs, suggesting a history of secure development or diligent patching.\n\nHowever, there are some areas for concern. The output escaping is only 67% properly escaped, meaning a notable portion of outputs might be vulnerable to cross-site scripting (XSS) attacks if user-supplied data is involved.  Additionally, the complete lack of nonce checks and capability checks on any potential entry points (though none were identified) is a significant omission. While the current attack surface is zero, any future additions or changes to the plugin could introduce vulnerabilities if these fundamental security checks are not implemented. The taint analysis showing zero flows, while good, is based on zero flows analyzed, which could be a limitation of the analysis itself or an indication of a very simple plugin.\n\nIn conclusion, the plugin is currently in a good state, primarily due to its minimal attack surface and lack of known vulnerabilities. The primary weaknesses lie in the incomplete output escaping and the absence of essential security checks like nonces and capability checks, which could become critical issues if the plugin's functionality expands. Addressing the output escaping and planning for robust security checks in future development are recommended.",[163,166,168],{"reason":164,"points":165},"Low output escaping coverage",6,{"reason":167,"points":60},"No nonce checks",{"reason":169,"points":60},"No capability checks","2026-03-17T06:14:44.731Z",{"wat":172,"direct":177},{"assetPaths":173,"generatorPatterns":174,"scriptPaths":175,"versionParams":176},[],[],[],[],{"cssClasses":178,"htmlComments":180,"htmlAttributes":181,"restEndpoints":182,"jsGlobals":183,"shortcodeOutput":184},[179],"up-posts-table",[],[],[],[],[]]