Vulnerability Database · Go · Package report

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

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

Vulert verdict on github.com/elazarl/go-bindata-assetfs v1.0.1 i

Updated on 23 Oct 2026

Good news: v1.0.1, the version you would install today, has no known vulnerabilities.

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

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

  • Current release v1.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 863 i
  • OpenSSF scorecard 3/10 i
  • Last release 77 months ago i
  • Licence BSD-2-Clause 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/elazarl/go-bindata-assetfs, 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-20250201162108-d06c361cdac6 01 Feb 2025 none BSD-2-Clause — Details →
v1.0.2-0.20250201162108-d06c361cdac6 01 Feb 2025 none BSD-2-Clause — Details →
v1.0.2-0.20250131190144-bd1010876af0 31 Jan 2025 none BSD-2-Clause — Details →
v1.0.2-0.20250130125617-1bf6bcc36a36 30 Jan 2025 none BSD-2-Clause — Details →
v1.0.2-0.20250129162212-26309d1cd10e 29 Jan 2025 none BSD-2-Clause — Details →
v1.0.2-0.20250124182331-405f32f57b73 24 Jan 2025 none BSD-2-Clause — Details →
v0.0.0-20220412150302-de3be3ce9537 12 Apr 2022 none BSD-2-Clause — Details →
v1.0.2-0.20220412150302-de3be3ce9537 12 Apr 2022 none BSD-2-Clause — Details →
v1.0.2-0.20220412145546-7ce3a9528728 12 Apr 2022 none BSD-2-Clause — Details →
v1.0.2-0.20220412144141-bf422e5c2704 12 Apr 2022 none BSD-2-Clause — Details →
v1.0.2-0.20220201173916-0cfd5409060d 01 Feb 2022 none BSD-2-Clause — Details →
v1.0.2-0.20220201112926-68eb727803eb 01 Feb 2022 none BSD-2-Clause — Details →
v0.0.0-20201223111950-02daa69507fc 23 Dec 2020 none BSD-2-Clause — Details →
v1.0.2-0.20201223111950-02daa69507fc 23 Dec 2020 none BSD-2-Clause — Details →
v1.0.2-0.20201223065429-31e88e84f818 23 Dec 2020 none BSD-2-Clause — Details →
v1.0.2-0.20201223055311-b9f85e97b5e3 23 Dec 2020 none BSD-2-Clause — Details →
v1.0.2-0.20201223051911-c141374d7434 23 Dec 2020 none BSD-2-Clause — Details →
v1.0.2-0.20201223045943-9eed52a8e825 23 Dec 2020 none BSD-2-Clause — Details →
v0.0.0-20200509193318-234c15e7648f 09 May 2020 none BSD-2-Clause — Details →
v1.0.1 09 May 2020 none BSD-2-Clause — Details →
v1.0.1-0.20200509193318-234c15e7648f 09 May 2020 none BSD-2-Clause — Details →
v0.0.0-20191027195357-d0111fe6fb11 27 Oct 2019 none BSD-2-Clause — Details →
v1.0.1-0.20191027195357-d0111fe6fb11 27 Oct 2019 none BSD-2-Clause — Details →
v1.0.1-0.20191027192947-67801e4648d5 27 Oct 2019 none BSD-2-Clause — Details →
v0.0.0-20180223160309-38087fe4dafb 23 Feb 2018 none BSD-2-Clause — Details →
v1.0.1-0.20180223160309-38087fe4dafb 23 Feb 2018 none BSD-2-Clause — Details →
v1.0.1-0.20180207061511-c766eaf05c72 07 Feb 2018 none BSD-2-Clause — Details →
v0.0.0-20170227212728-30f82fa23fd8 27 Feb 2017 none BSD-2-Clause — Details →
v1.0.0 27 Feb 2017 none BSD-2-Clause — Details →
v0.0.0-20160822204401-9a6736ed45b4 22 Aug 2016 none BSD-2-Clause — Details →
v0.0.0-20160803192304-e1a2a7ec64b0 03 Aug 2016 none BSD-2-Clause — Details →
v0.0.0-20160803171436-47da8037de93 03 Aug 2016 none BSD-2-Clause — Details →
v0.0.0-20160803070943-41022e9a1e5b 03 Aug 2016 none BSD-2-Clause — Details →
v0.0.0-20160802183215-d0731f2b6671 02 Aug 2016 none BSD-2-Clause — Details →
v0.0.0-20160512164801-f9c88009e127 12 May 2016 none BSD-2-Clause — Details →
v0.0.0-20160102182805-b1a95d801a86 02 Jan 2016 none BSD-2-Clause — Details →
v0.0.0-20151224045452-57eb5e1fc594 24 Dec 2015 none BSD-2-Clause — Details →
v0.0.0-20151224014125-09c764a1a7c1 24 Dec 2015 none BSD-2-Clause — Details →
v0.0.0-20151218123904-8731e8bf23ba 18 Dec 2015 none BSD-2-Clause — Details →
v0.0.0-20151119015712-446cd78562b4 19 Nov 2015 none BSD-2-Clause — Details →
v0.0.0-20150826085337-ed3050ae9d15 26 Aug 2015 none BSD-2-Clause — Details →
v0.0.0-20150813044622-d5cac425555c 13 Aug 2015 none BSD-2-Clause — Details →
v0.0.0-20150812190925-ece58942df2f 12 Aug 2015 none BSD-2-Clause — Details →
v0.0.0-20150624150248-3dcc96556217 24 Jun 2015 none BSD-2-Clause — Details →
v0.0.0-20150624140556-baffddb2946a 24 Jun 2015 none BSD-2-Clause — Details →
v0.0.0-20150511114353-d6b9aa886833 11 May 2015 none BSD-2-Clause — Details →
v0.0.0-20150414184409-bea323321994 14 Apr 2015 none BSD-2-Clause — Details →
v0.0.0-20150414151453-c57a80f1ab2a 14 Apr 2015 none BSD-2-Clause — Details →
v0.0.0-20150310090446-d44555cb0afb 10 Mar 2015 none BSD-2-Clause — Details →
v0.0.0-20150310090249-76be3f14b535 10 Mar 2015 none BSD-2-Clause — Details →
v0.0.0-20150306153923-27b5cb0aa369 06 Mar 2015 none BSD-2-Clause — Details →
v0.0.0-20150305224553-9aabad13df79 05 Mar 2015 none BSD-2-Clause — Details →
v0.0.0-20150222070249-09ba9c6a7e9a 22 Feb 2015 none BSD-2-Clause — Details →
v0.0.0-20150221191446-6344bd18a4b8 21 Feb 2015 none BSD-2-Clause — Details →
v0.0.0-20150221172832-3a00df29b1bc 21 Feb 2015 none BSD-2-Clause — Details →
v0.0.0-20150220195259-faf85be07473 20 Feb 2015 none BSD-2-Clause — Details →
v0.0.0-20150209090441-00534a354892 09 Feb 2015 none BSD-2-Clause — Details →
v0.0.0-20150107053416-fe5a90c9bd29 07 Jan 2015 none BSD-2-Clause — Details →
v0.0.0-20150107023245-443359945fae 07 Jan 2015 none BSD-2-Clause — Details →
v0.0.0-20141124081852-3e654f77289b 24 Nov 2014 none BSD-2-Clause — Details →
v0.0.0-20141102103051-dae7b94ecb1c 02 Nov 2014 none BSD-2-Clause — Details →
v0.0.0-20141101200336-b0825bd4f66a 01 Nov 2014 none BSD-2-Clause — Details →
v0.0.0-20140927162727-ae4665cf2d18 27 Sep 2014 none BSD-2-Clause — Details →
v0.0.0-20140924231218-1551cde20f15 24 Sep 2014 none BSD-2-Clause — Details →
v0.0.0-20140713155043-41e10f80479f 13 Jul 2014 none BSD-2-Clause — Details →

All 65 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/elazarl/go-bindata-assetfs

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

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

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

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

No. v1.0.1, 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/elazarl/go-bindata-assetfs should I use?

v1.0.1 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/elazarl/go-bindata-assetfs have?

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

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

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