VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/notaryproject/notation-plugin-framework-go: vulnerability history, versions and safety

github.com/notaryproject/notation-plugin-framework-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/notaryproject/notation-plugin-framework-go vulnerabilities

Vulert verdict on github.com/notaryproject/notation-plugin-framework-go 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 59/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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
  • Last release 32 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/notaryproject/notation-plugin-framework-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.0.0-20240522170431-f7da81c3f38f 22 May 2024 none Apache-2.0 — Details →
v1.0.1-0.20240522170431-f7da81c3f38f 22 May 2024 none Apache-2.0 — Details →
v0.0.0-20240418164341-0d0eab24c9de 18 Apr 2024 none Apache-2.0 — Details →
v1.0.1-0.20240418164341-0d0eab24c9de 18 Apr 2024 none Apache-2.0 — Details →
v1.0.1-0.20240408200435-887f3a61ac5c 08 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240229064507-164385624925 29 Feb 2024 none Apache-2.0 — Details →
v1.0.1-0.20240229064507-164385624925 29 Feb 2024 none Apache-2.0 — Details →
v1.0.1-0.20240206191115-71eb02bc2cd7 06 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240131025544-b708a085c999 31 Jan 2024 none Apache-2.0 — Details →
v1.0.0 31 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240131025353-a1ec01ff7683 31 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240125020929-29add9b6ba35 25 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240124142630-113b0ed0991a 24 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240123020259-4df400ed5b01 23 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240119031034-43178dd6f114 19 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240118131908-1d7d81aad7a4 18 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240117132631-afc5fb9a7132 17 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240117123629-a078bb85a796 17 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240116162504-e3d2a30026df 16 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240103032027-c077edacd1ef 03 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20231231102023-d1bf2545609b 31 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231231101634-d62962875909 31 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231226051652-511a017f73c7 26 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231223071005-d5393d90819d 23 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231222132521-c8c68d2fe13b 22 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20230825173304-86df5d1a32c2 25 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230726062531-7b5a8a6f5bc6 26 Jul 2023 none Apache-2.0 — Details →

All 27 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/notaryproject/notation-plugin-framework-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/notaryproject/notation-plugin-framework-go

Is github.com/notaryproject/notation-plugin-framework-go safe to use?

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

Vulert scores github.com/notaryproject/notation-plugin-framework-go 59/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/notaryproject/notation-plugin-framework-go 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/notaryproject/notation-plugin-framework-go 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/notaryproject/notation-plugin-framework-go have?

0 vulnerabilities are recorded for github.com/notaryproject/notation-plugin-framework-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/notaryproject/notation-plugin-framework-go vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/notaryproject/notation-plugin-framework-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/notaryproject/notation-plugin-framework-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/notaryproject/notation-plugin-framework-go for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/notaryproject/notation-plugin-framework-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.