Vulnerability Database · Go · Package report
github.com/bgentry/go-netrc: vulnerability history, versions and safety
github.com/bgentry/go-netrc 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/bgentry/go-netrc v0.0.0-20140422174119-9fd32a8b3d3d i
Updated on 23 Oct 2026
Good news: v0.0.0-20140422174119-9fd32a8b3d3d, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20140422174119-9fd32a8b3d3d or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20140422174119-9fd32a8b3d3d too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20140422174119-9fd32a8b3d3d — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 26 i
- OpenSSF scorecard 1/10 i
- Last release 150 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/bgentry/go-netrc, 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-20140422174119-9fd32a8b3d3d 22 Apr 2014
- v0.0.0-20140328140126-2e5e1d1fe453 28 Mar 2014
- v0.0.0-20140131193637-13bba5cc3ac0 31 Jan 2014
- v0.0.0-20140131034117-2cbf58d9c8c0 31 Jan 2014
- v0.0.0-20140130171449-419b88e634d8 30 Jan 2014
- v0.0.0-20140130171448-202f370211f6 30 Jan 2014
- v0.0.0-20140127233355-79ca7e5a7155 27 Jan 2014
- v0.0.0-20131203011033-f001804ec3af 03 Dec 2013
- v0.0.0-20131202235605-86c675a0fb3f 02 Dec 2013
- v0.0.0-20131202234632-a40158e7764e 02 Dec 2013
- v0.0.0-20131013172847-4422b68c9c93 13 Oct 2013
- v0.0.0-20130904191252-e7caaf32ca3d 04 Sep 2013
- v0.0.0-20130904002336-76e5a931535b 04 Sep 2013
- v0.0.0-20120212223539-ad0347713f24 12 Feb 2012
- v0.0.0-20120118074807-ad987862450a 18 Jan 2012
- v0.0.0-20111205022812-83352cc55785 05 Dec 2011
- v0.0.0-20110411055653-e731dd1ff2fe 11 Apr 2011
- v0.0.0-20100925004727-066071aaeab5 25 Sep 2010
- v0.0.0-20100718015616-205bffba6dc5 18 Jul 2010
All 19 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/bgentry/go-netrc
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/bgentry/go-netrc
Is github.com/bgentry/go-netrc safe to use?
Vulert has no vulnerabilities on record for github.com/bgentry/go-netrc 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/bgentry/go-netrc's Vulert package health score?
Vulert scores github.com/bgentry/go-netrc 42/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/bgentry/go-netrc affected?
No. v0.0.0-20140422174119-9fd32a8b3d3d, 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/bgentry/go-netrc should I use?
v0.0.0-20140422174119-9fd32a8b3d3d 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/bgentry/go-netrc have?
0 vulnerabilities are recorded for github.com/bgentry/go-netrc 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/bgentry/go-netrc vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/bgentry/go-netrc 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/bgentry/go-netrc 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/bgentry/go-netrc for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/bgentry/go-netrc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.