Vulnerability Database · Go · Package report
github.com/blacktop/go-termimg: vulnerability history, versions and safety
github.com/blacktop/go-termimg is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/blacktop/go-termimg v0.1.26 i
Updated on 23 Oct 2026
Good news: v0.1.26, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.1.26 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.26 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.26 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 68 i
- Last release 8 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/blacktop/go-termimg, 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.
- v0.0.0-20260223013217-ba7747c5d296 23 Feb 2026
- v0.1.27-0.20260223013217-ba7747c5d296 23 Feb 2026
- v0.1.26 23 Feb 2026
- v0.1.25 23 Feb 2026
- v0.0.0-20260113021049-10c943d08691 13 Jan 2026
- v0.1.25-0.20260113021049-10c943d08691 13 Jan 2026
- v0.0.0-20251121054346-79e227292848 21 Nov 2025
- v0.1.24 21 Nov 2025
- v0.1.23 21 Nov 2025
- v0.0.0-20251121044310-858ad8d326d7 21 Nov 2025
- v0.1.22 21 Nov 2025
- v0.0.0-20251106215238-a992162c5c6e 06 Nov 2025
- v0.1.21 06 Nov 2025
- v0.0.0-20250908142116-6f10edfe878e 08 Sep 2025
- v0.1.21-0.20250908142116-6f10edfe878e 08 Sep 2025
- v0.0.0-20250825034510-6adc3ad4fe57 25 Aug 2025
- v0.1.21-0.20250825034510-6adc3ad4fe57 25 Aug 2025
- v0.0.0-20250811034053-609eb7f3b3de 11 Aug 2025
- v0.1.21-0.20250811034053-609eb7f3b3de 11 Aug 2025
- v0.0.0-20250715025337-0e7f52f31434 15 Jul 2025
- v0.1.21-0.20250715025337-0e7f52f31434 15 Jul 2025
- v0.1.21-0.20250713210525-8d73da175903 13 Jul 2025
- v0.1.21-0.20250713202456-298f6b5ad853 13 Jul 2025
- v0.1.20 13 Jul 2025
- v0.1.20-0.20250710002243-c1d556411864 10 Jul 2025
- v0.1.20-0.20250708212336-eb88777e95aa 08 Jul 2025
- v0.0.0-20250703232011-462d92e84ff2 03 Jul 2025
- v0.1.20-0.20250703232011-462d92e84ff2 03 Jul 2025
- v0.1.19 03 Jul 2025
- v0.1.18 03 Jul 2025
- v0.1.17 12 May 2025
- v0.0.0-20241111165607-ae216205f641 11 Nov 2024
- v0.1.17-0.20241111165607-ae216205f641 11 Nov 2024
- v0.1.17-0.20240906182907-bf97dcc377bc 06 Sep 2024
- v0.0.0-20240906043628-4b0d0d146586 06 Sep 2024
- v0.1.17-0.20240906043628-4b0d0d146586 06 Sep 2024
- v0.1.16 06 Sep 2024
- v0.1.16-0.20240905235036-4493aa3256ff 05 Sep 2024
- v0.1.15 05 Sep 2024
- v0.1.15-0.20240905220250-5bfedb89230f 05 Sep 2024
- v0.1.14 05 Sep 2024
- v0.1.14-0.20240905061029-bc2fe42fc94a 05 Sep 2024
- v0.1.13 05 Sep 2024
- v0.1.12 05 Sep 2024
- v0.1.12-0.20240904234127-dbc9378c411d 04 Sep 2024
- v0.1.11 04 Sep 2024
- v0.1.10 04 Sep 2024
- v0.1.9 04 Sep 2024
- v0.1.8 04 Sep 2024
- v0.1.7 04 Sep 2024
- v0.1.6 04 Sep 2024
- v0.1.5 04 Sep 2024
- v0.1.4 04 Sep 2024
- v0.1.3 04 Sep 2024
- v0.1.1 04 Sep 2024
- v0.1.2 04 Sep 2024
- v0.1.0 04 Sep 2024
- v0.0.0-20240904204522-3e0ec7223e4e 04 Sep 2024
All 58 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/blacktop/go-termimg
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
Questions
About github.com/blacktop/go-termimg
Is github.com/blacktop/go-termimg safe to use?
Vulert has no vulnerabilities on record for github.com/blacktop/go-termimg 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/blacktop/go-termimg's Vulert package health score?
Vulert scores github.com/blacktop/go-termimg 75/100, which reads as in good shape. 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/blacktop/go-termimg affected?
No. v0.1.26, 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/blacktop/go-termimg should I use?
v0.1.26 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/blacktop/go-termimg have?
0 vulnerabilities are recorded for github.com/blacktop/go-termimg 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/blacktop/go-termimg vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/blacktop/go-termimg 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/blacktop/go-termimg 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/blacktop/go-termimg for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/blacktop/go-termimg version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.