Vulnerability Database · Go · Package report
github.com/anacrolix/stm: vulnerability history, versions and safety
github.com/anacrolix/stm 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/anacrolix/stm v0.6.0 i
Updated on 23 Oct 2026
Good news: v0.6.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.6.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.6.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.6.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 92 i
- OpenSSF scorecard 3/10 i
- Last release 2 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/anacrolix/stm, 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.6.0 17 Aug 2026
- v0.0.0-20221221010108-32174bfc2d87 21 Dec 2022
- v0.4.2-0.20221221010108-32174bfc2d87 21 Dec 2022
- v0.5.0 21 Dec 2022
- v0.4.1-0.20221221005312-96d17df0e496 21 Dec 2022
- v0.4.1 06 Nov 2022
- v0.4.1-0.20221028032313-47dd0d0a98b6 28 Oct 2022
- v0.4.1-0.20221026225348-33b8a9d5dc0c 26 Oct 2022
- v0.4.1-0.20221026013506-f0e9444c8b25 26 Oct 2022
- v0.4.0 13 Jun 2022
- v0.3.1-0.20220608092604-002dedc9d095 08 Jun 2022
- v0.3.1-0.20220608090244-8d82a394042f 08 Jun 2022
- v0.3.1-0.20220608041330-477a1bc9d25f 08 Jun 2022
- v0.2.1-0.20210927023051-8a06827bbcce 27 Sep 2021
- v0.4.0-alpha.0 27 Sep 2021
- v0.3.0 24 Aug 2021
- v0.2.1-0.20210311004623-bccbd0ef92dc 11 Mar 2021
- v0.3.0-alpha 11 Mar 2021
- v0.2.1-0.20210311004443-2833ddd71309 11 Mar 2021
- v0.2.1-0.20210310231625-45c211559de6 10 Mar 2021
- v0.2.1-0.20201002073511-c35a2c748c6a 02 Oct 2020
- v0.2.1-0.20201002073320-877bf18b7e26 02 Oct 2020
- v0.2.1-0.20201001032701-196642dc25c4 01 Oct 2020
- v0.2.1-0.20200930081244-47e5cc608cde 30 Sep 2020
- v0.2.1-0.20200923014750-e0a706da27a7 23 Sep 2020
- v0.2.1-0.20200909235703-5df0d3b6be09 09 Sep 2020
- v0.2.1-0.20200909232235-2a64b89bdbc8 09 Sep 2020
- v0.2.1-0.20200909232235-d6711ea6dec3 09 Sep 2020
- v0.2.1-0.20200827230803-148eb2291953 27 Aug 2020
- v0.2.1-0.20200415073325-8ddce5e3df43 15 Apr 2020
- v0.2.0 06 Nov 2019
- v0.1.1-0.20191106051447-e749ba3531cf 06 Nov 2019
- v0.1.1-0.20191106035153-858a09c9c68b 06 Nov 2019
- v0.1.1-0.20191105075537-443c0b33d649 05 Nov 2019
- v0.1.1-0.20191104055207-1b68eff1b3d8 04 Nov 2019
- v0.1.0 03 Nov 2019
- v0.0.0-20160330223310-04af6bdd6eb3 30 Mar 2016
All 37 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/anacrolix/stm
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/anacrolix/stm
Is github.com/anacrolix/stm safe to use?
Vulert has no vulnerabilities on record for github.com/anacrolix/stm 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/anacrolix/stm's Vulert package health score?
Vulert scores github.com/anacrolix/stm 72/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/anacrolix/stm affected?
No. v0.6.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/anacrolix/stm should I use?
v0.6.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/anacrolix/stm have?
0 vulnerabilities are recorded for github.com/anacrolix/stm 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/anacrolix/stm vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/anacrolix/stm 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/anacrolix/stm 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/anacrolix/stm for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/anacrolix/stm version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.