Vulnerability Database · Go · Package report
github.com/GehirnInc/crypt: vulnerability history, versions and safety
github.com/GehirnInc/crypt 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/GehirnInc/crypt v0.0.0-20230320061759-8cc1b52080c5 i
Updated on 23 Oct 2026
Good news: v0.0.0-20230320061759-8cc1b52080c5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Quiet
What to do: Stay on v0.0.0-20230320061759-8cc1b52080c5 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20230320061759-8cc1b52080c5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20230320061759-8cc1b52080c5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 82 i
- OpenSSF scorecard 2/10 i
- Last release 43 months ago i
- Licence BSD-2-Clause 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/GehirnInc/crypt, 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-20230320061759-8cc1b52080c5 20 Mar 2023
- v0.0.0-20200316065508-bb7000b8a962 16 Mar 2020
- v0.0.0-20200312132234-7a37f98c2186 12 Mar 2020
- v0.0.0-20200312121934-4e0dc7b99ba1 12 Mar 2020
- v0.0.0-20190301055215-6c0105aabd46 01 Mar 2019
- v0.0.0-20181012164702-df17b4ba03ee 12 Oct 2018
- v0.0.0-20180913103248-8d661b355ec0 13 Sep 2018
- v0.0.0-20180731120900-6e9b9f2f02a0 31 Jul 2018
- v0.0.0-20170404120257-5a3fafaa7c86 04 Apr 2017
- v0.0.0-20130714054319-18f26c25ff3d 14 Jul 2013
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20230320061759-8cc1b52080c5 | 20 Mar 2023 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20200316065508-bb7000b8a962 | 16 Mar 2020 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20200312132234-7a37f98c2186 | 12 Mar 2020 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20200312121934-4e0dc7b99ba1 | 12 Mar 2020 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20190301055215-6c0105aabd46 | 01 Mar 2019 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20181012164702-df17b4ba03ee | 12 Oct 2018 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20180913103248-8d661b355ec0 | 13 Sep 2018 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20180731120900-6e9b9f2f02a0 | 31 Jul 2018 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20170404120257-5a3fafaa7c86 | 04 Apr 2017 | none | BSD-2-Clause | — | Details → |
| v0.0.0-20130714054319-18f26c25ff3d | 14 Jul 2013 | none | BSD-2-Clause | — | Details → |
All 10 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/GehirnInc/crypt
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/GehirnInc/crypt
Is github.com/GehirnInc/crypt safe to use?
Vulert has no vulnerabilities on record for github.com/GehirnInc/crypt 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/GehirnInc/crypt's Vulert package health score?
Vulert scores github.com/GehirnInc/crypt 57/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/GehirnInc/crypt affected?
No. v0.0.0-20230320061759-8cc1b52080c5, 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/GehirnInc/crypt should I use?
v0.0.0-20230320061759-8cc1b52080c5 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/GehirnInc/crypt have?
0 vulnerabilities are recorded for github.com/GehirnInc/crypt 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/GehirnInc/crypt vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/GehirnInc/crypt 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/GehirnInc/crypt 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/GehirnInc/crypt for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/GehirnInc/crypt version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.