[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2nkRaqPtFoX-B2Ur9dIcIY8oUS1j70VwW76MM5wY66E":3},{"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":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":39,"analysis":131,"fingerprints":192},"gf-datetime-field-add-on","Date Time Field Add-On for Gravity Form","1.3.6","Awais","https:\u002F\u002Fprofiles.wordpress.org\u002Fawais300\u002F","\u003Cp>A date-time add-on for Gravity Forms with custom date time format:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>This plugin will add new type of field under \u003Ccode>Advanced Fields\u003C\u002Fcode> as \u003Ccode>Date-Time\u003C\u002Fcode>. \u003C\u002Fli>\n\u003Cli>Simply drag \u003Ccode>Date-Time\u003C\u002Fcode> field into the form.\u003C\u002Fli>\n\u003Cli>You can also add custom date time format under \u003Ccode>General\u003C\u002Fcode> tab. \u003C\u002Fli>\n\u003Cli>The date time format pattern must follow moment.js tokens. Click \u003Ca href=\"https:\u002F\u002Fmomentjs.com\u002Fdocs\u002F#\u002Fparsing\u002Fstring-format\u002F\" rel=\"nofollow ugc\">here\u003C\u002Fa> to view moment.js date and time tokens.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Translations included\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Français (French)\u003C\u002Fli>\n\u003C\u002Ful>\n","A date-time add-on for Gravity Forms with custom date time format.",1000,12033,90,2,"2025-12-14T22:36:00.000Z","6.9.4","4.0","7.4",[20,21,22,23,24],"addon","date","datetime","gravity-form","time","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgf-datetime-field-add-on.1.3.6.zip",100,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":27,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},"awais300",3,1080,30,94,"2026-04-04T05:32:30.327Z",[40,58,76,97,115],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":28,"num_ratings":28,"last_updated":50,"tested_up_to":51,"requires_at_least":17,"requires_php":25,"tags":52,"homepage":55,"download_link":56,"security_score":57,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"datetime-fields-for-gravityforms","Date\u002FTime Fields for Gravity Forms","1.0","Gravity Extra","https:\u002F\u002Fprofiles.wordpress.org\u002Fefetech\u002F","\u003Cp>Create a new custom field for “GravityForms” plugin called “Date\u002FTime” field:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Add a new field called “Date\u002FTime” field to GravityForms fields.\u003C\u002Fli>\n\u003Cli>User can drag that field into the form and use it.\u003C\u002Fli>\n\u003Cli>The field will allow user to select both Date and Time for one field.\u003C\u002Fli>\n\u003C\u002Ful>\n","Create a new custom field for \"GravityForms\" plugin called \"Date\u002FTime\" field.",200,5129,"2019-08-03T14:22:00.000Z","5.2.24",[21,22,53,54,24],"forms","gravity-forms","http:\u002F\u002Fwww.gravityforms.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdatetime-fields-for-gravityforms.1.1.zip",85,{"slug":59,"name":60,"version":61,"author":62,"author_profile":63,"description":64,"short_description":65,"active_installs":36,"downloaded":66,"rating":27,"num_ratings":67,"last_updated":68,"tested_up_to":69,"requires_at_least":25,"requires_php":25,"tags":70,"homepage":74,"download_link":75,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"advanced-date-time-field","Advanced Date Time Field For Contact Form 7, Gravity Forms, WPForms","1.0.1","PluginsCafe","https:\u002F\u002Fprofiles.wordpress.org\u002Fpluginscafe\u002F","\u003Cp>This plugin is a lightweight yet powerful date and time picker designed for popular form builder plugins.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>This plugin will add new type of field under \u003Ccode>Standrad Fields\u003C\u002Fcode> as \u003Ccode>Date Time\u003C\u002Fcode>. \u003C\u002Fli>\n\u003Cli>Simply drag \u003Ccode>Date-Time\u003C\u002Fcode> field into the form.\u003C\u002Fli>\n\u003Cli>You can also add custom date time format under \u003Ccode>Date Time Field\u003C\u002Fcode> tab.\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin is a lightweight yet powerful date and time picker designed for popular form builder plugins.",821,1,"2025-10-28T04:43:00.000Z","6.8.5",[71,72,22,54,73],"contact-form-7","date-picker","wpforms","https:\u002F\u002Fpluginscafe.com\u002Fplugin\u002Fadvanced-date-time-field\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadvanced-date-time-field.1.0.1.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":86,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":90,"requires_php":25,"tags":91,"homepage":95,"download_link":96,"security_score":57,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"blog-time","Blog Time","4.0.1","Scott Reilly","https:\u002F\u002Fprofiles.wordpress.org\u002Fcoffee2code\u002F","\u003Cp>This plugin adds a dynamic, functional clock to the admin bar (at top of all admin pages) to show the server time for the blog. The clock automatically updates as time passes, as you would expect of a digital clock.\u003C\u002Fp>\n\u003Cp>This plugin also supports a static mode which puts a timestamp string at the top of all admin pages instead of the dynamic clock. This static admin time widget can be clicked to update the time in-place (without a page reload) to show the new current server time.\u003C\u002Fp>\n\u003Cp>Also provided is a “Blog Time” widget providing the same functionality as the admin widget, but for your sidebars. You may also utilize the plugin’s functionality directly within a theme template via use of the template tag \u003Ccode>c2c_blog_time()\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>NOTE: For the front-end widget, if the “Use dynamic clock?” configuration option is unchecked, this plugin generates a timestamp and NOT a clock. The time being displayed is the time of the page load, or if clicked, the time when the widget last retrieved the time. It won’t actively increment time on the display. By default the widget displays a dynamic clock that does increment time.\u003C\u002Fp>\n\u003Cp>This is most useful to see the server\u002Fblog time to judge when a time sensitive post, comment, or action would be dated by the blog (i.e. such as monitoring for when to close comments on a contest post, or just accounting for the server being hosted in a different timezone). Or, when used statically as a timestamp and not a clock, it can indicate\u002Fpreserve when the page was loaded.\u003C\u002Fp>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fmomentjs.com\u002F\" rel=\"nofollow ugc\">Moment.js\u003C\u002Fa> for the JavaScript date handling library.\u003C\u002Fp>\n\u003Cp>Links: \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Fblog-time\u002F\" rel=\"nofollow ugc\">Plugin Homepage\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fblog-time\u002F\" rel=\"ugc\">Plugin Directory Page\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcoffee2code\u002Fblog-time\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\" rel=\"nofollow ugc\">Author Homepage\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Template Tags\u003C\u002Fh3>\n\u003Cp>The plugin provides one template tag for use in your theme templates, functions.php, or plugins.\u003C\u002Fp>\n\u003Ch4>Functions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>\u003C?php function c2c_blog_time( $time_format = '', $echo = true ) ?>\u003C\u002Fcode>\u003Cbr \u002F>\nReturns and\u002For displays the formatted time for the site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Arguments\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Ccode>$time_format\u003C\u002Fcode> (string)\u003Cbr \u002F>\nOptional. PHP-style time format string. See https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fdatetime.format.php for more info. Default is ” (which, unless otherwise modified, uses the default time forat: ‘g:i A’).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$echo\u003C\u002Fcode> (bool)\u003Cbr \u002F>\nOptional. Echo the template info? Default is true.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Ccode>\u003C?php \u002F\u002F Output the site's current time.\u003Cbr \u002F>\nc2c_blog_time();\u003Cbr \u002F>\n?>\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>\u003C?php \u002F\u002F Retrieve the value for use in code, so don't display\u002Fecho it.\u003Cbr \u002F>\n$site_date = c2c_blog_time( 'M d, Y', false );\u003Cbr \u002F>\n?>\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Hooks\u003C\u002Fh3>\n\u003Cp>The plugin exposes four filters for hooking. Code using these filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain). Less ideally, you could put them in your active theme’s functions.php file.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>c2c_blog_time (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>'c2c_blog_time'\u003C\u002Fcode> hook allows you to use an alternative approach to safely invoke \u003Ccode>c2c_blog_time()\u003C\u002Fcode> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>same as for \u003Ccode>c2c_blog_time()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cp>Instead of:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php c2c_blog_time(); ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Do:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php echo apply_filters( 'c2c_blog_time', '' ); ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>c2c_blog_time_format (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>'c2c_blog_time_format'\u003C\u002Fcode> hook allows you to customize the default format for the blog time. By default this is ‘g:i A’ (though this may be different if modified by localization).\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$format (string): The default format for the blog time.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Change the default blog time string\n *\n * @param string $format The default time format.\n * @return string\n *\u002F\nfunction change_blog_time_format( $format ) {\n    return 'b, g:i A';\n}\nadd_filter( 'c2c_blog_time_format', 'change_blog_time_format' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>c2c_blog_time_toolbar_widget_for_user (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>c2c_blog_time_toolbar_widget_for_user\u003C\u002Fcode> hook allows you to control if the admin toolbar clock widget should be shown, on a per-user basis. By default the admin toolbar clock is shown to everyone who can see the admin toolbar.\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$shown (boolean): Whether the admin toolbar clock widget should be shown. Default of true.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Only show the admin toolbar clock for the 'boss' user.\n *\n * @param $show bool Status of whether the admin toolbar clock should be shown.\n * @return bool\n *\u002F\nfunction restrict_blog_time_widget_appearance( $show ) {\n    return 'boss' === get_current_user()->user_login;\n}\nadd_filter( 'c2c_blog_time_toolbar_widget_for_user', 'restrict_blog_time_widget_appearance' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>c2c_blog_time_active_clock (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>'c2c_blog_time_active_clock'\u003C\u002Fcode> hook returns the boolean value indicating if the Javascript-powered dynamic clock introduced in v2.0 should be enabled or if instead the v1.x era behavior of a static timestamp that can be clicked to update the timestamp via AJAX should be enabled. By default the dynamic clock is enabled.\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$allow (boolean): Boolean indicating if the admin widget should be a dynamic clock. Default is true.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F Disable the dynamic clock and use the static timestamp (whcih can be clicked to update the time via AJAX) instead.\nadd_filter( 'c2c_blog_time_active_clock', '__return_false' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Display the time according to your blog via an admin toolbar widget, a sidebar widget, and\u002For a template tag.",600,25105,72,8,"2021-07-29T08:59:00.000Z","5.8.13","4.6",[92,93,22,94,24],"blog","clock","server","https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Fblog-time\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblog-time.4.0.1.zip",{"slug":98,"name":99,"version":61,"author":100,"author_profile":101,"description":102,"short_description":103,"active_installs":27,"downloaded":104,"rating":105,"num_ratings":34,"last_updated":106,"tested_up_to":107,"requires_at_least":25,"requires_php":108,"tags":109,"homepage":113,"download_link":114,"security_score":57,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"timeline-express-date-time-add-on","Timeline Express – Date – Time Add-On","Code Parrots","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodeparrots\u002F","\u003Cp>When active, the Timeline Express – Date – Time Add-On will hide the default announcement date field, and generate a date and time field for you to use.\u003C\u002Fp>\n\u003Cp>Multiple announcements that have the same date & time will fallback to use the published date to dictate order on the timeline.\u003C\u002Fp>\n\u003Ch3>Developers\u003C\u002Fh3>\n\u003Cp>Filters:\u003Cbr \u002F>\n\u003Cstrong>timeline_express_date_time_formats\u003C\u002Fstrong> – Add your own date formats to the announcement.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Example:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\n\u002F**\n * Assign a custom date format to the announcements.\n *\n * @param array $date_formats The original date formats array.\n *\u002F\nfunction timeline_express_demo_custom_date_format( $date_formats ) {\n\n    $date_formats['custom'] = 'Y-m-d'; \u002F\u002F eg: 2018-10-02\n\n}\nadd_filter( 'timeline_express_date_time_formats', 'timeline_express_demo_custom_date_format' );\n\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>timeline_express_date_time_query_args\u003C\u002Fstrong> – Filter the query run for the date time add-on.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Example:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\n\u002F**\n * Filter the announcement date time add-on query.\n * Fall back to post titles instead of published date when announcements contain the same date-time values.\n *\n * @param array $query_args The original date time add-on query arguments.\n *\u002F\nfunction timeline_express_demo_filter_query_args( $query_args ) {\n\n    unset( $query_args['orderby'] );\n\n    $query_args['orderby'] = 'meta_value_num title';\n\n    return $query_args;\n\n}\nadd_filter( 'timeline_express_date_time_query_args', 'timeline_express_demo_filter_query_args' );\n\u003C\u002Fpre>\n","Assign and display times alongside the announcement dates in Timeline Express announcements.",3706,46,"2023-03-22T07:35:00.000Z","6.2.9","5.6",[110,20,21,111,112],"add-on","express","timeline","https:\u002F\u002Fwww.wp-timelineexpress.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftimeline-express-date-time-add-on.1.0.1.zip",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":123,"downloaded":124,"rating":27,"num_ratings":67,"last_updated":125,"tested_up_to":126,"requires_at_least":25,"requires_php":25,"tags":127,"homepage":25,"download_link":130,"security_score":57,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"startend-subscription-add-on-for-gravityforms","STARTEND Subscription Add-On for GravityForms","4.0.6","Concurrent","https:\u002F\u002Fprofiles.wordpress.org\u002Fcncrrnt\u002F","\u003Cp>STARTEND is a Gravity Forms Add-on that allows you to set one or many future start dates and customize an automated end date for your Gravity Forms Stripe Subscriptions.\u003C\u002Fp>\n\u003Cp>\u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Combine with GravityStripe for a full-fledged Subscription Management Solution! \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">←\u003C\u002Fspan>\u003C\u002Fp>\n\u003Ch3>BASIC VERSION\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Set a single or multiple future start dates\u003C\u002Fli>\n\u003Cli>Set a single or multiple fixed end dates\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>PREMIUM VERSION\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Set a single or multiple future start dates\u003C\u002Fli>\n\u003Cli>Set a single or multiple fixed end dates\u003C\u002Fli>\n\u003Cli>End a subscription after a specified number of payments\u003C\u002Fli>\n\u003Cli>End a subscription after a specified term limit\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Examples\u003C\u002Fh3>\n\u003Cp>1) Summer camp has 3 different start dates. The camp charges on the first day of camp. 1 week later the second and final automated payment comes out.\u003Cbr \u002F>\nSolution\u003Cbr \u002F>\n3 drop-down dates for parents to select from. The billing cycle is set to weekly. The subscription ends after 2 payments.\u003C\u002Fp>\n\u003Cp>2) A purchaser has the option to pay for a product in full or in 6 month installments.\u003Cbr \u002F>\nSolution\u003Cbr \u002F>\nPay in full charges the user using a product feed in Stripe. The installment option triggers the conditional subscription feed. Only the end date setting is used. The billing cycle is set to monthly. The term limit option is used and set to 6 months.\u003C\u002Fp>\n\u003Cp>3) A service charges a user every month for one year. If the service subscription isn’t renewed, it cancels automatically.\u003Cbr \u002F>\nSolution\u003Cbr \u002F>\nOnly the end date setting is used. The billing cycle is set to annual. The “x number of payments” option is used and set to 1.\u003C\u002Fp>\n\u003Cp>STARTEND is the only way to fully customize the start and end date for Stripe subscriptions on Gravity forms.\u003Cbr \u002F>\nDownload the Basic Version or BUY THE PRO VERSION Today!\u003Cbr \u002F>\nBasic Version comes with limited forum support, Pro Version comes with priority ticket support.\u003C\u002Fp>\n\u003Cp>Want to give subscribers the ability to manage their subscriptions on their own? Check out [https:\u002F\u002Fgravitystripe.com]https:\u002F\u002Fgravitystripe.com GravityStripe! With STARTEND and GravityStripe you can save hundreds of dollars per year and turn your website into a full-fledged subscription management platform that YOU control.\u003C\u002Fp>\n\u003Ch3>Video\u003C\u002Fh3>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F0XOCdS21XdU?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n","Description: STARTEND is a Gravity Forms Add-on that allows you to set one or many future start dates and customize an automated end date for your Gra …",20,1018,"2024-02-21T18:43:00.000Z","6.3.8",[20,21,54,128,129],"gravity-forms-stripe","stripe","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fstartend-subscription-add-on-for-gravityforms.zip",{"attackSurface":132,"codeSignals":163,"taintFlows":185,"riskAssessment":186,"analyzedAt":191},{"hooks":133,"ajaxHandlers":159,"restRoutes":160,"shortcodes":161,"cronEvents":162,"entryPointCount":28,"unprotectedCount":28},[134,141,147,150,155],{"type":135,"name":136,"callback":137,"priority":138,"file":139,"line":140},"action","gform_loaded","load",5,"gf-datetime-field-add-on.php",15,{"type":135,"name":142,"callback":143,"priority":144,"file":145,"line":146},"gform_field_standard_settings","datetime_field_standard_settings",10,"includes\\class-awaiswp-datetime-field-settings.php",19,{"type":135,"name":148,"callback":149,"file":145,"line":123},"gform_editor_js","datetime_field_editor_script",{"type":151,"name":152,"callback":153,"file":145,"line":154},"filter","gform_tooltips","datetime_add_tooltips",22,{"type":151,"name":156,"callback":157,"file":145,"line":158},"gform_pre_render","datetime_add_gf_form_script",23,[],[],[],[],{"dangerousFunctions":164,"sqlUsage":165,"outputEscaping":167,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":184},[],{"prepared":28,"raw":28,"locations":166},[],{"escaped":168,"rawEcho":169,"locations":170},9,6,[171,174,176,178,180,182],{"file":145,"line":172,"context":173},45,"raw output",{"file":145,"line":175,"context":173},170,{"file":145,"line":177,"context":173},183,{"file":145,"line":179,"context":173},204,{"file":145,"line":181,"context":173},208,{"file":145,"line":183,"context":173},221,[],[],{"summary":187,"deductions":188},"The static analysis of gf-datetime-field-add-on v1.3.6 reveals a plugin with an extremely limited attack surface, showing zero AJAX handlers, REST API routes, shortcodes, or cron events. This absence of common entry points is a strong indicator of good security design. Furthermore, the code analysis shows no dangerous functions, no file operations, no external HTTP requests, and importantly, all SQL queries are properly prepared. This demonstrates a commitment to preventing common web vulnerabilities like SQL injection.\n\nHowever, a notable concern arises from the output escaping. With 15 total outputs and only 60% properly escaped, there is a significant risk of Cross-Site Scripting (XSS) vulnerabilities. This means user-supplied or dynamic data might be rendered on a page without adequate sanitization, allowing attackers to inject malicious scripts. The complete absence of nonce checks and capability checks on potential (though currently non-existent) entry points, while less critical with zero entry points, could become a risk if new functionality is added without proper security considerations.\n\nThe plugin's vulnerability history is clean, with zero recorded CVEs. This, combined with the strong static analysis findings regarding SQL and dangerous functions, suggests a historically well-maintained and secure plugin. The primary weakness identified is the insufficient output escaping, which represents a tangible risk. In conclusion, while the plugin exhibits excellent practices in preventing injection attacks and maintaining a minimal attack surface, the XSS risk due to poor output escaping warrants attention.",[189],{"reason":190,"points":169},"Output escaping is only 60% proper","2026-03-16T19:04:41.627Z",{"wat":193,"direct":204},{"assetPaths":194,"generatorPatterns":198,"scriptPaths":199,"versionParams":200},[195,196,197],"\u002Fwp-content\u002Fplugins\u002Fgf-datetime-field-add-on\u002Fassets\u002Fcss\u002Fdatetimepicker.min.css","\u002Fwp-content\u002Fplugins\u002Fgf-datetime-field-add-on\u002Fassets\u002Fjs\u002Fdatetimepicker.min.js","\u002Fwp-content\u002Fplugins\u002Fgf-datetime-field-add-on\u002Fassets\u002Fjs\u002Fgform_datetime_field.js",[],[196,197],[201,202,203],"gf-datetime-field-add-on\u002Fassets\u002Fcss\u002Fdatetimepicker.min.css?ver=","gf-datetime-field-add-on\u002Fassets\u002Fjs\u002Fdatetimepicker.min.js?ver=","gf-datetime-field-add-on\u002Fassets\u002Fjs\u002Fgform_datetime_field.js?ver=",{"cssClasses":205,"htmlComments":207,"htmlAttributes":208,"restEndpoints":210,"jsGlobals":211,"shortcodeOutput":213},[206],"datetime_format_value_setting",[],[209],"field_datetime_format_value",[],[212],"fieldSettings",[]]