Vulnerability Database · Go · Package report

github.com/hashicorp/vault-plugin-mock: vulnerability history, versions and safety

Q: How do I monitor github.com/hashicorp/vault-plugin-mock for upcoming vulnerabilities?

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

github.com/hashicorp/vault-plugin-mock is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/hashicorp/vault-plugin-mock vulnerabilities

Vulert verdict on github.com/hashicorp/vault-plugin-mock v0.19.13 i

Updated on 23 Oct 2026

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

Package health score 45/100

Security Minor issues
Maintenance Unmaintained
Popularity Little adoption
Community Inactive

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

Current release v0.19.13 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
OpenSSF scorecard 3/10 i
Last release 66 months ago i
Licence MPL-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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/hashicorp/vault-plugin-mock, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.19.1-0.20241112143912-9a2930e18229	12 Nov 2024	none	MPL-2.0	—	Details →
v0.19.1-0.20230117192134-6eb8b420c331	17 Jan 2023	none	MPL-2.0	—	Details →
v0.19.1-0.20220726185152-0fc8ca5d37ff	26 Jul 2022	none	MPL-2.0	—	Details →
v0.19.1-0.20220110211950-d2e09a276405	10 Jan 2022	none	MPL-2.0	—	Details →
v0.19.1-0.20210602224343-bd8a0f62318a	02 Jun 2021	none	MPL-2.0	—	Details →
v0.19.1-0.20210521213129-c955c959a1d0	21 May 2021	none	MPL-2.0	—	Details →
v0.19.13	22 Apr 2021	none	—	—	Details →
v0.19.12	10 Apr 2021	none	—	—	Details →
v0.19.11	10 Apr 2021	none	—	—	Details →
v0.19.10	10 Apr 2021	none	—	—	Details →
v0.19.8	09 Apr 2021	none	—	—	Details →
v0.19.7	09 Apr 2021	none	—	—	Details →
v0.19.6	09 Apr 2021	none	—	—	Details →
v0.19.5	09 Apr 2021	none	—	—	Details →
v0.19.4	09 Apr 2021	none	—	—	Details →
v0.19.3	09 Apr 2021	none	—	—	Details →
v0.19.2	08 Apr 2021	none	—	—	Details →
v0.19.1	08 Apr 2021	none	—	—	Details →
v0.19.0	07 Apr 2021	none	—	—	Details →
v0.18.0	07 Apr 2021	none	—	—	Details →
v0.17.0	07 Apr 2021	none	—	—	Details →
v0.15.3	02 Sep 2020	none	—	—	Details →
v0.16.0	02 Sep 2020	none	—	—	Details →
v0.15.2	02 Sep 2020	none	—	—	Details →
v0.15.1	02 Sep 2020	none	—	—	Details →
v0.16.1	26 Aug 2020	none	—	—	Details →
v0.12.9	26 Aug 2020	none	—	—	Details →
v0.14.0	26 Aug 2020	none	—	—	Details →
v0.12.8	26 Aug 2020	none	—	—	Details →
v0.12.6	26 Aug 2020	none	—	—	Details →
v0.12.7	26 Aug 2020	none	—	—	Details →
v0.12.5	26 Aug 2020	none	—	—	Details →
v0.12.4	26 Aug 2020	none	—	—	Details →
v0.12.3	21 Aug 2020	none	—	—	Details →
v0.12.2	20 Aug 2020	none	—	—	Details →
v0.13.0	20 Aug 2020	none	—	—	Details →
v0.12.1	19 Aug 2020	none	—	—	Details →
v0.12.0	19 Aug 2020	none	—	—	Details →
v0.11.0	19 Aug 2020	none	—	—	Details →
v0.10.0	19 Aug 2020	none	—	—	Details →
v0.9.0	19 Aug 2020	none	—	—	Details →
v0.8.0	19 Aug 2020	none	—	—	Details →
v0.7.0	19 Aug 2020	none	—	—	Details →
v0.6.4	19 Aug 2020	none	—	—	Details →
v0.6.3	19 Aug 2020	none	—	—	Details →
v0.6.2	19 Aug 2020	none	—	—	Details →
v0.6.1	19 Aug 2020	none	—	—	Details →
v0.6.0	19 Aug 2020	none	—	—	Details →
v0.5.0	19 Aug 2020	none	—	—	Details →
v0.4.0	19 Aug 2020	none	—	—	Details →
v0.3.0	19 Aug 2020	none	—	—	Details →
v0.2.0	19 Aug 2020	none	—	—	Details →
v0.1.0	19 Aug 2020	none	—	—	Details →
v0.0.0-20200817190708-9e12e106da80	17 Aug 2020	none	—	—	Details →

All 54 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for github.com/hashicorp/vault-plugin-mock

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/hashicorp/vault-plugin-mock

Is github.com/hashicorp/vault-plugin-mock safe to use?

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

Vulert scores github.com/hashicorp/vault-plugin-mock 45/100, which reads as risky. 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/hashicorp/vault-plugin-mock affected?

No. v0.19.13, 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/hashicorp/vault-plugin-mock should I use?

v0.19.13 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/hashicorp/vault-plugin-mock have?

0 vulnerabilities are recorded for github.com/hashicorp/vault-plugin-mock 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/hashicorp/vault-plugin-mock vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/hashicorp/vault-plugin-mock 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/hashicorp/vault-plugin-mock 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/hashicorp/vault-plugin-mock for upcoming vulnerabilities?

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