Vulnerability Database · Go · Package report

github.com/jedisct1/go-minisign: vulnerability history, versions and safety

Q: How do I monitor github.com/jedisct1/go-minisign for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the github.com/jedisct1/go-minisign version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

github.com/jedisct1/go-minisign is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/jedisct1/go-minisign vulnerabilities

Vulert verdict on github.com/jedisct1/go-minisign v0.0.0-20260527172527-a09352b57a22 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260527172527-a09352b57a22, the version you would install today, has no known vulnerabilities.

Package health score 66/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Inactive

What to do: Stay on v0.0.0-20260527172527-a09352b57a22 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260527172527-a09352b57a22 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release v0.0.0-20260527172527-a09352b57a22 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 120 i
OpenSSF scorecard 2/10 i
Last release 4 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/jedisct1/go-minisign, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.0.0-20260527172527-a09352b57a22	27 May 2026	none	MIT	—	Details →
v0.0.0-20260527165831-d0f28f397b06	27 May 2026	none	MIT	—	Details →
v0.0.0-20241212093149-d2f9f49435c7	12 Dec 2024	none	MIT	—	Details →
v0.0.0-20241212092403-96011901fcc4	12 Dec 2024	none	MIT	—	Details →
v0.0.0-20241212092208-adfdf8c8c224	12 Dec 2024	none	MIT	—	Details →
v0.0.0-20230811132847-661be99b8267	11 Aug 2023	none	MIT	—	Details →
v0.0.0-20230513092556-d96eb068239a	13 May 2023	none	MIT	—	Details →
v0.0.0-20230410063418-3d885d71f62c	10 Apr 2023	none	MIT	—	Details →
v0.0.0-20230211184525-1f273d8dc776	11 Feb 2023	none	MIT	—	Details →
v0.0.0-20230211133123-a7e3312f9ba9	11 Feb 2023	none	MIT	—	Details →
v0.0.0-20211028175153-1c139d1cc84b	28 Oct 2021	none	MIT	—	Details →
v0.0.0-20211008170404-d0c644b276f4	08 Oct 2021	none	MIT	—	Details →
v0.0.0-20210927135422-df01d8d3e6f4	27 Sep 2021	none	MIT	—	Details →
v0.0.0-20210813171713-0b9bfaa3a6f6	13 Aug 2021	none	MIT	—	Details →
v0.0.0-20210703085342-c1f07ee84431	03 Jul 2021	none	MIT	—	Details →
v0.0.0-20210414164026-819d7e2534ac	14 Apr 2021	none	MIT	—	Details →
v0.0.0-20210414162832-92b1ff9c6e99	14 Apr 2021	none	MIT	—	Details →
v0.0.0-20210106175330-e54e81d562c7	06 Jan 2021	none	MIT	—	Details →
v0.0.0-20210106175029-a911269a6702	06 Jan 2021	none	MIT	—	Details →
v0.0.0-20210101122305-335e26e05d5b	01 Jan 2021	none	MIT	—	Details →
v0.0.0-20210101122252-71174274badc	01 Jan 2021	none	MIT	—	Details →
v0.0.0-20201231231454-0d68e8cb573a	31 Dec 2020	none	MIT	—	Details →
v0.0.0-20190909160543-45766022959e	09 Sep 2019	none	MIT	—	Details →
v0.0.0-20190420161605-5cc5b100fd4d	20 Apr 2019	none	MIT	—	Details →
v0.0.0-20190420145252-1b8376d8f109	20 Apr 2019	none	MIT	—	Details →
v0.0.0-20190420145214-9fd418ca2919	20 Apr 2019	none	MIT	—	Details →
v0.0.0-20190116111841-a4a14b527183	16 Jan 2019	none	MIT	—	Details →
v0.0.0-20180516093733-f4dbde220b4f	16 May 2018	none	MIT	—	Details →
v0.0.0-20180510095731-9db77cefece9	10 May 2018	none	MIT	—	Details →
v0.0.0-20180113214641-f404c079ea5f	13 Jan 2018	none	MIT	—	Details →

All 30 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for github.com/jedisct1/go-minisign

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

Subscribe to Vulert on Telegram

Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.

Join the channel →

Questions

About github.com/jedisct1/go-minisign

Is github.com/jedisct1/go-minisign safe to use?

Vulert has no vulnerabilities on record for github.com/jedisct1/go-minisign 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/jedisct1/go-minisign's Vulert package health score?

Vulert scores github.com/jedisct1/go-minisign 66/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/jedisct1/go-minisign affected?

No. v0.0.0-20260527172527-a09352b57a22, 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/jedisct1/go-minisign should I use?

v0.0.0-20260527172527-a09352b57a22 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/jedisct1/go-minisign have?

0 vulnerabilities are recorded for github.com/jedisct1/go-minisign 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/jedisct1/go-minisign vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/jedisct1/go-minisign 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/jedisct1/go-minisign 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/jedisct1/go-minisign for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jedisct1/go-minisign version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.