Vulnerability Database · Go · Package report
github.com/xordataexchange/crypt: vulnerability history, versions and safety
github.com/xordataexchange/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/xordataexchange/crypt v0.0.2 i
Updated on 23 Oct 2026
Good news: v0.0.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v0.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 523 i
- OpenSSF scorecard 1/10 i
- Last release 143 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/xordataexchange/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-20170626215501-b2862e3d0a77 26 Jun 2017
- v0.0.2-0.20170626215501-b2862e3d0a77 26 Jun 2017
- v0.0.3-0.20170626215501-b2862e3d0a77 26 Jun 2017
- v0.0.3-0.20170626195725-0e2a6ad3766a 26 Jun 2017
- v0.0.0-20150523230031-749e360c8f23 23 May 2015
- v0.0.3-0.20150523230031-749e360c8f23 23 May 2015
- v0.0.3-0.20150505025706-6bef06dc39f6 05 May 2015
- v0.0.0-20150327172645-93de65664ef0 27 Mar 2015
- v0.0.3-0.20150327172645-93de65664ef0 27 Mar 2015
- v0.0.3-0.20150207231920-8bc1a9168d30 07 Feb 2015
- v0.0.3-0.20150205063739-82deba0f5624 05 Feb 2015
- v0.0.3-0.20150204063517-615ea9ae6201 04 Feb 2015
- v0.0.3-0.20150127213156-0499a3c94698 27 Jan 2015
- v0.0.3-0.20150113162044-55de7505d844 13 Jan 2015
- v0.0.0-20141203013100-9095a9689663 03 Dec 2014
- v0.0.3-0.20141203013100-9095a9689663 03 Dec 2014
- v0.0.3-0.20141119160833-0d01a097d404 19 Nov 2014
- v0.0.0-20141111190654-7654b5e814b5 11 Nov 2014
- v0.0.3-0.20141111190654-7654b5e814b5 11 Nov 2014
- v0.0.3-0.20141107130945-03786bce9f8a 07 Nov 2014
- v0.0.3-0.20141105210653-32346be2d0a6 05 Nov 2014
- v0.0.3-0.20141105204405-d773445670c8 05 Nov 2014
- v0.0.0-20141027180634-0d6dc8c093c1 27 Oct 2014
- v0.0.2 27 Oct 2014
- v0.0.2-0.20141024160138-041620bddb3e 24 Oct 2014
- v0.0.1 19 Oct 2014
- v0.0.0-20141018152456-0da2d78deff9 18 Oct 2014
- v0.0.0-20141018042923-20aedd147c22 18 Oct 2014
All 28 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/xordataexchange/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/xordataexchange/crypt
Is github.com/xordataexchange/crypt safe to use?
Vulert has no vulnerabilities on record for github.com/xordataexchange/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/xordataexchange/crypt's Vulert package health score?
Vulert scores github.com/xordataexchange/crypt 55/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/xordataexchange/crypt affected?
No. v0.0.2, 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/xordataexchange/crypt should I use?
v0.0.2 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/xordataexchange/crypt have?
0 vulnerabilities are recorded for github.com/xordataexchange/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/xordataexchange/crypt vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/xordataexchange/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/xordataexchange/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/xordataexchange/crypt for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/xordataexchange/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.