Vulnerability Database · Go · Package report
github.com/srwiley/rasterx: vulnerability history, versions and safety
github.com/srwiley/rasterx 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/srwiley/rasterx v0.0.0-20220730225603-2ab79fcdd4ef i
Updated on 23 Oct 2026
Good news: v0.0.0-20220730225603-2ab79fcdd4ef, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20220730225603-2ab79fcdd4ef or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20220730225603-2ab79fcdd4ef too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20220730225603-2ab79fcdd4ef — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 150 i
- OpenSSF scorecard 1/10 i
- Last release 50 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/srwiley/rasterx, 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-20220730225603-2ab79fcdd4ef 30 Jul 2022
- v0.0.0-20220615024203-67b7089efd25 15 Jun 2022
- v0.0.0-20220128185129-2efea2b9ea41 28 Jan 2022
- v0.0.0-20210519020934-456a8d69b780 19 May 2021
- v0.0.0-20200120212402-85cb7272f5e9 20 Jan 2020
- v0.0.0-20181219215540-696f7edb7a7e 19 Dec 2018
- v0.0.0-20181219215056-ad60d10d9a74 19 Dec 2018
- v0.0.0-20181206061844-cc62e474106d 06 Dec 2018
- v0.0.0-20181106005149-5c501e873244 06 Nov 2018
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20220730225603-2ab79fcdd4ef | 30 Jul 2022 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20220615024203-67b7089efd25 | 15 Jun 2022 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20220128185129-2efea2b9ea41 | 28 Jan 2022 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20210519020934-456a8d69b780 | 19 May 2021 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20200120212402-85cb7272f5e9 | 20 Jan 2020 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20181219215540-696f7edb7a7e | 19 Dec 2018 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20181219215056-ad60d10d9a74 | 19 Dec 2018 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20181206061844-cc62e474106d | 06 Dec 2018 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20181106005149-5c501e873244 | 06 Nov 2018 | none | BSD-3-Clause | — | Details → |
All 9 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/srwiley/rasterx
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/srwiley/rasterx
Is github.com/srwiley/rasterx safe to use?
Vulert has no vulnerabilities on record for github.com/srwiley/rasterx 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/srwiley/rasterx's Vulert package health score?
Vulert scores github.com/srwiley/rasterx 47/100, which reads as risky. 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/srwiley/rasterx affected?
No. v0.0.0-20220730225603-2ab79fcdd4ef, 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/srwiley/rasterx should I use?
v0.0.0-20220730225603-2ab79fcdd4ef 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/srwiley/rasterx have?
0 vulnerabilities are recorded for github.com/srwiley/rasterx 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/srwiley/rasterx vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/srwiley/rasterx 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/srwiley/rasterx 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/srwiley/rasterx for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/srwiley/rasterx version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.