Vulnerability Database · Go · Package report
github.com/protocolbuffers/protoscope: vulnerability history, versions and safety
github.com/protocolbuffers/protoscope 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/protocolbuffers/protoscope vulnerabilities
Vulert verdict on github.com/protocolbuffers/protoscope v0.0.0-20221109213918-8e7a6aafa2c9 i
Updated on 23 Oct 2026
Good news: v0.0.0-20221109213918-8e7a6aafa2c9, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Quiet
What to do: Stay on v0.0.0-20221109213918-8e7a6aafa2c9 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20221109213918-8e7a6aafa2c9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20221109213918-8e7a6aafa2c9 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 433 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/protocolbuffers/protoscope, 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-20240313214634-59cbc171eb2c 13 Mar 2024
- v0.0.0-20221109213918-8e7a6aafa2c9 09 Nov 2022
- v0.0.0-20221104180241-706251788458 04 Nov 2022
- v0.0.0-20221102203920-1bef78be753b 02 Nov 2022
- v0.0.0-20221004195836-8b1d63939ee1 04 Oct 2022
- v0.0.0-20220801191939-6253f929ca70 01 Aug 2022
- v0.0.0-20220725161243-456501ee7624 25 Jul 2022
- v0.0.0-20220706210535-0af6ffb15f7b 06 Jul 2022
- v0.0.0-20220630155723-aed2b19b3863 30 Jun 2022
- v0.0.0-20220628201451-3afafde3dbba 28 Jun 2022
- v0.0.0-20220628201322-5ee8a2938738 28 Jun 2022
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20240313214634-59cbc171eb2c | 13 Mar 2024 | none | Apache-2.0 | — | Details → |
| v0.0.0-20221109213918-8e7a6aafa2c9 | 09 Nov 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20221104180241-706251788458 | 04 Nov 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20221102203920-1bef78be753b | 02 Nov 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20221004195836-8b1d63939ee1 | 04 Oct 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220801191939-6253f929ca70 | 01 Aug 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220725161243-456501ee7624 | 25 Jul 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220706210535-0af6ffb15f7b | 06 Jul 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220630155723-aed2b19b3863 | 30 Jun 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220628201451-3afafde3dbba | 28 Jun 2022 | none | Apache-2.0 | — | Details → |
| v0.0.0-20220628201322-5ee8a2938738 | 28 Jun 2022 | none | Apache-2.0 | — | Details → |
All 11 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/protocolbuffers/protoscope
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/protocolbuffers/protoscope
Is github.com/protocolbuffers/protoscope safe to use?
Vulert has no vulnerabilities on record for github.com/protocolbuffers/protoscope 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/protocolbuffers/protoscope's Vulert package health score?
Vulert scores github.com/protocolbuffers/protoscope 58/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/protocolbuffers/protoscope affected?
No. v0.0.0-20221109213918-8e7a6aafa2c9, 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/protocolbuffers/protoscope should I use?
v0.0.0-20221109213918-8e7a6aafa2c9 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/protocolbuffers/protoscope have?
0 vulnerabilities are recorded for github.com/protocolbuffers/protoscope 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/protocolbuffers/protoscope vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/protocolbuffers/protoscope 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/protocolbuffers/protoscope 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/protocolbuffers/protoscope for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/protocolbuffers/protoscope version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.