VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/holiman/billy: vulnerability history, versions and safety

github.com/holiman/billy 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/holiman/billy vulnerabilities

Vulert verdict on github.com/holiman/billy v0.0.0-20250707135307-f2f9b9aae7db i

Updated on 23 Oct 2026

Good news: v0.0.0-20250707135307-f2f9b9aae7db, the version you would install today, has no known vulnerabilities.

Package health score 61/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Inactive

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

  • Current release v0.0.0-20250707135307-f2f9b9aae7db — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 62 i
  • OpenSSF scorecard 2/10 i
  • Last release 15 months ago i
  • Licence BSD-3-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/holiman/billy, 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-20250707135307-f2f9b9aae7db 07 Jul 2025 none BSD-3-Clause — Details →
v0.0.0-20250108194907-5352da567d3e 08 Jan 2025 none BSD-3-Clause — Details →
v0.0.0-20250108194813-593306ca7d70 08 Jan 2025 none BSD-3-Clause — Details →
v0.0.0-20241012173847-7527a2505cb9 12 Oct 2024 none BSD-3-Clause — Details →
v0.0.0-20240322075458-72a4e81ec6da 22 Mar 2024 none BSD-3-Clause — Details →
v0.0.0-20240321072129-bc745246cfd0 21 Mar 2024 none BSD-3-Clause — Details →
v0.0.0-20240216141850-2abb0c79d3c4 16 Feb 2024 none BSD-3-Clause — Details →
v0.0.0-20240216131340-2f83e1ec0866 16 Feb 2024 none BSD-3-Clause — Details →
v0.0.0-20240216113543-33af227c444b 16 Feb 2024 none BSD-3-Clause — Details →
v0.0.0-20230718173358-1c7e68d277a7 18 Jul 2023 none BSD-3-Clause — Details →
v0.0.0-20230616073924-97ff6efa2b93 16 Jun 2023 none BSD-3-Clause — Details →
v0.0.0-20230317085645-f164d9ae3da9 17 Mar 2023 none BSD-3-Clause — Details →
v0.0.0-20230316185826-aa185eaf63cd 16 Mar 2023 none BSD-3-Clause — Details →
v0.0.0-20230216192329-4c8dcfa72fd6 16 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230215105924-6fa72ae39e1d 15 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230211195139-c683dcd3608f 11 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230207114840-541d897a8ee7 07 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230207111604-546238ffe63b 07 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230207105259-2a89ba389171 07 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230207093140-0f75cc661234 07 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230207081921-325444aabbb0 07 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230207080543-e2772adf0341 07 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230206154916-9262195bb578 06 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230205214435-954ef0cb0494 05 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230205213840-792836a3c561 05 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230205213225-4e4672c51413 05 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230205194214-1671ef14964e 05 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230204094400-5de837b67bfc 04 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230203142234-397c36db4105 03 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230203122042-1ad2af8393e0 03 Feb 2023 none BSD-3-Clause — Details →
v0.0.0-20230130130824-a8d3067d0be1 30 Jan 2023 none — — Details →
v0.0.0-20230127162400-c7010b972997 27 Jan 2023 none — — Details →
v0.0.0-20230127160036-11546fb35d17 27 Jan 2023 none — — Details →
v0.0.0-20230126142721-0dd9ea2ea27b 26 Jan 2023 none — — Details →
v0.0.0-20230126140109-24a5fd0b4679 26 Jan 2023 none — — Details →
v0.0.0-20230126124831-2498c963d16a 26 Jan 2023 none — — Details →
v0.0.0-20230125135123-10615159f211 25 Jan 2023 none — — Details →
v0.0.0-20230125124524-fbaa215dd53f 25 Jan 2023 none — — Details →
v0.0.0-20230125094816-1ae100eefae7 25 Jan 2023 none — — Details →
v0.0.0-20230125085559-e205f6ade7af 25 Jan 2023 none — — Details →
v0.0.0-20230124161554-07a776fde6cb 24 Jan 2023 none — — Details →
v0.0.0-20230124135706-f810a526b332 24 Jan 2023 none — — Details →
v0.0.0-20230124134021-5091cd27231a 24 Jan 2023 none — — Details →
v0.0.0-20230124092423-b3014147dc4d 24 Jan 2023 none — — Details →

All 44 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/holiman/billy

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/holiman/billy

Is github.com/holiman/billy safe to use?

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

Vulert scores github.com/holiman/billy 61/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/holiman/billy affected?

No. v0.0.0-20250707135307-f2f9b9aae7db, 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/holiman/billy should I use?

v0.0.0-20250707135307-f2f9b9aae7db 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/holiman/billy have?

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

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

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