Vulnerability Database · Go · Package report
github.com/bloom42/stdx-go: vulnerability history, versions and safety
github.com/bloom42/stdx-go 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/bloom42/stdx-go v0.0.0-20260115084611-ff53b61899a9 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260115084611-ff53b61899a9, 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.0-20260115084611-ff53b61899a9 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260115084611-ff53b61899a9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260115084611-ff53b61899a9 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 9 months ago i
- Licence MIT 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/bloom42/stdx-go, 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-20260115084611-ff53b61899a9 15 Jan 2026
- v0.0.0-20251227081323-ebd5b26e2bad 27 Dec 2025
- v0.0.0-20251216094135-aea7dc8102f5 16 Dec 2025
- v0.0.0-20251115120151-a7b97eb16586 15 Nov 2025
- v0.0.0-20251021083538-fa232b97572c 21 Oct 2025
- v0.0.0-20250811085142-4b987334962f 11 Aug 2025
- v0.0.0-20250803150454-38313289a3c9 03 Aug 2025
- v0.0.0-20250724072927-e18034748d95 24 Jul 2025
- v0.0.0-20250714062210-c928241917d6 14 Jul 2025
- v0.0.0-20250706084935-56d77a91e7d7 06 Jul 2025
- v0.0.0-20250630064620-a4346a303bad 30 Jun 2025
- v0.0.0-20250624083055-0833b49f1030 24 Jun 2025
- v0.0.0-20250613170246-c1892dcc8e84 13 Jun 2025
- v0.0.0-20250611174549-1f2fcb0db8f2 11 Jun 2025
- v0.0.0-20250604081759-1cd365121388 04 Jun 2025
- v0.0.0-20250520181623-3523a8e39dbe 20 May 2025
- v0.0.0-20250520071234-9d909ad16426 20 May 2025
- v0.0.0-20250520065532-5c0b01a23fcc 20 May 2025
- v0.0.0-20250516091535-64712a368191 16 May 2025
- v0.0.0-20250513111747-5836b2c7b650 13 May 2025
- v0.0.0-20250512095731-2cf6355b4966 12 May 2025
- v0.0.0-20250512085851-b56052e1e14a 12 May 2025
All 22 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/bloom42/stdx-go
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/bloom42/stdx-go
Is github.com/bloom42/stdx-go safe to use?
Vulert has no vulnerabilities on record for github.com/bloom42/stdx-go 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/bloom42/stdx-go's Vulert package health score?
Vulert scores github.com/bloom42/stdx-go 70/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/bloom42/stdx-go affected?
No. v0.0.0-20260115084611-ff53b61899a9, 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/bloom42/stdx-go should I use?
v0.0.0-20260115084611-ff53b61899a9 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/bloom42/stdx-go have?
0 vulnerabilities are recorded for github.com/bloom42/stdx-go 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/bloom42/stdx-go vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/bloom42/stdx-go 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/bloom42/stdx-go 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/bloom42/stdx-go for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/bloom42/stdx-go version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.