Vulnerability Database · Go · Package report
github.com/jbenet/goprocess: vulnerability history, versions and safety
github.com/jbenet/goprocess 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/jbenet/goprocess v0.1.4 i
Updated on 23 Oct 2026
Good news: v0.1.4, 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.1.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 73 i
- OpenSSF scorecard 1/10 i
- Last release 78 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/jbenet/goprocess, 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-20200324212226-23d20c20149e 24 Mar 2020
- v0.1.4 24 Mar 2020
- v0.1.4-0.20200324212226-23d20c20149e 24 Mar 2020
- v0.1.4-0.20200324212049-0912cb7da61d 24 Mar 2020
- v0.0.0-20190509221706-7f9d9ed286ba 09 May 2019
- v0.1.3 09 May 2019
- v0.1.3-0.20190509211533-04d75c1c5bd0 09 May 2019
- v0.1.2 07 May 2019
- v0.1.1 07 May 2019
- v0.1.1-0.20190507181628-379d0b20d112 07 May 2019
- v0.1.0 01 May 2019
- v0.0.0-20190501193229-35160f55530e 01 May 2019
- v0.0.0-20160826012719-b497e2f366b8 26 Aug 2016
- v0.0.0-20160826012641-d62d4e2eb025 26 Aug 2016
- v0.0.0-20150909030556-64a8220330a4 09 Sep 2015
- v0.0.0-20150909025230-2a13f2f03197 09 Sep 2015
- v0.0.0-20150729082859-4562d0c5780b 29 Jul 2015
- v0.0.0-20150714035543-788dcf5ca351 14 Jul 2015
- v0.0.0-20150712093902-847dff69c3e2 12 Jul 2015
- v0.0.0-20150711071028-1427143f40ee 11 Jul 2015
- v0.0.0-20150704225049-a6650d0b69f2 04 Jul 2015
- v0.0.0-20150617221317-67fe91f1081e 17 Jun 2015
- v0.0.0-20150412112309-ea63e9540cd1 12 Apr 2015
- v0.0.0-20150323080833-c877297c00ff 23 Mar 2015
- v0.0.0-20150223215053-b4efc4c8775f 23 Feb 2015
- v0.0.0-20150223172056-ac78a156e293 23 Feb 2015
- v0.0.0-20150126214018-060ad098994e 26 Jan 2015
- v0.0.0-20150120195208-5b02f8d275a2 20 Jan 2015
- v0.0.0-20150106161253-162148a58668 06 Jan 2015
All 29 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/jbenet/goprocess
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/jbenet/goprocess
Is github.com/jbenet/goprocess safe to use?
Vulert has no vulnerabilities on record for github.com/jbenet/goprocess 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/jbenet/goprocess's Vulert package health score?
Vulert scores github.com/jbenet/goprocess 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/jbenet/goprocess affected?
No. v0.1.4, 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/jbenet/goprocess should I use?
v0.1.4 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/jbenet/goprocess have?
0 vulnerabilities are recorded for github.com/jbenet/goprocess 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/jbenet/goprocess vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jbenet/goprocess 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/jbenet/goprocess 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/jbenet/goprocess for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jbenet/goprocess version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.