[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f9xwkahNK63cNodf57AOpaAVJ3chkzUJHcv7p_rvpL48":3,"$fYESfJBqYrOQhe06O0nTgwcu2KczBSivqG_ut97slBAk":251,"$fI4XfRjwA2Hsce0NvpcMqV_rCfROzvStItz9rcLbsaaE":256},{"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,"discovery_status":31,"vulnerabilities":32,"developer":33,"crawl_stats":29,"alternatives":37,"analysis":134,"fingerprints":231},"field-helper-for-gravity-forms","Field Helper for Gravity Forms","1.10.6","brilliantplugins","https:\u002F\u002Fprofiles.wordpress.org\u002Fbrilliantplugins\u002F","\u003Cp>Adds a settings page and REST API endpoint to retrieve human- and computer-friendly field names.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Ffield-helper-for-gravity-forms.brilliantplugins.info\" rel=\"nofollow ugc\">field-helper-for-gravity-forms.brilliantplugins.info\u003C\u002Fa> for more documentation.\u003C\u002Fp>\n\u003Cp>Looking to import Gravity Forms entries from your WordPress website into FileMaker?\u003C\u002Fp>\n\u003Cp>Create nearly any form with Gravity Form’s drag-and-drop interface, and use this plugin to quickly import that form’s entry data to your FileMaker solution via \u003Ca href=\"fmflare.com\" rel=\"nofollow ugc\">fmFlare\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Create a Gravity Forms API key.\u003C\u002Fli>\n\u003Cli>On each form, go to the Field Helper settings tab and set the friendly names for the fields you need.\u003C\u002Fli>\n\u003Cli>Append \u003Ccode>\u002Fjson\u003C\u002Fcode> to Gravity Forms’ form- or entry-related endpoints to get JSON field data.\u003C\u002Fli>\n\u003Cli>Retrieve all entries:  \u003Ccode>https:\u002F\u002Fyour-site.com\u002Fwp-json\u002Fgf\u002Fv2\u002Fentries\u002Fjson\u002F\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Retrieve a specific entry:  \u003Ccode>https:\u002F\u002Fyour-site.com\u002Fwp-json\u002Fgf\u002Fv2\u002Fentries\u002F\u003Centry_id>\u002Fjson\u002F\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Retrieve all entries from a specific form:  \u003Ccode>https:\u002F\u002Fyour-site.com\u002Fwp-json\u002Fgf\u002Fv2\u002Fforms\u002F\u003Cform_id>\u002Fjson\u002F\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Retrieve a specific entry from a specific form:  \u003Ccode>https:\u002F\u002Fyour-site.com\u002Fwp-json\u002Fgf\u002Fv2\u002Fforms\u002F\u003Cform_id>\u002Fentries\u002F\u003Centry_id>\u002Fjson\u002F\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you need to use the friendly field names in PHP (using the \u003Ccode>gform_after_submission\u003C\u002Fcode> hook, for instance), follow this example:\u003C\u002Fp>\n\u003Cpre>\n\u002F\u002F Assuming $entry is a single form entry.\n\u002F\u002F You can retrieve an entry by id using GFAPI::get_entry( $id );\n$entry_with_friendly_names = GF_Field_Helper_Common::replace_field_names( $entry );\n\u003C\u002Fpre>\n","Adds a settings page and REST API endpoint to retrieve human- and computer-friendly field names.",50,5033,100,1,"2024-11-05T21:07:00.000Z","6.2.9","4.8","",[20,21,22,23,24],"api","filemaker","form-entries","forms","gravity-forms","https:\u002F\u002Fbrilliantplugins.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.10.6.zip",92,0,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":11,"avg_security_score":27,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},30,88,"2026-05-20T04:32:08.675Z",[38,59,80,99,118],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":27,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":18,"download_link":58,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"retrigger-notifications-gravity-forms","Retrigger Notifications Gravity Forms","1.3","wpspin","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpspin\u002F","\u003Cp>\u003Cstrong>Retrigger Notifications Gravity Forms\u003C\u002Fstrong> lets you manually re-send Gravity Forms entry data to external Zapier and Webhook API feeds — directly from the WordPress admin, without resubmitting the form.\u003C\u002Fp>\n\u003Cp>Whether a webhook failed silently, Zapier missed a trigger, or you simply need to push historical entries to a new integration, this plugin has you covered.\u003C\u002Fp>\n\u003Ch3>🔄 What It Does\u003C\u002Fh3>\n\u003Cp>When Gravity Forms sends entry data to Zapier or Webhooks, things don’t always go right. Endpoints go down, APIs timeout, and integrations break. Instead of asking users to resubmit, this plugin lets you \u003Cstrong>retrigger the feed\u003C\u002Fstrong> for any entry — individually or in bulk.\u003C\u002Fp>\n\u003Ch3>✅ Use Cases\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Cstrong>🔁 Resend failed Zapier triggers\u003C\u002Fstrong> — A Zap didn’t fire? Retrigger it from the entry detail page without asking the user to resubmit.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🌐 Resend failed Webhook deliveries\u003C\u002Fstrong> — Push entry data again to your Webhook endpoint when the first attempt failed or timed out.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📦 Bulk resend entries to Zapier\u003C\u002Fstrong> — Select multiple entries from the Entries list and resend them all to Zapier feeds in one action.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📦 Bulk resend entries to Webhooks\u003C\u002Fstrong> — Select multiple entries and push them all to Webhook endpoints at once.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🐛 Debug API integrations\u003C\u002Fstrong> — Use the built-in test endpoint and GF logging to troubleshoot why data isn’t reaching your external service.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🔗 Connect a new Zapier integration to old entries\u003C\u002Fstrong> — Set up a new Zap and retrigger historical entries so they flow into the new workflow.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🔗 Connect a new Webhook to old entries\u003C\u002Fstrong> — Added a new Webhook feed? Push past entries through it without resubmission.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🛠️ Test Zapier\u002FWebhook setup during development\u003C\u002Fstrong> — Quickly retrigger entries while building and testing your automation pipeline.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📊 Sync data after downtime\u003C\u002Fstrong> — If your external service was down during form submissions, retrigger all affected entries once it’s back online.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🔍 Verify data delivery\u003C\u002Fstrong> — Retrigger a single entry and check GF logs to confirm data was sent and received correctly.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>⚙️ Settings & Usage\u003C\u002Fh3>\n\u003Cp>This plugin works seamlessly within the existing Gravity Forms interface — no separate settings page required.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Single Entry Resend:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>Forms \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Entries\u003C\u002Fstrong> in your WordPress admin.\u003C\u002Fli>\n\u003Cli>Click on any entry to open the \u003Cstrong>Entry Detail\u003C\u002Fstrong> page.\u003C\u002Fli>\n\u003Cli>In the right sidebar, you’ll see \u003Cstrong>“Resend Zapier Feeds”\u003C\u002Fstrong> and\u002For \u003Cstrong>“Resend Webhook Feeds”\u003C\u002Fstrong> panels.\u003C\u002Fli>\n\u003Cli>Check the feeds you want to retrigger.\u003C\u002Fli>\n\u003Cli>Click the \u003Cstrong>Resend\u003C\u002Fstrong> button. Done!\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Bulk Resend:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>Forms \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Entries\u003C\u002Fstrong> and select the entries you want to resend.\u003C\u002Fli>\n\u003Cli>Choose \u003Cstrong>“Resend Zapier Feeds”\u003C\u002Fstrong> or \u003Cstrong>“Resend Webhook Feeds”\u003C\u002Fstrong> from the \u003Cstrong>Bulk Actions\u003C\u002Fstrong> dropdown.\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Apply\u003C\u002Fstrong>. Confirm the action in the popup dialog.\u003C\u002Fli>\n\u003Cli>All selected entries will be resent to the configured feeds.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Debugging:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable \u003Cstrong>Gravity Forms Logging\u003C\u002Fstrong> under Forms \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Logging.\u003C\u002Fli>\n\u003Cli>Use the built-in test endpoint (\u003Ccode>\u002Fwp-json\u002Fgf\u002Fv1\u002Ftest-webhook-api\u003C\u002Fcode>) to verify webhook delivery.\u003C\u002Fli>\n\u003Cli>All retrigger operations are logged to the GF debug log.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>🧩 Works Great With These Plugins\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002F\" rel=\"nofollow ugc\">Gravity Forms\u003C\u002Fa>\u003C\u002Fstrong> — Required. The form plugin this addon extends.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002Fadd-ons\u002Fzapier\u002F\" rel=\"nofollow ugc\">Gravity Forms Zapier Add-On\u003C\u002Fa>\u003C\u002Fstrong> — Required for Zapier retrigger features.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002Fadd-ons\u002Fwebhooks\u002F\" rel=\"nofollow ugc\">Gravity Forms Webhooks Add-On\u003C\u002Fa>\u003C\u002Fstrong> — Required for Webhook retrigger features.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravitykit.com\u002Fproducts\u002Fgravityview\u002F\" rel=\"nofollow ugc\">GravityView\u003C\u002Fa>\u003C\u002Fstrong> — Display entries on the frontend; use Retrigger to fix API issues behind the scenes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fgravitywiser.com\u002F\" rel=\"nofollow ugc\">Gravity Perks\u003C\u002Fa>\u003C\u002Fstrong> — Advanced Gravity Forms snippets and utilities that complement this plugin.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fgravityflow.io\u002F\" rel=\"nofollow ugc\">Gravity Flow\u003C\u002Fa>\u003C\u002Fstrong> — Workflow automation for Gravity Forms; retrigger feeds at any workflow step.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwp-webhooks.com\u002F\" rel=\"nofollow ugc\">WP Webhooks\u003C\u002Fa>\u003C\u002Fstrong> — Extend your webhook capabilities beyond Gravity Forms.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fzapier.com\u002F\" rel=\"nofollow ugc\">Zapier\u003C\u002Fa>\u003C\u002Fstrong> — The automation platform this plugin integrates with for retriggering Zaps.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.make.com\u002F\" rel=\"nofollow ugc\">Make (formerly Integromat)\u003C\u002Fa>\u003C\u002Fstrong> — Use with Gravity Forms Webhooks to push data to Make scenarios.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002Fadd-ons\u002Fsmtp\u002F\" rel=\"nofollow ugc\">Gravity SMTP\u003C\u002Fa>\u003C\u002Fstrong> — Reliable email delivery alongside your retriggered API feeds.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>📋 Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>WordPress 4.0 or higher\u003C\u002Fli>\n\u003Cli>Licensed \u003Cstrong>Gravity Forms\u003C\u002Fstrong> plugin (active)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Zapier Add-On\u003C\u002Fstrong> enabled (for Zapier features)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Webhooks Add-On\u003C\u002Fstrong> enabled (for Webhook features)\u003C\u002Fli>\n\u003C\u002Ful>\n","Resend Gravity Forms entry data to Zapier and Webhook feeds with one click -- no need to resubmit the form.",1000,6494,5,"2026-02-12T20:35:00.000Z","6.9.4","4.0.0","7.0",[24,54,55,56,57],"gravity-forms-addon","resend-notifications","webhooks","zapier","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fretrigger-notifications-gravity-forms.1.3.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":28,"num_ratings":28,"last_updated":69,"tested_up_to":70,"requires_at_least":71,"requires_php":72,"tags":73,"homepage":77,"download_link":78,"security_score":79,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"integration-of-zoho-crm-and-gravity-forms","Integration of Zoho CRM and Gravity Forms","1.0.3","formsintegrations","https:\u002F\u002Fprofiles.wordpress.org\u002Fformsintegrations\u002F","\u003Cp>Visit plugin’s \u003Ca href=\"https:\u002F\u002Fformsintegrations.com\u002Fgravity-forms-integration-with-zoho-crm\" rel=\"nofollow ugc\">website\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Looking for an easy way to integrate \u003Cstrong>Gravity Forms with Zoho CRM\u003C\u002Fstrong>? Look no further than the Integrations of Zoho CRM with Gravity Forms plugin from WordPress! This plugin simplifies the process of connecting your Zoho CRM account and Gravity Forms, making it easy to collect and manage your customer data. Optimize your website’s functionality with this powerful plugin today!\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Check out our step-by-step tutorial on Zoho CRM Integration with Gravity Forms\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Things you need to use this plug-in :\u003C\u002Fstrong>\u003Cbr \u002F>\n1. Gravity Forms.\u003Cbr \u002F>\n2. Zoho CRM account.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Setup process for Gravity Forms integration with Zoho CRM:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to this plugin\u003C\u002Fli>\n\u003Cli>Select form created by Gravity Forms from which you want to send data in Zoho CRM\u003C\u002Fli>\n\u003Cli>Then go to Zoho CRM authorization page\u003C\u002Fli>\n\u003Cli>Click on “\u003Ca href=\"https:\u002F\u002Fapi-console.zoho.com\u002F\" rel=\"nofollow ugc\">Zoho API Console\u003C\u002Fa>“\u003C\u002Fli>\n\u003Cli>Select “Server Side Applications”\u003C\u002Fli>\n\u003Cli>Give a client name but I cannot contain keyword “\u003Cstrong>Zoho\u003C\u002Fstrong>“\u003C\u002Fli>\n\u003Cli>Copy “Homepage URL” and “Authorized Redirect URIs” from the plugin\u003C\u002Fli>\n\u003Cli>It will generate “Client ID” and “Client Secret”, paste it in the plugin\u003C\u002Fli>\n\u003Cli>Complete the authorization process\u003C\u002Fli>\n\u003Cli>Now select Zoho CRM module and layout where you want to send data\u003C\u002Fli>\n\u003Cli>Map Gravity Forms fields with Zoho CRM fields\u003C\u002Fli>\n\u003Cli>Here we go, you successfully set up the integration between Gravity Forms and Zoho CRM.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Note: Authorization compatible with Zoho CRM Plus and Zoho One within the scope CRM.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Timeline\u002FLog:\u003C\u002Fstrong>\u003Cbr \u002F>\nHere you can see the API response from Zoho CRM after Gravity Forms is submitted. You will get a response whether the submission is successful or failed. It will help you to debug the situation.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>FEATURES ON FREE VERSION:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>User can send any Gravity Forms data to leads module of Zoho CRM.\u003C\u002Fli>\n\u003Cli>Users can make one integration at a time.\u003C\u002Fli>\n\u003Cli>Users can map only two fields of Zoho CRM.\u003C\u002Fli>\n\u003Cli>This plugin allow user to send custom value also.\u003C\u002Fli>\n\u003Cli>Support file upload from Gravity Forms widget to Zoho CRM.\u003C\u002Fli>\n\u003Cli>View the detailed log of submitted data from the plugin dashboard.\u003C\u002Fli>\n\u003Cli>Advance conditional logic.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fformsintegrations.com\u002Fgravity-forms-integration-with-zoho-crm\" rel=\"nofollow ugc\">FEATURES ON PRO VERSION\u003C\u002Fa>:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>All the default modules (lead, deal, contact etc.) from Zoho CRM are available in pro plugin.\u003C\u002Fli>\n\u003Cli>Zoho CRM Custom modules are available.\u003C\u002Fli>\n\u003Cli>All the default layouts are available.\u003C\u002Fli>\n\u003Cli>Custom layouts are available.\u003C\u002Fli>\n\u003Cli>You can map unlimited field of Gravity Forms and Zoho CRM.\u003C\u002Fli>\n\u003Cli>WordPress meta data\u002Fsmart data fields are available for field mapping with Zoho CRM.\u003C\u002Fli>\n\u003Cli>Zoho CRM related list is available to send data and you can send data in multiple related list.\u003C\u002Fli>\n\u003Cli>All the actions are available in pro plugin.\u003C\u002Fli>\n\u003Cli>You can do multiple\u002Funlimited integrations.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>\u003Cem>Here are the actions available in the pro version:\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Workflow: Triggers Zoho CRM workflows\u003C\u002Fli>\n\u003Cli>Attachment: Send file upload field data to Zoho CRM related list Attachments\u003C\u002Fli>\n\u003Cli>Approval list: Send entries to Zoho CRM approval list.\u003C\u002Fli>\n\u003Cli>Blueprint: Trigger Zoho CRM blueprint when a form is submitted via Gravity Forms.\u003C\u002Fli>\n\u003Cli>Capture GCLID: Sends the click id of Google ads\u002FAdWords ads to Zoho CRM.\u003C\u002Fli>\n\u003Cli>Upsert Record: When a form is submitted in Gravity Forms it will check if the same data is already in Zoho CRM. If a data with the identical value exists in Zoho CRM, it will be updated with the new values, if not it will create a new record\u002Flead\u002Fcontact in Zoho CRM.\u003C\u002Fli>\n\u003Cli>Assignment Rule: Trigger assignment rules in Zoho CRM when Gravity Forms submitted.\u003C\u002Fli>\n\u003Cli>Tag records: Add a tag to the record that is pushed in Zoho CRM.\u003C\u002Fli>\n\u003Cli>Record owner: Assign an owner of the record pushed to Zoho.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Visit plugin’s \u003Ca href=\"https:\u002F\u002Fformsintegrations.com\u002Fgravity-forms-integration-with-zoho-crm\" rel=\"nofollow ugc\">website\u003C\u002Fa>\u003C\u002Fp>\n","Visit plugin's website",20,1271,"2023-12-06T16:35:00.000Z","6.4.8","5.0","5.6",[20,24,74,75,76],"leads","zoho","zoho-crm","https:\u002F\u002Fformsintegrations.com\u002Fgravity-forms-integration-with-zoho-crm","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fintegration-of-zoho-crm-and-gravity-forms.zip",85,{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":88,"downloaded":89,"rating":28,"num_ratings":28,"last_updated":90,"tested_up_to":91,"requires_at_least":92,"requires_php":52,"tags":93,"homepage":97,"download_link":98,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"gf-rest-api-for-cross-platform","Rest API For Cross Platform Support with Gravity Forms","1.0.1","Weboccult Technologies Pvt Ltd","https:\u002F\u002Fprofiles.wordpress.org\u002Fweboccults\u002F","\u003Cp>This will provide generated API links and a dataset which will be useful to cross-platform developers to send data to WordPress.\u003C\u002Fp>\n\u003Ch3>FEATURES\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Users can generate form-wise API custom endpoint name.\u003C\u002Fli>\n\u003Cli>Users can easily copy API link and dataset to share with cross-platform developers.\u003C\u002Fli>\n\u003Cli>Refresh button provided to regenerate dataset when any changes are made in form fields.\u003C\u002Fli>\n\u003Cli>Dataset contains all required information related to fields used in Gravity Form.\u003C\u002Fli>\n\u003Cli>Support for png, jpg, jpeg, pdf, doc, and docx file type.\u003C\u002Fli>\n\u003Cli>Blog posts can be created using this plugin from cross-platform.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>STEPS TO USE\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Go to the particular gravity form setting tab, You will find Generate API tab.\u003C\u002Fli>\n\u003Cli>Enter the API name and click on Generate API button to create API and dataset.\u003C\u002Fli>\n\u003Cli>Copy API link and dataset to use on cross-platform.\u003C\u002Fli>\n\u003Cli>When any changes are made on Gravity Form, use Refresh Button in Generate API tab to regenerate the dataset.\u003C\u002Fli>\n\u003C\u002Ful>\n","Create a custom API for Gravity Forms to support cross-platform entries from frameworks like React, AngularJS, and other platforms.",10,1457,"2025-06-12T06:06:00.000Z","6.8.5","6.2",[94,95,24,96],"api-for-angular-integration","api-for-react-integration","restapi","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fgf-rest-api-for-cross-platform\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgf-rest-api-for-cross-platform.1.0.1.zip",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":28,"downloaded":107,"rating":28,"num_ratings":28,"last_updated":108,"tested_up_to":50,"requires_at_least":109,"requires_php":110,"tags":111,"homepage":116,"download_link":117,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"gravityops-search","GravityOps Search – Search and Display Gravity Forms Entries","1.0.6.1","BrightLeaf Digital","https:\u002F\u002Fprofiles.wordpress.org\u002Feitanatbrightleaf\u002F","\u003Cp>GravityOps Search is a free, powerful shortcode for searching Gravity Forms entries on the front end and displaying the matching results anywhere on your site. Instead of paging through the admin entries screen, you can drop a single shortcode into a page, post, GravityView, or custom template and surface exactly the data you need. It works like an Excel-style lookup for Gravity Forms entries: you define which forms and fields to search, how to compare the values, and what to output for each match.\u003C\u002Fp>\n\u003Cp>The core \u003Ccode>[gravops_search]\u003C\u002Fcode> shortcode lets you target one form, several forms, or even all forms at once. You can filter by one field or many, pass in values directly in the shortcode content, and control whether entries must match all conditions or any of them. The same shortcode can handle simple lookups (showing a single field from the latest matching entry) or more complex reporting-style views that combine fields, entry properties, and custom HTML. Because everything is driven by attributes, you stay in full control of which entries are included and how their data appears on the front end.\u003C\u002Fp>\n\u003Cp>Results are rendered through a flexible \u003Ccode>display\u003C\u002Fcode> attribute, which understands both simple comma-separated field lists and advanced custom display strings with placeholders. You can output raw values, mix multiple fields into labeled text, or construct HTML lists, tables, and cards with links, CSS classes, and nested shortcodes. This gives you a fully custom front-end listing of Gravity Forms entries that you can drop into any layout, theme, or builder, without building a custom query or touching PHP.\u003C\u002Fp>\n\u003Cp>GravityOps Search fully supports Gravity Forms entry properties (such as entry ID, form ID, created-by, and more) alongside regular fields, and it includes options for sorting, limiting, and deduplicating results before they are rendered. You can sort by field values or entry properties, choose ascending, descending, or random ordering, add a secondary sort key, and request unique values only. When no entries match, you can show fallback text or per-field default values, so front-end visitors never see a broken layout or confusing blank output.\u003C\u002Fp>\n\u003Cp>This plugin is built explicitly for front-end entry search and display. It does not add live search tools to the Gravity Forms admin area and does not replace the Entries screen. Instead, it focuses on one thing and does it well: querying Gravity Forms entries in the background and printing clean, formatted results on the pages your users actually see.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Front-end search for Gravity Forms entries using a single, flexible shortcode.\u003C\u002Fli>\n\u003Cli>Target all forms, a single form, or a comma-separated list of form IDs using the \u003Ccode>target\u003C\u002Fcode> attribute.\u003C\u002Fli>\n\u003Cli>Filter entries by a comma-separated list of field IDs or entry properties via the \u003Ccode>search\u003C\u002Fcode> attribute.\u003C\u002Fli>\n\u003Cli>Pass search values in the shortcode content, separated by a pipe (\u003Ccode>|\u003C\u002Fcode>) to match positions with the fields in \u003Ccode>search\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Choose whether entries must match all search conditions (default) or any condition by setting \u003Ccode>search_mode=\\\"any\\\"\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Use the \u003Ccode>operators\u003C\u002Fcode> attribute to control how each value is compared to its field, with support for equals, not-equals, partial matches, SQL-style \u003Ccode>LIKE\u003C\u002Fcode>, “in” \u002F “not in” arrays, and numeric comparisons (greater than \u002F less than \u002F greater-or-equal \u002F less-or-equal).\u003C\u002Fli>\n\u003Cli>Display one or many fields and properties for each result using the \u003Ccode>display\u003C\u002Fcode> attribute, which supports both simple lists and rich custom templates.\u003C\u002Fli>\n\u003Cli>Include entry properties and field values in your output using placeholder formats like \u003Ccode>{13}\u003C\u002Fcode>, \u003Ccode>{id}\u003C\u002Fcode>, \u003Ccode>{form_id}\u003C\u002Fcode>, and \u003Ccode>{gos:id}\u003C\u002Fcode> where appropriate.\u003C\u002Fli>\n\u003Cli>Build fully custom HTML output (lists, tables, cards, badges, buttons, links) directly inside the \u003Ccode>display\u003C\u002Fcode> string.\u003C\u002Fli>\n\u003Cli>Insert CSS classes and inline markup into the output so results adopt your theme’s design and layout patterns.\u003C\u002Fli>\n\u003Cli>Use the \u003Ccode>separator\u003C\u002Fcode> attribute to control how multiple entry results are separated (including HTML separators or no separator at all using \u003Ccode>__none__\u003C\u002Fcode>).\u003C\u002Fli>\n\u003Cli>Sort entries using \u003Ccode>sort_key\u003C\u002Fcode>, \u003Ccode>sort_direction\u003C\u002Fcode>, and \u003Ccode>sort_is_num\u003C\u002Fcode>, with optional \u003Ccode>secondary_sort_key\u003C\u002Fcode> and \u003Ccode>secondary_sort_direction\u003C\u002Fcode> for tie-breaking.\u003C\u002Fli>\n\u003Cli>Limit the number of results returned with \u003Ccode>limit\u003C\u002Fcode>, including support for \u003Ccode>limit=\\\"all\\\"\u003C\u002Fcode> when you need to show every matching entry.\u003C\u002Fli>\n\u003Cli>Turn on \u003Ccode>unique\u003C\u002Fcode> to return only unique result values, great for building deduplicated lists such as unique email addresses, user IDs, or other fields.\u003C\u002Fli>\n\u003Cli>Search for empty or blank values with the \u003Ccode>search_empty\u003C\u002Fcode> attribute and an empty shortcode content, to find incomplete or missing data.\u003C\u002Fli>\n\u003Cli>Provide fallback values when no entries match—or when individual fields are empty—using the \u003Ccode>default\u003C\u002Fcode> attribute.\u003C\u002Fli>\n\u003Cli>Add an admin link to each result with the \u003Ccode>link\u003C\u002Fcode> attribute so power users can jump directly from the front end to the entry in the Gravity Forms admin.\u003C\u002Fli>\n\u003Cli>Designed to work smoothly alongside GravityView, GravityMath, and other shortcodes that can be nested inside the output.\u003C\u002Fli>\n\u003Cli>Compatible with the legacy \u003Ccode>gfsearch\u003C\u002Fcode> snippet approach while offering ongoing updates and a more robust, plugin-based implementation.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>How It Works\u003C\u002Fh3>\n\u003Cp>At its core, GravityOps Search evaluates your shortcode attributes and content to determine which entries to fetch, then formats each matching entry according to the \u003Ccode>display\u003C\u002Fcode> string you provide. The \u003Ccode>target\u003C\u002Fcode> attribute defines which forms to query: pass \u003Ccode>0\u003C\u002Fcode> to search all forms, a single form ID to target one form, or a comma-separated list of IDs for multi-form searches. The \u003Ccode>search\u003C\u002Fcode> attribute specifies the field IDs and entry properties to filter on, and the shortcode content supplies the corresponding values, separated by the pipe (\u003Ccode>|\u003C\u002Fcode>) character in the same order.\u003C\u002Fp>\n\u003Cp>You can configure the \u003Ccode>search_mode\u003C\u002Fcode> attribute to determine matching logic. The default mode (\u003Ccode>all\u003C\u002Fcode>) requires each entry to satisfy all conditions, while \u003Ccode>search_mode=\\\"any\\\"\u003C\u002Fcode> returns entries that meet at least one of the conditions listed. This gives you the flexibility to build both strict, multi-field filters and more permissive, keyword-style searches. If you need to perform a global search across all fields for a given value, you can leave the relevant search ID blank, and the plugin will look for that value anywhere in the entry.\u003C\u002Fp>\n\u003Cp>Sorting, limiting, and uniqueness are handled after the search conditions are applied. You can specify a \u003Ccode>sort_key\u003C\u002Fcode> (field ID, entry property, or meta key) with \u003Ccode>sort_direction\u003C\u002Fcode> set to \u003Ccode>ASC\u003C\u002Fcode>, \u003Ccode>DESC\u003C\u002Fcode>, or \u003Ccode>RAND\u003C\u002Fcode>. If you are sorting by numeric data, \u003Ccode>sort_is_num\u003C\u002Fcode> ensures values are compared correctly rather than as plain strings. When you need a consistent secondary ordering—such as sorting first by date and then by name—you can use \u003Ccode>secondary_sort_key\u003C\u002Fcode> and \u003Ccode>secondary_sort_direction\u003C\u002Fcode>. Once ordered, the plugin applies the \u003Ccode>limit\u003C\u002Fcode> attribute to control how many entries are actually returned and optionally filters down to unique results based on the full rendered output when \u003Ccode>unique\u003C\u002Fcode> is enabled.\u003C\u002Fp>\n\u003Cp>Defaults and fallbacks keep your front-end output robust. The \u003Ccode>default\u003C\u002Fcode> attribute can define text to display when no entries are found or when specific fields are empty, and the plugin can handle multiple default values mapped to multiple display fields. The \u003Ccode>separator\u003C\u002Fcode> attribute governs how multiple entries are joined, making it easy to build line-separated lists, HTML \u003Ccode>elements, or table rows. Because each [gravops_search]\u003C\u002Fcode> shortcode runs its own live database query, you can place different instances around your site to build different views of the same underlying Gravity Forms data.\u003C\u002Fp>\n\u003Ch3>Display and Formatting\u003C\u002Fh3>\n\u003Cp>The \u003Ccode>display\u003C\u002Fcode> attribute is the heart of how results are shown. In its simplest form, you can pass a comma-separated list of field IDs or entry properties, such as \u003Ccode>display=\\\"13,14,15\\\"\u003C\u002Fcode>. For each matching entry, GravityOps Search outputs those values in order, using sensible default separators between fields and entries. This mode is ideal when you simply need to surface raw values: a quick list of email addresses, a set of IDs, or basic single-column output.\u003C\u002Fp>\n\u003Cp>For more control, \u003Ccode>display\u003C\u002Fcode> supports custom display strings with placeholders. Instead of a list of IDs, you can provide a template like \u003Ccode>display=\\\"Name: {13}, Email: {14}\\\"\u003C\u002Fcode>, which will be rendered for each matching entry. Placeholders like \u003Ccode>{13}\u003C\u002Fcode> insert the value of field 13, while placeholders such as \u003Ccode>{id}\u003C\u002Fcode> and \u003Ccode>{form_id}\u003C\u002Fcode> work with entry properties. When you need to reference non-numeric properties or use merge tags in contexts that parse standard tags (such as GravityView content fields, confirmations, or notifications), you can use the special \u003Ccode>{gos:id}\u003C\u002Fcode> syntax. This gives you a consistent way to assemble complex messages, labels, and markup that incorporate both field data and meta data.\u003C\u002Fp>\n\u003Cp>The \u003Ccode>display\u003C\u002Fcode> attribute also accepts full HTML, including tags, attributes, and CSS classes. You can wrap values in \u003Ccode>,\u003C\u002Fcode>, \u003Ccode>,\u003C\u002Fcode>, “, or any other markup to build lists, tables, cards, or media objects. Because the \u003Ccode>separator\u003C\u002Fcode> attribute supports HTML as well, you can structure your markup so that each entry becomes one list item, table row, or card component. This makes it straightforward to integrate entry results into existing sections of your design, matching your theme and layout without a custom PHP query.\u003C\u002Fp>\n\u003Ch3>Nesting Shortcodes and Advanced Templates\u003C\u002Fh3>\n\u003Cp>GravityOps Search supports nesting other shortcodes inside the \u003Ccode>display\u003C\u002Fcode> attribute via a double-curly-brace syntax: \u003Ccode>{{ ... }}\u003C\u002Fcode>. This means you can embed tools like GravityMath, another \u003Ccode>gravops_search\u003C\u002Fcode>, or any other shortcode directly inside the output template for each entry. The outer \u003Ccode>[gravops_search]\u003C\u002Fcode> processes its own placeholders first and then hands the rendered string to the nested shortcodes, allowing you to feed entry values into calculations, secondary lookups, or formatting helpers.\u003C\u002Fp>\n\u003Cp>When you nest a second \u003Ccode>gravops_search\u003C\u002Fcode> inside the \u003Ccode>display\u003C\u002Fcode> attribute, each shortcode runs its own search and display logic in sequence. The outer shortcode resolves placeholders such as \u003Ccode>{13}\u003C\u002Fcode> and \u003Ccode>{gos:id}\u003C\u002Fcode> in its \u003Ccode>display\u003C\u002Fcode> string, while the nested shortcode uses its own \u003Ccode>display\u003C\u002Fcode> template and attributes. In nested scenarios where you need to reference placeholder values as input to another shortcode or formula, you can use the \u003Ccode>gos:id\u003C\u002Fcode> pattern without braces (for example, \u003Ccode>gos:21\u003C\u002Fcode>) to avoid conflicts with merge-tag parsing. This lets you do things like passing a field value into a GravityMath filter or dynamically controlling filters and IDs inside the nested shortcode configuration.\u003C\u002Fp>\n\u003Cp>Because nested shortcodes are fully supported and the plugin respects all standard shortcode attributes, you can construct sophisticated, layered outputs without custom PHP. For example, you can build a front-end summary that uses one \u003Ccode>[gravops_search]\u003C\u002Fcode> to list matching entries, another to pull related entries, and a GravityMath shortcode to compute totals—all wrapped in your own HTML structure. GravityOps Search handles placeholder substitution and nested processing order so that each piece of your template receives the data it needs at the right time.\u003C\u002Fp>\n\u003Ch3>Search Operators and Multi-Input Fields\u003C\u002Fh3>\n\u003Cp>The \u003Ccode>operators\u003C\u002Fcode> attribute lets you tell GravityOps Search exactly how to compare each search value against its corresponding field or property. You define a comma-separated list of operators that line up with the IDs in the \u003Ccode>search\u003C\u002Fcode> attribute. Supported operators include equality (\u003Ccode>=\u003C\u002Fcode> or \u003Ccode>is\u003C\u002Fcode>), inequality (\u003Ccode>!=\u003C\u002Fcode>, \u003Ccode>isnot\u003C\u002Fcode>, \u003Ccode>is not\u003C\u002Fcode>), partial matches (\u003Ccode>contains\u003C\u002Fcode>), SQL-style wildcard matches (\u003Ccode>like\u003C\u002Fcode>), membership tests (\u003Ccode>in\u003C\u002Fcode>, \u003Ccode>not in\u003C\u002Fcode>), and numeric comparisons (\u003Ccode>gt\u003C\u002Fcode>, \u003Ccode>lt\u003C\u002Fcode>, \u003Ccode>gt=\u003C\u002Fcode>, \u003Ccode>lt=\u003C\u002Fcode>). If you provide fewer operators than search fields, remaining fields default to exact matches; extra operators beyond the number of fields are ignored. When you omit \u003Ccode>operators\u003C\u002Fcode> entirely, all fields use exact matching by default.\u003C\u002Fp>\n\u003Cp>For more advanced scenarios, certain operators expect specific value formats. When using \u003Ccode>in\u003C\u002Fcode> or \u003Ccode>not in\u003C\u002Fcode>, for example, you can pass a PHP-style array in the shortcode content—such as \u003Ccode>array(\\'item one\\',\\'item two\\',\\'item three\\')\u003C\u002Fcode>—to test whether the field value appears in that list. This makes it easy to filter entries against multiple acceptable values for a single field without duplicating field IDs. Combined with \u003Ccode>search_mode\u003C\u002Fcode>, you can express a wide range of conditions: from strict multi-field comparisons to flexible multi-value lists and keyword-style filters.\u003C\u002Fp>\n\u003Cp>Multi-input Gravity Forms fields (like Name, Address, and Checkbox fields) are fully supported, but they behave differently for display versus search. When displaying, using the base field ID in a placeholder (e.g., \u003Ccode>{13}\u003C\u002Fcode>) automatically combines all sub-inputs (such as first name and last name) into a single string separated by spaces. If you need to display a specific sub-input—like first name only—you can use its input ID directly, for example \u003Ccode>{13.3}\u003C\u002Fcode>. When searching, checkboxes are best handled by searching the base field ID so that changes to individual options or dynamic checkboxes do not break the search. Other multi-input fields (like Name and Address) should be searched using their individual input IDs (e.g., \u003Ccode>13.3\u003C\u002Fcode>, \u003Ccode>13.6\u003C\u002Fcode>), as searching by the base ID will not work for those types.\u003C\u002Fp>\n\u003Ch3>Performance and Access Control\u003C\u002Fh3>\n\u003Cp>Every \u003Ccode>[gravops_search]\u003C\u002Fcode> shortcode runs a live database query against Gravity Forms entries, so thoughtful usage is important for both performance and privacy. On the performance side, heavy use of \u003Ccode>limit=\\\"all\\\"\u003C\u002Fcode>, many nested shortcodes, and large forms with complex conditions can slow down page loads. To keep pages responsive, it is recommended to set a reasonable \u003Ccode>limit\u003C\u002Fcode> where possible, minimize unnecessary nesting, and consider caching the rendered page output using your preferred caching plugin or server-level caching tools. These simple steps help ensure that even data-heavy views remain fast and reliable.\u003C\u002Fp>\n\u003Cp>On the access-control side, the shortcode does not enforce any special permission checks by itself. Anyone who can view the page where the shortcode is placed will be able to see whatever Gravity Forms entry data you choose to display, including potentially sensitive information. To protect private or restricted data, you should place the shortcode inside pages or templates that are protected by membership plugins, password protection, role-based visibility, or other gating mechanisms. This keeps the plugin flexible and focused on data retrieval and formatting, while allowing you to decide how and where to expose entry data based on your site’s security model.\u003C\u002Fp>\n\u003Cp>GravityOps Search is designed to be both powerful and predictable: you define the forms, fields, filters, and display template, and the plugin takes care of querying and rendering. Used thoughtfully, it becomes a core tool for building dynamic, entry-driven front-end experiences on top of Gravity Forms, without custom development or complex integrations.\u003C\u002Fp>\n","Search Gravity Forms entries on the front end and display matching results anywhere. Filter by any field value. Output custom formatted data.",566,"2026-02-19T14:39:00.000Z","6.5","8.0",[112,113,114,24,115],"display-form-entries","form-data-lookup","frontend-entry-search","shortcode-results-display","https:\u002F\u002Fbrightleafdigital.io\u002Fgravityops-search\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgravityops-search.1.0.6.1.zip",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":28,"downloaded":126,"rating":28,"num_ratings":28,"last_updated":127,"tested_up_to":50,"requires_at_least":71,"requires_php":18,"tags":128,"homepage":18,"download_link":132,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":133},"rt-webhook-for-gravity-forms","RT Webhook for Gravity Forms","2.0.0","raintech357","https:\u002F\u002Fprofiles.wordpress.org\u002Fraintech357\u002F","\u003Cp>\u003Cstrong>RT Webhook for Gravity Forms\u003C\u002Fstrong> allows you to send form submission data to any external URL or service (like Zapier, Make.com, or your own custom API) with granular control.\u003C\u002Fp>\n\u003Ch3>Advanced Features:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Multiple Webhooks\u003C\u002Fstrong>: Assign multiple webhooks to a single form.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Dynamic Field Mapping\u003C\u002Fstrong>: Select Gravity Forms fields from a dropdown and map them to custom JSON keys.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Conditional Logic\u003C\u002Fstrong>: Trigger webhooks only when specific field values match your criteria.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom HTTP Headers\u003C\u002Fstrong>: Add authorization tokens or other custom headers (e.g., Bearer tokens).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logging System\u003C\u002Fstrong>: Keep track of the last 10 webhook requests with full URLs, headers, payloads, and server responses.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Support for Multiple Methods\u003C\u002Fstrong>: Use POST, GET, or PUT requests.\u003C\u002Fli>\n\u003C\u002Ful>\n","An advanced webhook integration for Gravity Forms with field mapping, conditional logic, and custom headers.",163,"2026-02-13T15:21:00.000Z",[24,129,130,131,57],"integration","json","webhook","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frt-webhook-for-gravity-forms.zip","2026-04-06T09:54:40.288Z",{"attackSurface":135,"codeSignals":214,"taintFlows":222,"riskAssessment":223,"analyzedAt":230},{"hooks":136,"ajaxHandlers":210,"restRoutes":211,"shortcodes":212,"cronEvents":213,"entryPointCount":28,"unprotectedCount":28},[137,143,147,152,157,162,166,171,174,179,181,183,186,190,194,199,203,207],{"type":138,"name":139,"callback":140,"priority":88,"file":141,"line":142},"action","gform_field_advanced_settings","field_disable_autocomplete_settings","class-gf-disable-autocomplete.php",186,{"type":138,"name":144,"callback":145,"file":141,"line":146},"gform_editor_js","editor_script",187,{"type":148,"name":149,"callback":150,"file":141,"line":151},"filter","gform_tooltips","add_field_tooltip",188,{"type":148,"name":153,"callback":154,"priority":155,"file":141,"line":156},"gform_field_content","maybe_disable_autocomplete",15,191,{"type":148,"name":158,"callback":159,"priority":88,"file":160,"line":161},"gform_form_post_get_meta","get_form_meta","class-gf-field-helper-json.php",47,{"type":148,"name":163,"callback":164,"priority":88,"file":160,"line":165},"gform_post_update_form_meta","update_form_meta",48,{"type":148,"name":167,"callback":168,"priority":155,"file":169,"line":170},"gform_addon_feed_settings_fields","add_webhook_setting","class-gf-field-helper.php",174,{"type":148,"name":172,"callback":172,"priority":155,"file":169,"line":173},"gform_webhooks_request_data",175,{"type":138,"name":175,"callback":176,"priority":88,"file":177,"line":178},"gform_field_standard_settings","field_input_pattern_settings","class-gf-input-pattern.php",122,{"type":138,"name":144,"callback":145,"file":177,"line":180},123,{"type":148,"name":149,"callback":150,"file":177,"line":182},124,{"type":148,"name":153,"callback":184,"priority":155,"file":177,"line":185},"add_input_pattern",127,{"type":138,"name":187,"callback":188,"file":177,"line":189},"wp_enqueue_scripts","enqueue_assets",128,{"type":148,"name":191,"callback":192,"priority":88,"file":177,"line":193},"gform_field_validation","validate_input_pattern",131,{"type":138,"name":195,"callback":196,"priority":48,"file":197,"line":198},"gform_loaded","load_field_helper","field-helper-for-gravity-forms.php",38,{"type":138,"name":200,"callback":201,"file":197,"line":202},"rest_api_init","register_api_endpoint",39,{"type":138,"name":204,"callback":205,"file":197,"line":206},"admin_enqueue_scripts","register_backend_assets",79,{"type":138,"name":187,"callback":208,"file":197,"line":209},"register_frontend_assets",82,[],[],[],[],{"dangerousFunctions":215,"sqlUsage":216,"outputEscaping":218,"fileOperations":48,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":221},[],{"prepared":28,"raw":28,"locations":217},[],{"escaped":219,"rawEcho":28,"locations":220},55,[],[],[],{"summary":224,"deductions":225},"The static analysis of 'field-helper-for-gravity-forms' v1.10.6 reveals a generally strong security posture. The plugin exhibits excellent practices by utilizing prepared statements for all SQL queries and ensuring 100% of its output is properly escaped, significantly mitigating risks of SQL injection and cross-site scripting. The absence of any identified dangerous functions, external HTTP requests, or vulnerabilities in taint analysis further reinforces this positive assessment. The plugin also shows a clean vulnerability history with zero recorded CVEs, indicating a consistent focus on security by the developers.\n\nHowever, several areas warrant attention. The complete lack of nonce checks and capability checks across all identified entry points is a significant concern. While the current attack surface appears small (0 entry points), if any become exposed in future updates or through other means, they would be entirely unprotected, leaving the plugin vulnerable to unauthorized actions. The presence of file operations without explicit mention of sanitization also introduces a potential, albeit unconfirmed, risk. Despite these potential weaknesses, the plugin's current lack of known vulnerabilities and robust handling of SQL and output suggest a responsible development team.\n\nIn conclusion, 'field-helper-for-gravity-forms' v1.10.6 demonstrates a commendable commitment to secure coding fundamentals, particularly concerning database interactions and output sanitization. The clean vulnerability history is a significant positive. The primary risk lies in the complete absence of authentication and authorization checks on any potential entry points, which represents a critical oversight that could be exploited if the attack surface expands or if an indirect vulnerability exposes these points. Developers should prioritize implementing robust nonce and capability checks.",[226,228],{"reason":227,"points":88},"Missing nonce checks on entry points",{"reason":229,"points":88},"Missing capability checks on entry points","2026-04-16T11:09:27.798Z",{"wat":232,"direct":243},{"assetPaths":233,"generatorPatterns":237,"scriptPaths":238,"versionParams":239},[234,235,236],"\u002Fwp-content\u002Fplugins\u002Ffield-helper-for-gravity-forms\u002Fassets\u002Fjs\u002Fgravity-forms-field-helper-admin.js","\u002Fwp-content\u002Fplugins\u002Ffield-helper-for-gravity-forms\u002Fassets\u002Fjs\u002Fgravity-forms-field-helper.js","\u002Fwp-content\u002Fplugins\u002Ffield-helper-for-gravity-forms\u002Fassets\u002Fcss\u002Fgravity-forms-field-helper.css",[],[234,235],[240,241,242],"field-helper-for-gravity-forms\u002Fassets\u002Fjs\u002Fgravity-forms-field-helper-admin.js?ver=","field-helper-for-gravity-forms\u002Fassets\u002Fjs\u002Fgravity-forms-field-helper.js?ver=","field-helper-for-gravity-forms\u002Fassets\u002Fcss\u002Fgravity-forms-field-helper.css?ver=",{"cssClasses":244,"htmlComments":245,"htmlAttributes":246,"restEndpoints":247,"jsGlobals":249,"shortcodeOutput":250},[],[],[],[248],"\u002Fwp-json\u002Fgravityformsfieldhelper\u002Fv1",[],[],{"error":252,"url":253,"statusCode":254,"statusMessage":255,"message":255},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Ffield-helper-for-gravity-forms\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":257,"versions":258},33,[259,265,272,279,286,293,300,307,314,321,328,335,342,349,356,363,370,377,384,391,398,405,412,419,426,433,440,447,454,461,468,475,482],{"version":6,"download_url":26,"svn_tag_url":260,"released_at":29,"has_diff":261,"diff_files_changed":262,"diff_lines":29,"trac_diff_url":263,"vulnerabilities":264,"is_current":252},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.10.6\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.5&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.6",[],{"version":266,"download_url":267,"svn_tag_url":268,"released_at":29,"has_diff":261,"diff_files_changed":269,"diff_lines":29,"trac_diff_url":270,"vulnerabilities":271,"is_current":261},"1.10.5","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.10.5.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.10.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.4&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.5",[],{"version":273,"download_url":274,"svn_tag_url":275,"released_at":29,"has_diff":261,"diff_files_changed":276,"diff_lines":29,"trac_diff_url":277,"vulnerabilities":278,"is_current":261},"1.10.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.10.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.10.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.3&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.4",[],{"version":280,"download_url":281,"svn_tag_url":282,"released_at":29,"has_diff":261,"diff_files_changed":283,"diff_lines":29,"trac_diff_url":284,"vulnerabilities":285,"is_current":261},"1.10.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.10.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.10.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.2&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.3",[],{"version":287,"download_url":288,"svn_tag_url":289,"released_at":29,"has_diff":261,"diff_files_changed":290,"diff_lines":29,"trac_diff_url":291,"vulnerabilities":292,"is_current":261},"1.10.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.10.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.10.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.1&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.2",[],{"version":294,"download_url":295,"svn_tag_url":296,"released_at":29,"has_diff":261,"diff_files_changed":297,"diff_lines":29,"trac_diff_url":298,"vulnerabilities":299,"is_current":261},"1.10.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.10.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.10.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.1",[],{"version":301,"download_url":302,"svn_tag_url":303,"released_at":29,"has_diff":261,"diff_files_changed":304,"diff_lines":29,"trac_diff_url":305,"vulnerabilities":306,"is_current":261},"1.10.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.10.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.10.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.7&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.10.0",[],{"version":308,"download_url":309,"svn_tag_url":310,"released_at":29,"has_diff":261,"diff_files_changed":311,"diff_lines":29,"trac_diff_url":312,"vulnerabilities":313,"is_current":261},"1.9.7","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.7.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.7\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.6&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.7",[],{"version":315,"download_url":316,"svn_tag_url":317,"released_at":29,"has_diff":261,"diff_files_changed":318,"diff_lines":29,"trac_diff_url":319,"vulnerabilities":320,"is_current":261},"1.9.6","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.6.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.6\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.5&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.6",[],{"version":322,"download_url":323,"svn_tag_url":324,"released_at":29,"has_diff":261,"diff_files_changed":325,"diff_lines":29,"trac_diff_url":326,"vulnerabilities":327,"is_current":261},"1.9.5","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.5.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.4&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.5",[],{"version":329,"download_url":330,"svn_tag_url":331,"released_at":29,"has_diff":261,"diff_files_changed":332,"diff_lines":29,"trac_diff_url":333,"vulnerabilities":334,"is_current":261},"1.9.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.3&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.4",[],{"version":336,"download_url":337,"svn_tag_url":338,"released_at":29,"has_diff":261,"diff_files_changed":339,"diff_lines":29,"trac_diff_url":340,"vulnerabilities":341,"is_current":261},"1.9.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.2&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.3",[],{"version":343,"download_url":344,"svn_tag_url":345,"released_at":29,"has_diff":261,"diff_files_changed":346,"diff_lines":29,"trac_diff_url":347,"vulnerabilities":348,"is_current":261},"1.9.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.1&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.2",[],{"version":350,"download_url":351,"svn_tag_url":352,"released_at":29,"has_diff":261,"diff_files_changed":353,"diff_lines":29,"trac_diff_url":354,"vulnerabilities":355,"is_current":261},"1.9.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.1",[],{"version":357,"download_url":358,"svn_tag_url":359,"released_at":29,"has_diff":261,"diff_files_changed":360,"diff_lines":29,"trac_diff_url":361,"vulnerabilities":362,"is_current":261},"1.9.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.9.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.9.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.8.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.9.0",[],{"version":364,"download_url":365,"svn_tag_url":366,"released_at":29,"has_diff":261,"diff_files_changed":367,"diff_lines":29,"trac_diff_url":368,"vulnerabilities":369,"is_current":261},"1.8.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.8.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.8.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.7.1&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.8.0",[],{"version":371,"download_url":372,"svn_tag_url":373,"released_at":29,"has_diff":261,"diff_files_changed":374,"diff_lines":29,"trac_diff_url":375,"vulnerabilities":376,"is_current":261},"1.7.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.7.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.7.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.7.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.7.1",[],{"version":378,"download_url":379,"svn_tag_url":380,"released_at":29,"has_diff":261,"diff_files_changed":381,"diff_lines":29,"trac_diff_url":382,"vulnerabilities":383,"is_current":261},"1.7.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.7.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.7.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.6.1&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.7.0",[],{"version":385,"download_url":386,"svn_tag_url":387,"released_at":29,"has_diff":261,"diff_files_changed":388,"diff_lines":29,"trac_diff_url":389,"vulnerabilities":390,"is_current":261},"1.6.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.6.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.6.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.6.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.6.1",[],{"version":392,"download_url":393,"svn_tag_url":394,"released_at":29,"has_diff":261,"diff_files_changed":395,"diff_lines":29,"trac_diff_url":396,"vulnerabilities":397,"is_current":261},"1.6.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.6.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.6.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.5.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.6.0",[],{"version":399,"download_url":400,"svn_tag_url":401,"released_at":29,"has_diff":261,"diff_files_changed":402,"diff_lines":29,"trac_diff_url":403,"vulnerabilities":404,"is_current":261},"1.5.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.5.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.5.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.5&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.5.0",[],{"version":406,"download_url":407,"svn_tag_url":408,"released_at":29,"has_diff":261,"diff_files_changed":409,"diff_lines":29,"trac_diff_url":410,"vulnerabilities":411,"is_current":261},"1.4.5","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.4.5.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.4.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.4&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.5",[],{"version":413,"download_url":414,"svn_tag_url":415,"released_at":29,"has_diff":261,"diff_files_changed":416,"diff_lines":29,"trac_diff_url":417,"vulnerabilities":418,"is_current":261},"1.4.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.4.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.4.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.3&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.4",[],{"version":420,"download_url":421,"svn_tag_url":422,"released_at":29,"has_diff":261,"diff_files_changed":423,"diff_lines":29,"trac_diff_url":424,"vulnerabilities":425,"is_current":261},"1.4.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.4.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.4.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.2&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.3",[],{"version":427,"download_url":428,"svn_tag_url":429,"released_at":29,"has_diff":261,"diff_files_changed":430,"diff_lines":29,"trac_diff_url":431,"vulnerabilities":432,"is_current":261},"1.4.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.4.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.4.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.1&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.2",[],{"version":434,"download_url":435,"svn_tag_url":436,"released_at":29,"has_diff":261,"diff_files_changed":437,"diff_lines":29,"trac_diff_url":438,"vulnerabilities":439,"is_current":261},"1.4.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.4.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.4.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.1",[],{"version":441,"download_url":442,"svn_tag_url":443,"released_at":29,"has_diff":261,"diff_files_changed":444,"diff_lines":29,"trac_diff_url":445,"vulnerabilities":446,"is_current":261},"1.4.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.4.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.4.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.3.1&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.4.0",[],{"version":448,"download_url":449,"svn_tag_url":450,"released_at":29,"has_diff":261,"diff_files_changed":451,"diff_lines":29,"trac_diff_url":452,"vulnerabilities":453,"is_current":261},"1.3.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.3.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.3.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.3.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.3.1",[],{"version":455,"download_url":456,"svn_tag_url":457,"released_at":29,"has_diff":261,"diff_files_changed":458,"diff_lines":29,"trac_diff_url":459,"vulnerabilities":460,"is_current":261},"1.3.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.3.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.3.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.2.2&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.3.0",[],{"version":462,"download_url":463,"svn_tag_url":464,"released_at":29,"has_diff":261,"diff_files_changed":465,"diff_lines":29,"trac_diff_url":466,"vulnerabilities":467,"is_current":261},"1.2.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.2.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.2.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.2.1&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.2.2",[],{"version":469,"download_url":470,"svn_tag_url":471,"released_at":29,"has_diff":261,"diff_files_changed":472,"diff_lines":29,"trac_diff_url":473,"vulnerabilities":474,"is_current":261},"1.2.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.2.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.2.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.2.0&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.2.1",[],{"version":476,"download_url":477,"svn_tag_url":478,"released_at":29,"has_diff":261,"diff_files_changed":479,"diff_lines":29,"trac_diff_url":480,"vulnerabilities":481,"is_current":261},"1.2.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.2.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.2.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.1.2&new_path=%2Ffield-helper-for-gravity-forms%2Ftags%2F1.2.0",[],{"version":483,"download_url":484,"svn_tag_url":485,"released_at":29,"has_diff":261,"diff_files_changed":486,"diff_lines":29,"trac_diff_url":29,"vulnerabilities":487,"is_current":261},"1.1.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffield-helper-for-gravity-forms.1.1.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffield-helper-for-gravity-forms\u002Ftags\u002F1.1.2\u002F",[],[]]