Vulnerability Database · Go · Package report
github.com/juju/schema: vulnerability history, versions and safety
github.com/juju/schema 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/juju/schema v1.2.0 i
Updated on 23 Oct 2026
Good news: v1.2.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 6 i
- OpenSSF scorecard 2/10 i
- Last release 35 months ago i
- Licence LGPL-3.0 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/juju/schema, 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.
- v0.0.0-20231102095835-41e08deedca9 02 Nov 2023
- v1.0.2-0.20231102095835-41e08deedca9 02 Nov 2023
- v1.2.0 02 Nov 2023
- v1.0.1 27 Oct 2021
- v1.0.1-0.20211027175539-303a2da57660 27 Oct 2021
- v1.0.1-0.20211026143153-6c7c9df27d96 26 Oct 2021
- v1.0.1-0.20211025114208-632f431af0cf 25 Oct 2021
- v0.0.0-20190814234152-1f8aaeef0989 14 Aug 2019
- v1.0.1-0.20190814234152-1f8aaeef0989 14 Aug 2019
- v1.0.0 05 Apr 2019
- v0.0.0-20181210140654-64a6158e9071 10 Dec 2018
- v0.0.0-20181206204705-fbadcc54c3aa 06 Dec 2018
- v0.0.0-20180109041850-e4f08199aa80 09 Jan 2018
- v0.0.0-20160916142850-e4e05803c9a1 16 Sep 2016
- v0.0.0-20160822131148-29dd021fc4b6 22 Aug 2016
- v0.0.0-20160420044203-075de04f9b7d 20 Apr 2016
- v0.0.0-20160301111646-1e25943f8c6f 01 Mar 2016
- v0.0.0-20160119211926-47d9b102199f 19 Jan 2016
- v0.0.0-20150807075808-afe1151cb49d 07 Aug 2015
- v0.0.0-20150616195211-5fef1eb09944 16 Jun 2015
- v0.0.0-20150602101902-e32c2dd75b90 02 Jun 2015
- v0.0.0-20150330011223-1c4e902df91b 30 Mar 2015
- v0.0.0-20140723042318-27a52be50766 23 Jul 2014
- v0.0.0-20140716041130-de545dbe6bec 16 Jul 2014
- v0.0.0-20140605095908-1887e824896b 05 Jun 2014
All 25 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.
03 Vulnerabilities
Recorded vulnerabilities for github.com/juju/schema
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/juju/schema
Is github.com/juju/schema safe to use?
Vulert has no vulnerabilities on record for github.com/juju/schema 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/juju/schema's Vulert package health score?
Vulert scores github.com/juju/schema 50/100, which reads as usable, but worth attention. 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/juju/schema affected?
No. v1.2.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/juju/schema should I use?
v1.2.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/juju/schema have?
0 vulnerabilities are recorded for github.com/juju/schema 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/juju/schema vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/juju/schema 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/juju/schema 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/juju/schema for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/juju/schema version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.