Vulnerability Database · Go · Package report
github.com/ajg/form: vulnerability history, versions and safety
github.com/ajg/form is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/ajg/form v1.9.0 i
Updated on 23 Oct 2026
Good news: v1.9.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Moderate
What to do: Stay on v1.9.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.9.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.9.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 267 i
- OpenSSF scorecard 7/10 i
- Last release 3 months ago i
- Licence BSD-3-Clause i
Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for github.com/ajg/form, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- v1.9.1-0.20260807142816-b7b6d853b072 07 Aug 2026
- v1.9.1-0.20260724043635-b7f9bbd98a3d 24 Jul 2026
- v1.9.0 22 Jul 2026
- v1.8.1-0.20260719163956-a8630733309e 19 Jul 2026
- v1.8.1-0.20260716202156-5d322a52cc7f 16 Jul 2026
- v1.8.0 16 Jul 2026
- v1.7.3 13 Jul 2026
- v1.7.2 10 Jul 2026
- v0.0.0-20260218163003-20113a652bfa 18 Feb 2026
- v1.7.1 18 Feb 2026
- v1.7.0 17 Feb 2026
- v1.6.1 01 Feb 2026
- v0.0.0-20200323032839-9aeb3cf462e1 23 Mar 2020
- v1.5.2-0.20200323032839-9aeb3cf462e1 23 Mar 2020
- v1.5.2-0.20190422112121-771248efc1bb 22 Apr 2019
- v1.5.2-0.20190319000757-520624201564 19 Mar 2019
- v1.5.2-0.20190319000757-8eb9552b0310 19 Mar 2019
- v1.5.2-0.20190319000757-b5b94d9b7e1a 19 Mar 2019
- v0.0.0-20190318234958-5c4e22684113 18 Mar 2019
- v1.5.1 18 Mar 2019
- v0.0.0-20170718044755-5f6a2d96b23d 18 Jul 2017
- v0.0.0-20160822230020-523a5da1a92f 22 Aug 2016
- v0.0.0-20160802194845-cc2954064ec9 02 Aug 2016
- v0.0.0-20160802194107-0eaefc0dcc4d 02 Aug 2016
- v0.0.0-20160629214312-7ff89c758087 29 Jun 2016
- v0.0.0-20160628212924-3f3ee6b4a67d 28 Jun 2016
- v0.0.0-20160429221517-e7b99d6ea9c5 29 Apr 2016
- v0.0.0-20160429220236-01bc61fac8fe 29 Apr 2016
- v0.0.0-20160324211255-8cdb333b048c 24 Mar 2016
- v0.0.0-20150423191938-c9e1c3ae1f86 23 Apr 2015
- v0.0.0-20150423190634-3d986e16ddb0 23 Apr 2015
- v0.0.0-20150423190634-df2dcded7bae 23 Apr 2015
- v0.0.0-20150225033556-9b296c61c1ea 25 Feb 2015
- v0.0.0-20150211013154-c897840d3ff5 11 Feb 2015
- v0.0.0-20141120234531-5d852b2c0360 20 Nov 2014
- v0.0.0-20141119191055-e3edb42649de 19 Nov 2014
- v0.0.0-20140819195441-51f3dea6c738 19 Aug 2014
- v0.0.0-20140818170714-0cd9765547e2 18 Aug 2014
- v0.0.0-20140204163656-9c3654654bd9 04 Feb 2014
- v0.0.0-20140127190532-c143a81ec0e3 27 Jan 2014
- v0.0.0-20140124212735-1774537a31b4 24 Jan 2014
- v0.0.0-20140122211533-0992bb45bb97 22 Jan 2014
- v0.0.0-20140120181231-91b7d16455c1 20 Jan 2014
- v0.0.0-20140119045145-9df600add323 19 Jan 2014
- v0.0.0-20140117171952-8a01172aa36d 17 Jan 2014
- v0.0.0-20140116105558-182b6d3839ad 16 Jan 2014
- v0.0.0-20140115194046-0daa018f71f5 15 Jan 2014
- v0.0.0-20140115014902-319705683a56 15 Jan 2014
All 48 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for github.com/ajg/form
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About github.com/ajg/form
Is github.com/ajg/form safe to use?
Vulert has no vulnerabilities on record for github.com/ajg/form in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is github.com/ajg/form's Vulert package health score?
Vulert scores github.com/ajg/form 80/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of github.com/ajg/form affected?
No. v1.9.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of github.com/ajg/form should I use?
v1.9.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does github.com/ajg/form have?
0 vulnerabilities are recorded for github.com/ajg/form in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new github.com/ajg/form vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ajg/form in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of github.com/ajg/form are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor github.com/ajg/form for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ajg/form version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.