Vulnerability Database · Go · Package report
github.com/parallaxsecond/parsec-client-go: vulnerability history, versions and safety
github.com/parallaxsecond/parsec-client-go 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.
See all github.com/parallaxsecond/parsec-client-go vulnerabilities
Vulert verdict on github.com/parallaxsecond/parsec-client-go v0.0.0-20221025095442-f0a77d263cf9 i
Updated on 23 Oct 2026
Good news: v0.0.0-20221025095442-f0a77d263cf9, 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.0-20221025095442-f0a77d263cf9 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20221025095442-f0a77d263cf9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20221025095442-f0a77d263cf9 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 13 i
- OpenSSF scorecard 3/10 i
- Last release 47 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/parallaxsecond/parsec-client-go, 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-20221025095442-f0a77d263cf9 25 Oct 2022
- v0.0.0-20220111122524-cb78842db373 11 Jan 2022
- v0.0.0-20211103225106-5b20ea374a33 03 Nov 2021
- v0.0.0-20211103095135-ab55bfb86f91 03 Nov 2021
- v0.0.0-20210416104105-e2d188152601 16 Apr 2021
- v0.0.0-20210316233125-02b09a7ed631 16 Mar 2021
- v0.0.0-20210303002800-963abe41cb6d 03 Mar 2021
- v0.0.0-20210126115819-e044440361f1 26 Jan 2021
- v0.0.0-20210121225044-a6c51b7553a6 21 Jan 2021
- v0.0.0-20200327221407-c5f44d03a9c2 27 Mar 2020
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20221025095442-f0a77d263cf9 | 25 Oct 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220111122524-cb78842db373 | 11 Jan 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20211103225106-5b20ea374a33 | 03 Nov 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20211103095135-ab55bfb86f91 | 03 Nov 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210416104105-e2d188152601 | 16 Apr 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210316233125-02b09a7ed631 | 16 Mar 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210303002800-963abe41cb6d | 03 Mar 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210126115819-e044440361f1 | 26 Jan 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20210121225044-a6c51b7553a6 | 21 Jan 2021 | none | Apache-2.0 | — | Details → |
| v0.0.0-20200327221407-c5f44d03a9c2 | 27 Mar 2020 | 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/parallaxsecond/parsec-client-go
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/parallaxsecond/parsec-client-go
Is github.com/parallaxsecond/parsec-client-go safe to use?
Vulert has no vulnerabilities on record for github.com/parallaxsecond/parsec-client-go 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/parallaxsecond/parsec-client-go's Vulert package health score?
Vulert scores github.com/parallaxsecond/parsec-client-go 52/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/parallaxsecond/parsec-client-go affected?
No. v0.0.0-20221025095442-f0a77d263cf9, 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/parallaxsecond/parsec-client-go should I use?
v0.0.0-20221025095442-f0a77d263cf9 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/parallaxsecond/parsec-client-go have?
0 vulnerabilities are recorded for github.com/parallaxsecond/parsec-client-go 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/parallaxsecond/parsec-client-go vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/parallaxsecond/parsec-client-go 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/parallaxsecond/parsec-client-go 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/parallaxsecond/parsec-client-go for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/parallaxsecond/parsec-client-go version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.