Vulnerability Database · Go · Package report
github.com/jzelinskie/stringz: vulnerability history, versions and safety
github.com/jzelinskie/stringz 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/jzelinskie/stringz v0.0.3 i
Updated on 23 Oct 2026
Good news: v0.0.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1 i
- OpenSSF scorecard 2/10 i
- Last release 34 months ago i
- Licence Apache-2.0 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/jzelinskie/stringz, 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.3 08 Dec 2023
- v0.0.3-0.20231208220335-5903ada23cab 08 Dec 2023
- v0.0.2 31 Jul 2023
- v0.0.2-0.20230731201224-739fdb5aa897 31 Jul 2023
- v0.0.1 07 Jul 2021
- v0.0.0-20210604201827-321bc7aaa2dc 04 Jun 2021
- v0.0.0-20210414224931-d6a8ce844a70 14 Apr 2021
- v0.0.0-20210413012450-6d92f7dd1bdb 13 Apr 2021
- v0.0.0-20190611201025-8b95e4c8d5d9 11 Jun 2019
- v0.0.0-20190318210106-71e491f59d39 18 Mar 2019
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.3 | 08 Dec 2023 | none | Apache-2.0 | — | Details → |
| v0.0.3-0.20231208220335-5903ada23cab | 08 Dec 2023 | none | Apache-2.0 | — | Details → |
| v0.0.2 | 31 Jul 2023 | none | Apache-2.0 | — | Details → |
| v0.0.2-0.20230731201224-739fdb5aa897 | 31 Jul 2023 | none | Apache-2.0 | — | Details → |
| v0.0.1 | 07 Jul 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210604201827-321bc7aaa2dc | 04 Jun 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210414224931-d6a8ce844a70 | 14 Apr 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210413012450-6d92f7dd1bdb | 13 Apr 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20190611201025-8b95e4c8d5d9 | 11 Jun 2019 | none | Apache-2.0 | — | Details → |
| v0.0.0-20190318210106-71e491f59d39 | 18 Mar 2019 | none | Apache-2.0 | — | Details → |
All 10 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/jzelinskie/stringz
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/jzelinskie/stringz
Is github.com/jzelinskie/stringz safe to use?
Vulert has no vulnerabilities on record for github.com/jzelinskie/stringz 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/jzelinskie/stringz's Vulert package health score?
Vulert scores github.com/jzelinskie/stringz 50/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/jzelinskie/stringz affected?
No. v0.0.3, 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/jzelinskie/stringz should I use?
v0.0.3 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/jzelinskie/stringz have?
0 vulnerabilities are recorded for github.com/jzelinskie/stringz 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/jzelinskie/stringz vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jzelinskie/stringz 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/jzelinskie/stringz 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/jzelinskie/stringz for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jzelinskie/stringz version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.