Vulnerability Database · Go · Package report
github.com/juju/collections: vulnerability history, versions and safety
github.com/juju/collections 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/collections v1.0.4 i
Updated on 23 Oct 2026
Good news: v1.0.4, 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.0.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 3 i
- OpenSSF scorecard 2/10 i
- Last release 40 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/collections, 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-20240131020636-9dad3fcb4231 31 Jan 2024
- v1.0.5-0.20240131020636-9dad3fcb4231 31 Jan 2024
- v1.0.4-0.20240131020228-0fc0d2c412e5 31 Jan 2024
- v1.0.4 02 Jun 2023
- v1.0.4-0.20230602041413-5163edc56d22 02 Jun 2023
- v1.0.3 01 Jun 2023
- v1.0.3-0.20230601034730-a937262d7a61 01 Jun 2023
- v1.0.2 20 Jan 2023
- v1.0.1 29 Nov 2022
- v0.0.0-20220203020748-febd7cad8a7a 03 Feb 2022
- v1.0.0 03 Feb 2022
- v0.0.0-20200605021417-0d0ec82b7271 05 Jun 2020
- v0.0.0-20180717171555-9be91dc79b7c 17 Jul 2018
- v0.0.0-20180717171319-94aebf400610 17 Jul 2018
- v0.0.0-20180516022642-90152009b5f3 16 May 2018
- v0.0.0-20180515224113-78fe499598cd 15 May 2018
- v0.0.0-20180515203731-520e0549d51a 15 May 2018
All 17 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/collections
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/collections
Is github.com/juju/collections safe to use?
Vulert has no vulnerabilities on record for github.com/juju/collections 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/collections's Vulert package health score?
Vulert scores github.com/juju/collections 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/collections affected?
No. v1.0.4, 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/collections should I use?
v1.0.4 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/collections have?
0 vulnerabilities are recorded for github.com/juju/collections 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/collections vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/juju/collections 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/collections 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/collections for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/juju/collections version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.