Vulnerability Database · Go · Package report
github.com/spiffe/aws-spiffe-workload-helper: vulnerability history, versions and safety
github.com/spiffe/aws-spiffe-workload-helper 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.
See all github.com/spiffe/aws-spiffe-workload-helper vulnerabilities
Vulert verdict on github.com/spiffe/aws-spiffe-workload-helper v0.0.7 i
Updated on 23 Oct 2026
Good news: v0.0.7, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.7 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.7 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 16 i
- Last release this month i
- Licence Apache-2.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/spiffe/aws-spiffe-workload-helper, 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.7 20 Oct 2026
- v0.0.6 01 Oct 2026
- v0.0.6-0.20260401111059-a8ba7513444b 01 Apr 2026
- v0.0.5 16 Feb 2026
- v0.0.4 23 Jul 2025
- v0.0.3 16 Jun 2025
- v0.0.3-0.20250606134952-fc551f8daee4 06 Jun 2025
- v0.0.2 05 Jun 2025
- v0.0.1-rc.8 21 Feb 2025
- v0.0.1-rc.7 05 Feb 2025
- v0.0.1-rc.6 18 Dec 2024
- v0.0.1-rc.4.0.20241202110739-745798d66a1c 02 Dec 2024
- v0.0.1-rc.5 02 Dec 2024
- v0.0.1-rc.4.0.20241128165815-7e51c8a2da24 28 Nov 2024
- v0.0.1-rc.3.0.20241128104512-f037a833555f 28 Nov 2024
- v0.0.1-rc.4 28 Nov 2024
- v0.0.1-rc.2.0.20241029164951-6d5d403745f6 29 Oct 2024
- v0.0.1-rc.3 29 Oct 2024
- v0.0.1-rc.2.0.20241023100944-a49aa99e23ac 23 Oct 2024
- v0.0.1-rc.2 23 Oct 2024
- v0.0.1-rc.0.0.20241023092424-04cce1f972a5 23 Oct 2024
- v0.0.1-rc.1 23 Oct 2024
- v0.0.0-20241023091941-86f6271dcb50 23 Oct 2024
- v0.0.1-rc.0 23 Oct 2024
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.7 | 20 Oct 2026 | none | Apache-2.0 | — | Details → |
| v0.0.6 | 01 Oct 2026 | none | Apache-2.0 | — | Details → |
| v0.0.6-0.20260401111059-a8ba7513444b | 01 Apr 2026 | none | Apache-2.0 | — | Details → |
| v0.0.5 | 16 Feb 2026 | none | Apache-2.0 | — | Details → |
| v0.0.4 | 23 Jul 2025 | none | Apache-2.0 | — | Details → |
| v0.0.3 | 16 Jun 2025 | none | Apache-2.0 | — | Details → |
| v0.0.3-0.20250606134952-fc551f8daee4 | 06 Jun 2025 | none | Apache-2.0 | — | Details → |
| v0.0.2 | 05 Jun 2025 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.8 | 21 Feb 2025 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.7 | 05 Feb 2025 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.6 | 18 Dec 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.4.0.20241202110739-745798d66a1c | 02 Dec 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.5 | 02 Dec 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.4.0.20241128165815-7e51c8a2da24 | 28 Nov 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.3.0.20241128104512-f037a833555f | 28 Nov 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.4 | 28 Nov 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.2.0.20241029164951-6d5d403745f6 | 29 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.3 | 29 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.2.0.20241023100944-a49aa99e23ac | 23 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.2 | 23 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.0.0.20241023092424-04cce1f972a5 | 23 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.1 | 23 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.0-20241023091941-86f6271dcb50 | 23 Oct 2024 | none | Apache-2.0 | — | Details → |
| v0.0.1-rc.0 | 23 Oct 2024 | none | Apache-2.0 | — | Details → |
All 24 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/spiffe/aws-spiffe-workload-helper
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/spiffe/aws-spiffe-workload-helper
Is github.com/spiffe/aws-spiffe-workload-helper safe to use?
Vulert has no vulnerabilities on record for github.com/spiffe/aws-spiffe-workload-helper 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/spiffe/aws-spiffe-workload-helper's Vulert package health score?
Vulert scores github.com/spiffe/aws-spiffe-workload-helper 74/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/spiffe/aws-spiffe-workload-helper affected?
No. v0.0.7, 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.
How many vulnerabilities does github.com/spiffe/aws-spiffe-workload-helper have?
0 vulnerabilities are recorded for github.com/spiffe/aws-spiffe-workload-helper 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/spiffe/aws-spiffe-workload-helper vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/spiffe/aws-spiffe-workload-helper 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/spiffe/aws-spiffe-workload-helper 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/spiffe/aws-spiffe-workload-helper for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/spiffe/aws-spiffe-workload-helper version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.