VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/go-bindata/go-bindata: vulnerability history, versions and safety

github.com/go-bindata/go-bindata 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/go-bindata/go-bindata vulnerabilities

Vulert verdict on github.com/go-bindata/go-bindata v3.1.2+incompatible i

Updated on 23 Oct 2026

Good news: v3.1.2+incompatible, the version you would install today, has no known vulnerabilities.

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

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

  • Current release v3.1.2+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,910 i
  • OpenSSF scorecard 2/10 i
  • Last release 88 months ago i
  • Licence non-standard 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/go-bindata/go-bindata, 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-20200225045032-e95cfde2231b 25 Feb 2020 none — — Details →
v0.0.0-20200225044736-05c33f4eca0e 25 Feb 2020 none — — Details →
v0.0.0-20200225043923-da2d11185c7b 25 Feb 2020 none — — Details →
v0.0.0-20200120190340-5ef44676b7c0 20 Jan 2020 none — — Details →
v0.0.0-20191126083508-8639be0519b3 26 Nov 2019 none — — Details →
v1.0.1-0.20191126083508-8639be0519b3 26 Nov 2019 none — — Details →
v0.0.0-20190727215321-8d0fd4a6bcbc 27 Jul 2019 none — — Details →
v0.0.0-20190711162640-ee3c2418e368 11 Jul 2019 none — — Details →
v1.0.1-0.20190711162640-ee3c2418e368 11 Jul 2019 none — — Details →
v1.0.1-0.20190612062754-1bff0b8a062d 12 Jun 2019 none — — Details →
v0.0.0-20190612062219-2fd8009b8966 12 Jun 2019 none — — Details →
v1.0.1-0.20190612060128-1b54bbffbcf3 12 Jun 2019 none — — Details →
v0.0.0-20190612055933-b139d7db0394 12 Jun 2019 none — — Details →
v0.0.0-20190612052453-0cb471447831 12 Jun 2019 none — — Details →
v3.1.2+incompatible 11 Jun 2019 none — — Details →
v3.1.2-0.20190501152150-2447bc714f98+incompatible 01 May 2019 none — — Details →
v3.1.2-0.20190419160932-b97c95f139f1+incompatible 19 Apr 2019 none — — Details →
v3.1.1+incompatible 02 Apr 2019 none — — Details →
v3.1.1-0.20190402051959-77f7b3292e2a+incompatible 02 Apr 2019 none — — Details →
v3.1.0+incompatible 01 Apr 2019 none — — Details →
v1.0.1-0.20190323153451-22f7e2b04721 23 Mar 2019 none — — Details →
v1.0.1-0.20181115135310-0561df6c74e3 15 Nov 2018 none — — Details →
v1.0.1-0.20181114132151-8b65995d7539 14 Nov 2018 none — — Details →
v0.0.0-20181025070752-41975c0ccc30 25 Oct 2018 none — — Details →
v1.0.1-0.20181025070752-41975c0ccc30 25 Oct 2018 none — — Details →
v1.0.1-0.20181025070635-6518908443d2 25 Oct 2018 none — — Details →
v1.0.1-0.20181017183725-59fc9bc25624 17 Oct 2018 none — — Details →
v1.0.1-0.20180813172013-fbb4dc43ae24 13 Aug 2018 none — — Details →
v0.0.0-20180714090641-d266f3a45668 14 Jul 2018 none — — Details →
v1.0.1-0.20180714090641-d266f3a45668 14 Jul 2018 none — — Details →
v1.0.1-0.20180304075109-987f604888da 04 Mar 2018 none — — Details →
v0.0.0-20180304072717-5ebd2c033d84 04 Mar 2018 none — — Details →
v1.0.0 04 Mar 2018 none — — Details →
v0.0.0-20151023074806-8ed2cd0f6d98 23 Oct 2015 none — — Details →
v0.0.0-20150721061843-94e9e44a67ab 21 Jul 2015 none — — Details →
v0.0.0-20150310181717-b5d9eff767e2 10 Mar 2015 none — — Details →
v0.0.0-20141120174717-bbd0c6e27120 20 Nov 2014 none — — Details →

All 37 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/go-bindata/go-bindata

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/go-bindata/go-bindata

Is github.com/go-bindata/go-bindata safe to use?

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

Vulert scores github.com/go-bindata/go-bindata 57/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/go-bindata/go-bindata affected?

No. v3.1.2+incompatible, 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/go-bindata/go-bindata should I use?

v3.1.2+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/go-bindata/go-bindata have?

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

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

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