VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/codeclysm/extract: vulnerability history, versions and safety

github.com/codeclysm/extract is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 27 releases, first recorded in Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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/codeclysm/extract vulnerabilities

Vulert verdict on github.com/codeclysm/extract v2.2.0+incompatible i

Updated on 23 Oct 2026

Careful: v2.2.0+incompatible has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 54/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v2.2.0+incompatible — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 15 Oct 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 50 i
  • OpenSSF scorecard 2/10 i
  • Last release 90 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/codeclysm/extract, 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
v1.1.2-0.20200820150813-87d1afb0e2c3 20 Aug 2020 U1 MIT No Details →
v1.1.2-0.20200820142657-c7035b38db59 20 Aug 2020 U1 MIT No Details →
v2.2.0+incompatible 05 Apr 2019 U1 MIT No Details →
v2.1.2-0.20190405092917-472639dadcd2+incompatible 05 Apr 2019 U1 MIT No Details →
v2.1.1+incompatible 01 Apr 2019 U1 MIT No Details →
v2.1.1-0.20190329192141-f3205c267524+incompatible 29 Mar 2019 U1 MIT No Details →
v2.1.0+incompatible 29 Jan 2019 U1 MIT No Details →
v1.1.2-0.20181106103905-5fdc569276f2 06 Nov 2018 U1 MIT No Details →
v1.1.2-0.20181106103905-a7efd3f7d980 06 Nov 2018 U1 MIT No Details →
v2.0.0+incompatible 06 Nov 2018 U1 MIT No Details →
v1.1.1 15 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170811144712-00c19ed537a3 11 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170811144712-3a83d0fc5a94 11 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170811144712-f12911e98817 11 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170811144712-f57f98614d44 11 Aug 2017 U1 MIT No Details →
v1.1.0 11 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170811135531-b94307061c1a 11 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170811124815-b16ffff4c57b 11 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170811124042-55b993bd87b1 11 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170810131824-58342a0eb6d8 10 Aug 2017 U1 MIT No Details →
v1.0.2-0.20170215101100-e9e3da042c5c 15 Feb 2017 U1 MIT No Details →
v1.0.1 15 Feb 2017 U1 MIT No Details →
v0.0.0-20160826142011-5e532d2c06d0 26 Aug 2016 U1 MIT No Details →
v0.0.0-20160826102830-3af8ea3f2d28 26 Aug 2016 U1 MIT No Details →
v0.0.0-20160826085811-0cf6ecb16ef7 26 Aug 2016 U1 MIT No Details →
v0.0.0-20160826085551-2821f7e2297e 26 Aug 2016 U1 MIT No Details →
v0.0.0-20160826085329-c9660bf29728 26 Aug 2016 U1 MIT No 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

  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/codeclysm/extract

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Symlink Vulnerability in Extract Package: Insufficient Checks Allowing Directory Traversal N/A unrated No fix published 15 Oct 2024

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/codeclysm/extract

Is github.com/codeclysm/extract safe to use?

Vulert records 1 vulnerabilities for github.com/codeclysm/extract in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/codeclysm/extract's Vulert package health score?

Vulert scores github.com/codeclysm/extract 54/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/codeclysm/extract affected?

Yes. v2.2.0+incompatible, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/codeclysm/extract should I use?

v2.2.0+incompatible 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/codeclysm/extract have?

1 vulnerability is recorded for github.com/codeclysm/extract in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/codeclysm/extract vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/codeclysm/extract in the last 12 months, and the oldest entry in this database dates to 15 Oct 2024. 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/codeclysm/extract 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/codeclysm/extract for upcoming vulnerabilities?

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