VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/cdevents/sdk-go: vulnerability history, versions and safety

github.com/cdevents/sdk-go 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.

See all github.com/cdevents/sdk-go vulnerabilities

Vulert verdict on github.com/cdevents/sdk-go v0.5.1 i

Updated on 23 Oct 2026

Good news: v0.5.1, the version you would install today, has no known vulnerabilities.

Package health score 72/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v0.5.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 17 i
  • OpenSSF scorecard 6/10 i
  • Last release 3 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/cdevents/sdk-go, 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.5.2-0.20260729124027-e499d2be4b91 29 Jul 2026 none Apache-2.0 — Details →
v0.5.1 25 Jun 2026 none Apache-2.0 — Details →
v0.4.2-0.20260213121459-a54a820329ec 13 Feb 2026 none Apache-2.0 — Details →
v0.5.0 13 Feb 2026 none Apache-2.0 — Details →
v0.4.2-0.20260213120125-4f095f3ef863 13 Feb 2026 none Apache-2.0 — Details →
v0.4.2-0.20250716150913-468b88e50ada 16 Jul 2025 none Apache-2.0 — Details →
v0.3.3-0.20240807104310-d5d4efc9ee25 07 Aug 2024 none Apache-2.0 — Details →
v0.4.1 07 Aug 2024 none Apache-2.0 — Details →
v0.3.3-0.20240724093315-1078d5069c99 24 Jul 2024 none Apache-2.0 — Details →
v0.3.3-0.20240717073559-5e81f2367a79 17 Jul 2024 none Apache-2.0 — Details →
v0.3.3-0.20240709170947-080d904cf609 09 Jul 2024 none Apache-2.0 — Details →
v0.3.3-0.20240624103922-9ac1c5642fbe 24 Jun 2024 none Apache-2.0 — Details →
v0.3.3-0.20240517121732-f8b8b910f8d0 17 May 2024 none Apache-2.0 — Details →
v0.3.2 26 Jun 2023 none Apache-2.0 — Details →
v0.3.2-0.20230626134845-39341b23818a 26 Jun 2023 none Apache-2.0 — Details →
v0.3.2-0.20230626110327-b99c57a5d64a 26 Jun 2023 none Apache-2.0 — Details →
v0.2.1-0.20230623132925-a9483fa2b595 23 Jun 2023 none Apache-2.0 — Details →
v0.3.1 23 Jun 2023 none Apache-2.0 — Details →
v0.2.1-0.20230504122745-1a3b71a88d73 04 May 2023 none Apache-2.0 — Details →
v0.3.0 04 May 2023 none Apache-2.0 — Details →
v0.2.1 04 Apr 2023 none Apache-2.0 — Details →
v0.2.1-0.20230404225052-af5880c7b23b 04 Apr 2023 none Apache-2.0 — Details →
v0.2.0 28 Mar 2023 none Apache-2.0 — Details →
v0.1.1-0.20230320215354-c5213f103c25 20 Mar 2023 none Apache-2.0 — Details →
v0.1.2 20 Mar 2023 none Apache-2.0 — Details →
v0.1.1 20 Mar 2023 none Apache-2.0 — Details →
v0.1.1-0.20221021162310-01ccf8944718 21 Oct 2022 none Apache-2.0 — Details →
v0.1.0 21 Oct 2022 none Apache-2.0 — Details →
v0.0.0-20221020121544-0fd6ba2fe3e7 20 Oct 2022 none Apache-2.0 — Details →
v0.0.0-20221020102454-cbb0046cb711 20 Oct 2022 none Apache-2.0 — Details →
v0.0.0-20221019140100-7274160e5c7a 19 Oct 2022 none Apache-2.0 — Details →
v0.0.0-20221010171210-f8b7d36f49d5 10 Oct 2022 none Apache-2.0 — Details →
v0.0.0-20220914152319-4fae45c2a16f 14 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220908201233-c4f7d249a3da 08 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220908103927-c3f283b46080 08 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220906180749-68332d9d2c73 06 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220901132553-c3770e8607a7 01 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220831194302-9fd3c41cf2f9 31 Aug 2022 none Apache-2.0 — Details →
v0.0.0-20220831193317-0c7f31ae45a7 31 Aug 2022 none Apache-2.0 — Details →
v0.0.0-20220825132926-eb173b454645 25 Aug 2022 none Apache-2.0 — 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/cdevents/sdk-go

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/cdevents/sdk-go

Is github.com/cdevents/sdk-go safe to use?

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

Vulert scores github.com/cdevents/sdk-go 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/cdevents/sdk-go affected?

No. v0.5.1, 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/cdevents/sdk-go should I use?

v0.5.1 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/cdevents/sdk-go have?

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

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

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