VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/hoppscotch/proxyscotch: vulnerability history, versions and safety

github.com/hoppscotch/proxyscotch is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 10 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/hoppscotch/proxyscotch vulnerabilities

Vulert verdict on github.com/hoppscotch/proxyscotch v0.1.4 i

Updated on 23 Oct 2026

Action needed: v0.1.4 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 69/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.1.4 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 428 i
  • OpenSSF scorecard 4/10 i
  • Last release 19 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/hoppscotch/proxyscotch, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.1.5-0.20250312094420-9f5c60f591a0 12 Mar 2025 H1 MIT Yes Details →
v0.1.4 12 Mar 2025 H1 MIT Yes Details →
v0.1.3 12 Mar 2025 H1 MIT Yes Details →
v0.1.2-0.20231116084603-cc0c4c79ae8b 16 Nov 2023 H1 MIT Yes Details →
v0.1.2-0.20230704014005-94b0c0f2c0aa 04 Jul 2023 H1 MIT Yes Details →
v0.1.2-0.20230123185923-69a8f67cfb8b 23 Jan 2023 H1 MIT Yes Details →
v0.1.2-0.20221024192153-6a513693f52d 24 Oct 2022 H1 MIT Yes Details →
v0.1.2-0.20220911140322-2e94def1c281 11 Sep 2022 H1 MIT Yes Details →
v0.1.1 10 Sep 2022 H1 MIT Yes Details →
v0.1.0 03 Jun 2022 H1 — Yes 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

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/hoppscotch/proxyscotch

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2022-25850: Server-side Request Forgery (SSRF) in ProxyScotch 7.5 high 1.0.0 03 May 2022

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/hoppscotch/proxyscotch

Is github.com/hoppscotch/proxyscotch safe to use?

Vulert records 1 vulnerabilities for github.com/hoppscotch/proxyscotch in Go: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/hoppscotch/proxyscotch's Vulert package health score?

Vulert scores github.com/hoppscotch/proxyscotch 69/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/hoppscotch/proxyscotch affected?

Yes. v0.1.4, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/hoppscotch/proxyscotch 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/hoppscotch/proxyscotch have?

1 vulnerability is recorded for github.com/hoppscotch/proxyscotch in the Go ecosystem: 0 critical, 1 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/hoppscotch/proxyscotch vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/hoppscotch/proxyscotch in the last 12 months, and the oldest entry in this database dates to 03 May 2022. 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/hoppscotch/proxyscotch 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/hoppscotch/proxyscotch for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hoppscotch/proxyscotch version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.