Vulnerability Database · Go · Package report
github.com/hashicorp/copywrite: vulnerability history, versions and safety
github.com/hashicorp/copywrite 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/hashicorp/copywrite v0.25.3 i
Updated on 23 Oct 2026
Good news: v0.25.3, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v0.25.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.25.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.25.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 121 i
- OpenSSF scorecard 6/10 i
- Last release 5 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.
01 Versions
Which versions are affected
Every version Vulert tracks for github.com/hashicorp/copywrite, 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.25.4-0.20261022071116-6206c58c9b33 22 Oct 2026
- v0.25.4-0.20261013072052-32c8ccaf5a08 13 Oct 2026
- v0.25.4-0.20260821054319-a7e97f1b896b 21 Aug 2026
- v0.25.4-0.20260714065922-3d1ec1cf3e66 14 Jul 2026
- v0.25.3 29 Apr 2026
- v0.25.2 23 Mar 2026
- v0.25.1 02 Mar 2026
- v0.25.0 12 Feb 2026
- v0.24.2 05 Feb 2026
- v0.24.1 03 Feb 2026
- v0.24.0 28 Jan 2026
- v0.23.0 27 Jan 2026
- v0.22.1-0.20260108065303-46323435e774 08 Jan 2026
- v0.22.1-0.20250625043554-35eedf5f520b 25 Jun 2025
- v0.22.0 18 Mar 2025
- v0.21.0 20 Feb 2025
- v0.20.0 20 Jan 2025
- v0.19.1-0.20241119115222-23206318c975 19 Nov 2024
- v0.19.1-0.20241024135202-9452ada66fd6 24 Oct 2024
- v0.18.1-0.20240624205013-6ed520a71016 24 Jun 2024
- v0.19.0 24 Jun 2024
- v0.18.1-0.20240325202718-69677b0b60eb 25 Mar 2024
- v0.17.1-0.20231128182935-0f077594eee1 28 Nov 2023
- v0.18.0 28 Nov 2023
- v0.16.7-0.20231113194056-9103d867d88f 13 Nov 2023
- v0.17.0 13 Nov 2023
- v0.16.6 28 Sep 2023
- v0.16.5 27 Sep 2023
- v0.0.0-20230808155615-e76cf1905ae8 08 Aug 2023
- v0.16.4 26 Jun 2023
- v0.16.4-0.20230322152847-39309b6187ad 22 Mar 2023
- v0.16.4-0.20230313210940-4152d017e567 13 Mar 2023
- v0.16.3 01 Mar 2023
- v0.16.2 27 Feb 2023
- v0.16.2-0.20230209023601-4af928579f5a 09 Feb 2023
- v0.16.1 09 Feb 2023
- v0.16.0 06 Feb 2023
- v0.15.0 02 Feb 2023
- v0.14.0 30 Jan 2023
- v0.13.2 27 Jan 2023
- v0.13.1 24 Jan 2023
- v0.13.0 20 Jan 2023
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.25.4-0.20261022071116-6206c58c9b33 | 22 Oct 2026 | none | MPL-2.0 | — | Details → |
| v0.25.4-0.20261013072052-32c8ccaf5a08 | 13 Oct 2026 | none | MPL-2.0 | — | Details → |
| v0.25.4-0.20260821054319-a7e97f1b896b | 21 Aug 2026 | none | MPL-2.0 | — | Details → |
| v0.25.4-0.20260714065922-3d1ec1cf3e66 | 14 Jul 2026 | none | MPL-2.0 | — | Details → |
| v0.25.3 | 29 Apr 2026 | none | MPL-2.0 | — | Details → |
| v0.25.2 | 23 Mar 2026 | none | MPL-2.0 | — | Details → |
| v0.25.1 | 02 Mar 2026 | none | MPL-2.0 | — | Details → |
| v0.25.0 | 12 Feb 2026 | none | MPL-2.0 | — | Details → |
| v0.24.2 | 05 Feb 2026 | none | MPL-2.0 | — | Details → |
| v0.24.1 | 03 Feb 2026 | none | MPL-2.0 | — | Details → |
| v0.24.0 | 28 Jan 2026 | none | MPL-2.0 | — | Details → |
| v0.23.0 | 27 Jan 2026 | none | MPL-2.0 | — | Details → |
| v0.22.1-0.20260108065303-46323435e774 | 08 Jan 2026 | none | MPL-2.0 | — | Details → |
| v0.22.1-0.20250625043554-35eedf5f520b | 25 Jun 2025 | none | MPL-2.0 | — | Details → |
| v0.22.0 | 18 Mar 2025 | none | MPL-2.0 | — | Details → |
| v0.21.0 | 20 Feb 2025 | none | MPL-2.0 | — | Details → |
| v0.20.0 | 20 Jan 2025 | none | MPL-2.0 | — | Details → |
| v0.19.1-0.20241119115222-23206318c975 | 19 Nov 2024 | none | MPL-2.0 | — | Details → |
| v0.19.1-0.20241024135202-9452ada66fd6 | 24 Oct 2024 | none | MPL-2.0 | — | Details → |
| v0.18.1-0.20240624205013-6ed520a71016 | 24 Jun 2024 | none | MPL-2.0 | — | Details → |
| v0.19.0 | 24 Jun 2024 | none | MPL-2.0 | — | Details → |
| v0.18.1-0.20240325202718-69677b0b60eb | 25 Mar 2024 | none | MPL-2.0 | — | Details → |
| v0.17.1-0.20231128182935-0f077594eee1 | 28 Nov 2023 | none | MPL-2.0 | — | Details → |
| v0.18.0 | 28 Nov 2023 | none | MPL-2.0 | — | Details → |
| v0.16.7-0.20231113194056-9103d867d88f | 13 Nov 2023 | none | MPL-2.0 | — | Details → |
| v0.17.0 | 13 Nov 2023 | none | MPL-2.0 | — | Details → |
| v0.16.6 | 28 Sep 2023 | none | MPL-2.0 | — | Details → |
| v0.16.5 | 27 Sep 2023 | none | MPL-2.0 | — | Details → |
| v0.0.0-20230808155615-e76cf1905ae8 | 08 Aug 2023 | none | MPL-2.0 | — | Details → |
| v0.16.4 | 26 Jun 2023 | none | MPL-2.0 | — | Details → |
| v0.16.4-0.20230322152847-39309b6187ad | 22 Mar 2023 | none | MPL-2.0 | — | Details → |
| v0.16.4-0.20230313210940-4152d017e567 | 13 Mar 2023 | none | MPL-2.0 | — | Details → |
| v0.16.3 | 01 Mar 2023 | none | MPL-2.0 | — | Details → |
| v0.16.2 | 27 Feb 2023 | none | MPL-2.0 | — | Details → |
| v0.16.2-0.20230209023601-4af928579f5a | 09 Feb 2023 | none | MPL-2.0 | — | Details → |
| v0.16.1 | 09 Feb 2023 | none | MPL-2.0 | — | Details → |
| v0.16.0 | 06 Feb 2023 | none | MPL-2.0 | — | Details → |
| v0.15.0 | 02 Feb 2023 | none | MPL-2.0 | — | Details → |
| v0.14.0 | 30 Jan 2023 | none | MPL-2.0 | — | Details → |
| v0.13.2 | 27 Jan 2023 | none | MPL-2.0 | — | Details → |
| v0.13.1 | 24 Jan 2023 | none | MPL-2.0 | — | Details → |
| v0.13.0 | 20 Jan 2023 | none | MPL-2.0 | — | Details → |
All 42 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/hashicorp/copywrite
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/hashicorp/copywrite
Is github.com/hashicorp/copywrite safe to use?
Vulert has no vulnerabilities on record for github.com/hashicorp/copywrite 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/copywrite's Vulert package health score?
Vulert scores github.com/hashicorp/copywrite 75/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/hashicorp/copywrite affected?
No. v0.25.3, 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/copywrite should I use?
v0.25.3 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/copywrite have?
0 vulnerabilities are recorded for github.com/hashicorp/copywrite 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/copywrite vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hashicorp/copywrite 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/copywrite 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/copywrite for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hashicorp/copywrite version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.