Vulnerability Database · Go · Package report
github.com/emersion/go-vcard: vulnerability history, versions and safety
github.com/emersion/go-vcard 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/emersion/go-vcard v0.1.0 i
Updated on 23 Oct 2026
Good news: v0.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v0.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 129 i
- OpenSSF scorecard 2/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/emersion/go-vcard, 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.1.0 18 Aug 2026
- v0.0.0-20260618161152-d854b7e0e2d3 18 Jun 2026
- v0.0.0-20241024213814-c9703dde27ff 24 Oct 2024
- v0.0.0-20230815062825-8fda7d206ec9 15 Aug 2023
- v0.0.0-20230626131229-38c18b295bbd 26 Jun 2023
- v0.0.0-20230620162823-8ba80123c260 20 Jun 2023
- v0.0.0-20230331202150-f3d26859ccd3 31 Mar 2023
- v0.0.0-20220507122617-d4056df0ec4a 07 May 2022
- v0.0.0-20220507095133-23d9bf4dcb88 07 May 2022
- v0.0.0-20210521075357-3445b9171995 21 May 2021
- v0.0.0-20200508080525-dd3110a24ec2 08 May 2020
- v0.0.0-20200508074950-8801711c9355 08 May 2020
- v0.0.0-20191221110513-5f81fa0d3cc7 21 Dec 2019
- v0.0.0-20190105225839-8856043f13c5 05 Jan 2019
- v0.0.0-20181001195144-be59a9be3b3f 01 Oct 2018
- v0.0.0-20171002085919-e65e62c72276 02 Oct 2017
- v0.0.0-20170930020304-311a5fdc321e 30 Sep 2017
All 17 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/emersion/go-vcard
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/emersion/go-vcard
Is github.com/emersion/go-vcard safe to use?
Vulert has no vulnerabilities on record for github.com/emersion/go-vcard 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/emersion/go-vcard's Vulert package health score?
Vulert scores github.com/emersion/go-vcard 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/emersion/go-vcard affected?
No. v0.1.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/emersion/go-vcard should I use?
v0.1.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/emersion/go-vcard have?
0 vulnerabilities are recorded for github.com/emersion/go-vcard 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/emersion/go-vcard vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/emersion/go-vcard 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/emersion/go-vcard 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/emersion/go-vcard for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/emersion/go-vcard version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.