Vulnerability Database · Go · Package report
github.com/codegangsta/inject: vulnerability history, versions and safety
github.com/codegangsta/inject 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/codegangsta/inject v0.0.0-20150114235600-33e0aa1cb7c0 i
Updated on 23 Oct 2026
Good news: v0.0.0-20150114235600-33e0aa1cb7c0, 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 v0.0.0-20150114235600-33e0aa1cb7c0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20150114235600-33e0aa1cb7c0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20150114235600-33e0aa1cb7c0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 976 i
- OpenSSF scorecard 1/10 i
- Last release 141 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/codegangsta/inject, 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-20150114235600-33e0aa1cb7c0 14 Jan 2015
- v0.0.0-20141229062759-36b0b9b3a1e3 29 Dec 2014
- v0.0.0-20140630231407-4b8172520a03 30 Jun 2014
- v0.0.0-20140630230639-30d6043ea633 30 Jun 2014
- v0.0.0-20140627235300-2ba402c4886b 27 Jun 2014
- v0.0.0-20140425184007-37d7f8432a3e 25 Apr 2014
- v0.0.0-20140423185230-c5f917dab170 23 Apr 2014
- v0.0.0-20140423032335-8822b072a363 23 Apr 2014
- v0.0.0-20140416125411-73f95eb26ad5 16 Apr 2014
- v0.0.0-20140218220929-9aea7a2fa5b7 18 Feb 2014
- v0.0.0-20140205221022-1817ef28a0e7 05 Feb 2014
- v0.0.0-20131215055853-346a984957aa 15 Dec 2013
- v0.0.0-20131214044408-8b1a9340f98d 14 Dec 2013
- v0.0.0-20131214042755-38b4cba53804 14 Dec 2013
- v0.0.0-20131205230241-07b1cf5ecdb5 05 Dec 2013
- v0.0.0-20131205225203-0028222ed395 05 Dec 2013
- v0.0.0-20131121011029-32500f07db6e 21 Nov 2013
- v0.0.0-20131121011029-37512bbe41b4 21 Nov 2013
- v0.0.0-20131117180115-a77f61897e56 17 Nov 2013
- v0.0.0-20131116162008-efc7081a7fbd 16 Nov 2013
- v0.0.0-20131107180103-13ba42b54c9b 07 Nov 2013
- v0.0.0-20131106021144-570bc87c7c34 06 Nov 2013
- v0.0.0-20131106015159-01a1370030f9 06 Nov 2013
- v0.0.0-20131030201854-814af716b322 30 Oct 2013
- v0.0.0-20131029195048-47dfc51935ef 29 Oct 2013
- v0.0.0-20131029032147-16be42cdd6f4 29 Oct 2013
All 26 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/codegangsta/inject
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/codegangsta/inject
Is github.com/codegangsta/inject safe to use?
Vulert has no vulnerabilities on record for github.com/codegangsta/inject 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/codegangsta/inject's Vulert package health score?
Vulert scores github.com/codegangsta/inject 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/codegangsta/inject affected?
No. v0.0.0-20150114235600-33e0aa1cb7c0, 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/codegangsta/inject should I use?
v0.0.0-20150114235600-33e0aa1cb7c0 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/codegangsta/inject have?
0 vulnerabilities are recorded for github.com/codegangsta/inject 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/codegangsta/inject vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/codegangsta/inject 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/codegangsta/inject 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/codegangsta/inject for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/codegangsta/inject version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.