Vulnerability Database · Go · Package report

github.com/containerd/errdefs: vulnerability history, versions and safety

github.com/containerd/errdefs is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/containerd/errdefs v1.0.0 i

Updated on 23 Oct 2026

Good news: v1.0.0, the version you would install today, has no known vulnerabilities.

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3 i
  • OpenSSF scorecard 4/10 i
  • Last release 24 months ago i
  • Licence Apache-2.0 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/containerd/errdefs, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.3.1-0.20260610152211-d09a3057588c 10 Jun 2026 none Apache-2.0 — Details →
v1.0.1-0.20260610152211-d09a3057588c 10 Jun 2026 none Apache-2.0 — Details →
v1.0.1-0.20260609220351-1846affbb768 09 Jun 2026 none Apache-2.0 — Details →
v0.0.0-20241008131009-4817405e4a3c 08 Oct 2024 none Apache-2.0 — Details →
v0.3.1-0.20241008131009-4817405e4a3c 08 Oct 2024 none Apache-2.0 — Details →
v1.0.0 08 Oct 2024 none Apache-2.0 — Details →
v0.0.0-20241007212025-9fd32fc2ca77 07 Oct 2024 none Apache-2.0 — Details →
v0.2.1-0.20241007212025-9fd32fc2ca77 07 Oct 2024 none Apache-2.0 — Details →
v0.3.0 07 Oct 2024 none Apache-2.0 — Details →
v0.2.1-0.20241007023010-303a6ea6abfd 07 Oct 2024 none Apache-2.0 — Details →
v0.2.1-0.20241002171454-46a6522eb15b 02 Oct 2024 none Apache-2.0 — Details →
v0.1.1-0.20240902073319-02b65bcc1b50 02 Sep 2024 none Apache-2.0 — Details →
v0.2.0 02 Sep 2024 none Apache-2.0 — Details →
v0.1.1-0.20240901231122-41d12e1db5cf 01 Sep 2024 none Apache-2.0 — Details →
v0.1.1-0.20240816002822-70440b892c8b 16 Aug 2024 none Apache-2.0 — Details →
v0.1.1-0.20240815220859-b9dce4d7bd5a 15 Aug 2024 none Apache-2.0 — Details →
v0.1.1-0.20240710171436-ffb0349b41b9 10 Jul 2024 none Apache-2.0 — Details →
v0.1.1-0.20240703235926-124d0dc9f0cd 03 Jul 2024 none Apache-2.0 — Details →
v0.1.1-0.20240621225552-6c7f4021d232 21 Jun 2024 none Apache-2.0 — Details →
v0.1.1-0.20240621223057-9f87502f13ad 21 Jun 2024 none Apache-2.0 — Details →
v0.1.1-0.20240619070649-6022faf38302 19 Jun 2024 none Apache-2.0 — Details →
v0.1.1-0.20240619070649-70fd2d7ff216 19 Jun 2024 none Apache-2.0 — Details →
v0.1.1-0.20240601002953-038bb7bc3611 01 Jun 2024 none Apache-2.0 — Details →
v0.1.1-0.20240531010750-9564d8ff8829 31 May 2024 none Apache-2.0 — Details →
v0.1.1-0.20240426162928-2dc9c179f365 26 Apr 2024 none Apache-2.0 — Details →
v0.1.1-0.20240209060210-98ae5ec6b555 09 Feb 2024 none Apache-2.0 — Details →
v0.1.1-0.20240123063307-9854dc7575de 23 Jan 2024 none Apache-2.0 — Details →
v0.1.1-0.20240123063307-f727cdba81f1 23 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240123060242-3abe02904986 23 Jan 2024 none Apache-2.0 — Details →
v0.1.0 23 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240122203849-1a36dc069f18 22 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20230103204716-e0d1732a5c38 03 Jan 2023 none — — Details →
v0.0.0-20190529000229-a5ed164fa1d7 29 May 2019 none — — Details →
v0.0.0-20181129222653-6429ed05c3f2 29 Nov 2018 none — — Details →
v0.0.0-20171128203449-5141fc3c3f40 28 Nov 2017 none — — Details →
v0.0.0-20171113214525-c58133ca4faa 13 Nov 2017 none — — Details →
v0.0.0-20171010234047-0442ecd10b19 10 Oct 2017 none — — Details →
v0.0.0-20170909022229-3840e985d0df 09 Sep 2017 none — — Details →
v0.0.0-20170823214517-c1ced0002b5f 23 Aug 2017 none — — Details →
v0.0.0-20170818181908-84ac5e255fd2 18 Aug 2017 none — — Details →

All 40 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/containerd/errdefs

No vulnerability write-ups match this view

Search all 0 in the database →

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/containerd/errdefs

Is github.com/containerd/errdefs safe to use?

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

Vulert scores github.com/containerd/errdefs 60/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/containerd/errdefs affected?

No. v1.0.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/containerd/errdefs should I use?

v1.0.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/containerd/errdefs have?

0 vulnerabilities are recorded for github.com/containerd/errdefs 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/containerd/errdefs vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/containerd/errdefs 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/containerd/errdefs 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/containerd/errdefs for upcoming vulnerabilities?

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