Vulnerability Database · Go · Package report
github.com/mohae/deepcopy: vulnerability history, versions and safety
github.com/mohae/deepcopy 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/mohae/deepcopy v0.0.0-20170929034955-c48cc78d4826 i
Updated on 23 Oct 2026
Good news: v0.0.0-20170929034955-c48cc78d4826, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v0.0.0-20170929034955-c48cc78d4826 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20170929034955-c48cc78d4826 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20170929034955-c48cc78d4826 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 628 i
- OpenSSF scorecard 1/10 i
- Last release 108 months ago i
- Licence MIT 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/mohae/deepcopy, 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.0.0-20170929034955-c48cc78d4826 29 Sep 2017
- v0.0.0-20170929031650-d8e86ac006a9 29 Sep 2017
- v0.0.0-20170919140209-4acc1c1b863e 19 Sep 2017
- v0.0.0-20170603005431-491d3605edfb 03 Jun 2017
- v0.0.0-20170602191618-01d67a0e1056 02 Jun 2017
- v0.0.0-20170602191443-c105187fac68 02 Jun 2017
- v0.0.0-20170531073922-25c8afc60478 31 May 2017
- v0.0.0-20170517194949-8134ed2cabdb 17 May 2017
- v0.0.0-20170513120728-8a8944732ecd 13 May 2017
- v0.0.0-20170308212314-bb9b5e7adda9 08 Mar 2017
- v0.0.0-20170308023632-7cea61f9bd06 08 Mar 2017
- v0.0.0-20170307013643-8dd8bab174b6 07 Mar 2017
- v0.0.0-20170301220515-b9f5cb2f9aef 01 Mar 2017
- v0.0.0-20161019173447-7163f267ab2e 19 Oct 2016
- v0.0.0-20161019065048-a40e8fd6a885 19 Oct 2016
- v0.0.0-20161011073316-1231e776b8f3 11 Oct 2016
- v0.0.0-20161006075835-07081e0dcbec 06 Oct 2016
- v0.0.0-20160901041428-d5a94469974f 01 Sep 2016
- v0.0.0-20160901041154-54dd4efc2065 01 Sep 2016
- v0.0.0-20160830174339-2e8e5ad54391 30 Aug 2016
- v0.0.0-20160829234501-28cfb1c9620c 29 Aug 2016
- v0.0.0-20150609203506-7bfd57b89471 09 Jun 2015
- v0.0.0-20150127044606-db327f63413e 27 Jan 2015
- v0.0.0-20140817012415-af3206c208b2 17 Aug 2014
- v0.0.0-20140815032732-dfdb4f253f86 15 Aug 2014
- v0.0.0-20140807031214-b14c419f8b1f 07 Aug 2014
- v0.0.0-20140731162500-89ddb925450d 31 Jul 2014
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/mohae/deepcopy
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/mohae/deepcopy
Is github.com/mohae/deepcopy safe to use?
Vulert has no vulnerabilities on record for github.com/mohae/deepcopy 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/mohae/deepcopy's Vulert package health score?
Vulert scores github.com/mohae/deepcopy 55/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/mohae/deepcopy affected?
No. v0.0.0-20170929034955-c48cc78d4826, 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/mohae/deepcopy should I use?
v0.0.0-20170929034955-c48cc78d4826 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/mohae/deepcopy have?
0 vulnerabilities are recorded for github.com/mohae/deepcopy 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/mohae/deepcopy vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mohae/deepcopy 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/mohae/deepcopy 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/mohae/deepcopy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mohae/deepcopy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.