Vulnerability Database · Go · Package report

github.com/k1LoW/expand: vulnerability history, versions and safety

Q: How do I monitor github.com/k1LoW/expand for upcoming vulnerabilities?

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

github.com/k1LoW/expand is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/k1LoW/expand vulnerabilities

Vulert verdict on github.com/k1LoW/expand v0.16.7 i

Updated on 23 Oct 2026

Good news: v0.16.7, the version you would install today, has no known vulnerabilities.

Package health score 63/100

Security Minor issues
Maintenance Sustainable
Popularity Little adoption
Community Inactive

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

Current release v0.16.7 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 1 i
OpenSSF scorecard 3/10 i
Last release 9 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/k1LoW/expand, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.16.8-0.20260629002726-39ee30fd530b	29 Jun 2026	none	MIT	—	Details →
v0.16.7	12 Jan 2026	none	MIT	—	Details →
v0.16.6	22 Dec 2025	none	MIT	—	Details →
v0.16.5	17 Dec 2025	none	MIT	—	Details →
v0.16.4	01 Dec 2025	none	MIT	—	Details →
v0.16.3	26 Oct 2025	none	MIT	—	Details →
v0.16.2	04 May 2025	none	MIT	—	Details →
v0.16.1	08 Apr 2025	none	MIT	—	Details →
v0.16.0	17 Mar 2025	none	MIT	—	Details →
v0.15.5	19 Feb 2025	none	MIT	—	Details →
v0.15.4	03 Feb 2025	none	MIT	—	Details →
v0.15.3	20 Jan 2025	none	MIT	—	Details →
v0.15.2	23 Dec 2024	none	MIT	—	Details →
v0.15.1	16 Dec 2024	none	MIT	—	Details →
v0.14.1-0.20241202023249-0c2be1b4ff05	02 Dec 2024	none	MIT	—	Details →
v0.15.0	02 Dec 2024	none	MIT	—	Details →
v0.13.1-0.20241116010413-d83bf778d16b	16 Nov 2024	none	MIT	—	Details →
v0.14.0	16 Nov 2024	none	MIT	—	Details →
v0.13.1-0.20241111105443-ab03e144020c	11 Nov 2024	none	MIT	—	Details →
v0.12.1-0.20241104122722-58621f20ac5c	04 Nov 2024	none	MIT	—	Details →
v0.13.0	04 Nov 2024	none	MIT	—	Details →
v0.11.1-0.20240308083409-27531b63c23e	08 Mar 2024	none	MIT	—	Details →
v0.12.0	08 Mar 2024	none	MIT	—	Details →
v0.10.2-0.20231230052421-977a4c886a3c	30 Dec 2023	none	MIT	—	Details →
v0.11.0	30 Dec 2023	none	MIT	—	Details →
v0.10.2-0.20231030121834-28bc9e231f50	30 Oct 2023	none	MIT	—	Details →
v0.10.1	30 Oct 2023	none	MIT	—	Details →
v0.10.0	30 Oct 2023	none	MIT	—	Details →
v0.9.0	12 Oct 2023	none	MIT	—	Details →
v0.8.0	07 May 2023	none	MIT	—	Details →
v0.7.0	04 Mar 2023	none	MIT	—	Details →
v0.6.1	04 Mar 2023	none	MIT	—	Details →
v0.6.0	03 Mar 2023	none	MIT	—	Details →
v0.5.6	04 Feb 2023	none	MIT	—	Details →
v0.5.6-0.20221121213216-f4050fac60a3	21 Nov 2022	none	MIT	—	Details →
v0.5.5	21 Nov 2022	none	MIT	—	Details →
v0.5.4	14 Nov 2022	none	MIT	—	Details →
v0.5.3	05 Oct 2022	none	MIT	—	Details →
v0.5.2	05 Oct 2022	none	MIT	—	Details →
v0.5.1	04 Oct 2022	none	MIT	—	Details →
v0.5.0	04 Oct 2022	none	MIT	—	Details →
v0.4.0	18 Jul 2022	none	MIT	—	Details →
v0.3.0	06 Mar 2022	none	MIT	—	Details →
v0.2.0	05 Mar 2022	none	MIT	—	Details →
v0.1.1-0.20211009160120-46ce5a750170	09 Oct 2021	none	MIT	—	Details →
v0.1.1-0.20211009141659-725fa704a1b3	09 Oct 2021	none	MIT	—	Details →
v0.1.0	09 Oct 2021	none	MIT	—	Details →
v0.0.0-20211009141313-1fa0398e82e9	09 Oct 2021	none	MIT	—	Details →

All 48 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for github.com/k1LoW/expand

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/k1LoW/expand

Is github.com/k1LoW/expand safe to use?

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

Vulert scores github.com/k1LoW/expand 63/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/k1LoW/expand affected?

No. v0.16.7, 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/k1LoW/expand should I use?

v0.16.7 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/k1LoW/expand have?

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

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

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