Vulnerability Database · Go · Package report
github.com/adams-sarah/test2doc: vulnerability history, versions and safety
github.com/adams-sarah/test2doc 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/adams-sarah/test2doc v0.0.0-20211124171229-79cd42e7411d i
Updated on 23 Oct 2026
Good news: v0.0.0-20211124171229-79cd42e7411d, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20211124171229-79cd42e7411d or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20211124171229-79cd42e7411d too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20211124171229-79cd42e7411d — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 335 i
- OpenSSF scorecard 1/10 i
- Last release 58 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/adams-sarah/test2doc, 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-20211124171229-79cd42e7411d 24 Nov 2021
- v0.0.0-20210514182215-2580a24111e5 14 May 2021
- v0.0.0-20180225015401-dfbef56b3eab 25 Feb 2018
- v0.0.0-20171120213140-c7ff98656171 20 Nov 2017
- v0.0.0-20170919182239-35497a3ca876 19 Sep 2017
- v0.0.0-20170305224440-da8da9088830 05 Mar 2017
- v0.0.0-20150615064854-373a18f73dfe 15 Jun 2015
- v0.0.0-20150606040653-27a070481e71 06 Jun 2015
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20211124171229-79cd42e7411d | 24 Nov 2021 | none | MIT | — | Details → |
| v0.0.0-20210514182215-2580a24111e5 | 14 May 2021 | none | MIT | — | Details → |
| v0.0.0-20180225015401-dfbef56b3eab | 25 Feb 2018 | none | MIT | — | Details → |
| v0.0.0-20171120213140-c7ff98656171 | 20 Nov 2017 | none | MIT | — | Details → |
| v0.0.0-20170919182239-35497a3ca876 | 19 Sep 2017 | none | MIT | — | Details → |
| v0.0.0-20170305224440-da8da9088830 | 05 Mar 2017 | none | MIT | — | Details → |
| v0.0.0-20150615064854-373a18f73dfe | 15 Jun 2015 | none | MIT | — | Details → |
| v0.0.0-20150606040653-27a070481e71 | 06 Jun 2015 | none | MIT | — | Details → |
All 8 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/adams-sarah/test2doc
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/adams-sarah/test2doc
Is github.com/adams-sarah/test2doc safe to use?
Vulert has no vulnerabilities on record for github.com/adams-sarah/test2doc 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/adams-sarah/test2doc's Vulert package health score?
Vulert scores github.com/adams-sarah/test2doc 49/100, which reads as risky. 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/adams-sarah/test2doc affected?
No. v0.0.0-20211124171229-79cd42e7411d, 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/adams-sarah/test2doc should I use?
v0.0.0-20211124171229-79cd42e7411d 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/adams-sarah/test2doc have?
0 vulnerabilities are recorded for github.com/adams-sarah/test2doc 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/adams-sarah/test2doc vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/adams-sarah/test2doc 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/adams-sarah/test2doc 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/adams-sarah/test2doc for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/adams-sarah/test2doc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.