Vulnerability Database · Go · Package report
github.com/jinzhu/inflection: vulnerability history, versions and safety
github.com/jinzhu/inflection 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/jinzhu/inflection v1.0.0 i
Updated on 23 Oct 2026
Good news: v1.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 528 i
- OpenSSF scorecard 2/10 i
- Last release 88 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/jinzhu/inflection, 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-20231016084002-bbe0a3e7399f 16 Oct 2023
- v1.0.1-0.20231016084002-bbe0a3e7399f 16 Oct 2023
- v1.0.1-0.20231016022929-92dce236bb13 16 Oct 2023
- v1.0.1-0.20230911020941-6e0c606753b8 11 Sep 2023
- v0.0.0-20210111022912-b5281034e75e 11 Jan 2021
- v1.0.1-0.20210111022912-b5281034e75e 11 Jan 2021
- v0.0.0-20201025041559-098f377e9000 25 Oct 2020
- v1.0.1-0.20201025041559-098f377e9000 25 Oct 2020
- v0.0.0-20200916080226-072f6a6317be 16 Sep 2020
- v1.0.1-0.20200916080226-072f6a6317be 16 Sep 2020
- v1.0.1-0.20200902230105-9e3e761abf6f 02 Sep 2020
- v0.0.0-20200624021413-970f05d9c0e1 24 Jun 2020
- v1.0.1-0.20200624021413-970f05d9c0e1 24 Jun 2020
- v1.0.1-0.20200624020829-592948494fff 24 Jun 2020
- v1.0.1-0.20200529102011-24bfe5197a42 29 May 2020
- v0.0.0-20200216102404-196e6ce06ca4 16 Feb 2020
- v1.0.1-0.20200216102404-196e6ce06ca4 16 Feb 2020
- v0.0.0-20190603042836-f5c5f50e6090 03 Jun 2019
- v1.0.0 03 Jun 2019
- v0.0.0-20190428173743-998a4eb7a183 28 Apr 2019
- v0.0.0-20190227044119-c2c01188fdec 27 Feb 2019
- v0.0.0-20180308033659-04140366298a 08 Mar 2018
- v0.0.0-20170102125226-1c35d901db3d 02 Jan 2017
- v0.0.0-20161126035456-b074e8fe6adf 26 Nov 2016
- v0.0.0-20160817014601-74387dc39a75 17 Aug 2016
- v0.0.0-20160816183415-e538c76307e7 16 Aug 2016
- v0.0.0-20160816180314-b0800e87c4c4 16 Aug 2016
- v0.0.0-20160816174018-1effac884841 16 Aug 2016
- v0.0.0-20160626222713-8f4d3a0d04ce 26 Jun 2016
- v0.0.0-20160626020131-a3c9edaa779d 26 Jun 2016
- v0.0.0-20151009084129-3272df6c21d0 09 Oct 2015
- v0.0.0-20150715062027-161901ffa02c 15 Jul 2015
All 32 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/jinzhu/inflection
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/jinzhu/inflection
Is github.com/jinzhu/inflection safe to use?
Vulert has no vulnerabilities on record for github.com/jinzhu/inflection 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/jinzhu/inflection's Vulert package health score?
Vulert scores github.com/jinzhu/inflection 55/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/jinzhu/inflection affected?
No. v1.0.0, 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/jinzhu/inflection should I use?
v1.0.0 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/jinzhu/inflection have?
0 vulnerabilities are recorded for github.com/jinzhu/inflection 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/jinzhu/inflection vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jinzhu/inflection 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/jinzhu/inflection 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/jinzhu/inflection for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jinzhu/inflection version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.