VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@orpc/openapi: vulnerability history, versions and safety

@orpc/openapi is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 45 releases, first recorded in Mar 2026. 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
1 in the last 12 months

Most recent disclosure 20 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @orpc/openapi vulnerabilities

Vulert verdict on @orpc/openapi 1.16.1 i

Updated on 23 Oct 2026

Good news: 1.16.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 1.16.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.16.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.16.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 20 Mar 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Stars 5,693 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 @orpc/openapi, 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
1.16.1 22 Oct 2026 none MIT — Details →
2.0.0-beta.45 22 Oct 2026 none MIT — Details →
1.16.0 21 Oct 2026 none MIT — Details →
2.0.0-beta.44 16 Oct 2026 none MIT — Details →
1.15.7 14 Oct 2026 none MIT — Details →
1.15.6 12 Oct 2026 none MIT — Details →
2.0.0-beta.43 09 Oct 2026 none MIT — Details →
1.15.5 07 Oct 2026 none MIT — Details →
2.0.0-beta.42 04 Oct 2026 none MIT — Details →
2.0.0-beta.41 01 Oct 2026 none MIT — Details →
2.0.0-beta.40 23 Sep 2026 none MIT — Details →
1.15.4 23 Sep 2026 none MIT — Details →
2.0.0-beta.39 23 Sep 2026 none MIT — Details →
2.0.0-beta.38 21 Sep 2026 none MIT — Details →
1.15.3 21 Sep 2026 none MIT — Details →
2.0.0-beta.37 19 Sep 2026 none MIT — Details →
1.15.2 19 Sep 2026 none MIT — Details →
2.0.0-beta.36 16 Sep 2026 none MIT — Details →
1.15.1 15 Sep 2026 none MIT — Details →
2.0.0-beta.35 09 Sep 2026 none MIT — Details →
2.0.0-beta.34 07 Sep 2026 none MIT — Details →
2.0.0-beta.33 05 Sep 2026 none MIT — Details →
2.0.0-beta.32 29 Aug 2026 none MIT — Details →
2.0.0-beta.31 23 Aug 2026 none MIT — Details →
2.0.0-beta.30 21 Aug 2026 none MIT — Details →
2.0.0-beta.29 20 Aug 2026 none MIT — Details →
2.0.0-beta.28 15 Aug 2026 none MIT — Details →
2.0.0-beta.27 13 Aug 2026 none MIT — Details →
1.15.0 08 Aug 2026 none MIT — Details →
2.0.0-beta.26 08 Aug 2026 none MIT — Details →
1.14.15 07 Aug 2026 none MIT — Details →
2.0.0-beta.25 04 Aug 2026 none MIT — Details →
1.14.14 04 Aug 2026 none MIT — Details →
2.0.0-beta.24 03 Aug 2026 none MIT — Details →
2.0.0-beta.23 30 Jul 2026 none MIT — Details →
2.0.0-beta.22 29 Jul 2026 none MIT — Details →
1.14.13 29 Jul 2026 none MIT — Details →
1.14.12 27 Jul 2026 none MIT — Details →
1.14.11 27 Jul 2026 none MIT — Details →
2.0.0-beta.21 26 Jul 2026 none MIT — Details →
1.14.10 25 Jul 2026 none MIT — Details →
1.14.9 25 Jul 2026 none MIT — Details →
2.0.0-beta.20 25 Jul 2026 none MIT — Details →
2.0.0-beta.19 24 Jul 2026 none MIT — Details →
2.0.0-beta.18 16 Jul 2026 none MIT — Details →
2.0.0-beta.17 14 Jul 2026 none MIT — Details →
1.14.8 13 Jul 2026 none MIT — Details →
2.0.0-beta.16 10 Jul 2026 none MIT — Details →
2.0.0-beta.15 06 Jul 2026 none MIT — Details →
1.14.7 06 Jul 2026 none MIT — Details →
2.0.0-beta.14 03 Jul 2026 none MIT — Details →
2.0.0-beta.11 01 Jul 2026 none MIT — Details →
2.0.0-beta.10 30 Jun 2026 none MIT — Details →
2.0.0-beta.9 30 Jun 2026 none MIT — Details →
2.0.0-beta.8 30 Jun 2026 none MIT — Details →
2.0.0-beta.7 27 Jun 2026 none MIT — Details →
2.0.0-beta.6 27 Jun 2026 none MIT — Details →
2.0.0-beta.5 25 Jun 2026 none MIT — Details →
2.0.0-beta.4 25 Jun 2026 none MIT — Details →
2.0.0-beta.3 24 Jun 2026 none MIT — Details →
2.0.0-beta.2 23 Jun 2026 none MIT — Details →
2.0.0-beta.1 21 Jun 2026 none MIT — Details →
1.14.6 12 Jun 2026 none MIT — Details →
0.0.0-next.47dbd93 12 Jun 2026 H1 MIT Yes Details →
0.0.0-next.1463d76 06 Jun 2026 H1 MIT Yes Details →
1.14.5 05 Jun 2026 none MIT — Details →
0.0.0-next.21703c0 05 Jun 2026 H1 MIT Yes Details →
1.14.4 28 May 2026 none MIT — Details →
0.0.0-next.36cf381 28 May 2026 H1 MIT Yes Details →
0.0.0-next.de2bec7 13 May 2026 H1 MIT Yes Details →
1.14.3 12 May 2026 none MIT — Details →
0.0.0-next.7605f6c 12 May 2026 H1 MIT Yes Details →
1.14.2 06 May 2026 none MIT — Details →
0.0.0-next.683f2ee 06 May 2026 H1 MIT Yes Details →
1.14.1 04 May 2026 none MIT — Details →
0.0.0-next.90a4d22 04 May 2026 H1 MIT Yes Details →
1.14.0 22 Apr 2026 none MIT — Details →
0.0.0-next.b6b8746 22 Apr 2026 H1 MIT Yes Details →
0.0.0-next.0ee06ff 17 Apr 2026 H1 MIT Yes Details →
0.0.0-next.6168b40 11 Apr 2026 H1 MIT Yes Details →
1.13.14 09 Apr 2026 none MIT — Details →
0.0.0-next.99d5d75 09 Apr 2026 H1 MIT Yes Details →
0.0.0-next.6a3f818 09 Apr 2026 H1 MIT Yes Details →
0.0.0-next.1bc0bef 05 Apr 2026 H1 MIT Yes Details →
0.0.0-next.dd914a8 03 Apr 2026 H1 MIT Yes Details →
0.0.0-next.5725903 01 Apr 2026 H1 MIT Yes Details →
0.0.0-next.b50e4fc 27 Mar 2026 H1 MIT Yes Details →
0.0.0-next.f8670e3 26 Mar 2026 H1 MIT Yes Details →
1.13.13 26 Mar 2026 none MIT — Details →
0.0.0-next.77e421e 26 Mar 2026 H1 MIT Yes Details →
1.13.12 26 Mar 2026 none MIT — Details →
0.0.0-next.89acf15 26 Mar 2026 H1 MIT Yes Details →
1.13.11 25 Mar 2026 none MIT — Details →
0.0.0-next.672192e 25 Mar 2026 H1 MIT Yes Details →
1.13.10 24 Mar 2026 none MIT — Details →
0.0.0-next.6bc474e 24 Mar 2026 H1 MIT Yes Details →
0.0.0-next.401936e 20 Mar 2026 H1 MIT Yes Details →
1.13.9 19 Mar 2026 none MIT — Details →
0.0.0-next.4f0efa8 19 Mar 2026 H1 MIT Yes Details →
1.13.8 18 Mar 2026 H1 MIT Yes Details →
0.0.0-next.3816dda 18 Mar 2026 H1 — Yes Details →
0.0.0-next.a45fc95 18 Mar 2026 H1 — Yes Details →
0.0.0-next.8812be1 17 Mar 2026 H1 — Yes Details →
0.0.0-next.325aa5d 17 Mar 2026 H1 — Yes Details →
0.0.0-next.62c9665 16 Mar 2026 H1 — Yes Details →
0.0.0-next.70a1a81 15 Mar 2026 H1 — Yes Details →
1.13.7 13 Mar 2026 H1 — Yes Details →
0.0.0-next.5ebcc86 13 Mar 2026 H1 — Yes Details →
0.0.0-next.f4868a1 06 Mar 2026 H1 — Yes Details →
0.0.0-next.2b2e8a0 06 Mar 2026 H1 — Yes Details →
0.0.0-next.a16ca72 06 Mar 2026 H1 — Yes Details →
0.0.0-next.e1d2637 05 Mar 2026 H1 — Yes Details →
0.0.0-next.32bf331 04 Mar 2026 H1 — Yes Details →
0.0.0-next.ba7984f 03 Mar 2026 H1 — Yes Details →
1.13.6 02 Mar 2026 H1 — Yes Details →
0.0.0-next.1dba06f 02 Mar 2026 H1 — Yes Details →
0.0.0-next.dc2afcb 15 Feb 2026 H1 — Yes Details →
0.0.0-next.88bc377 13 Feb 2026 H1 — Yes Details →
1.13.5 11 Feb 2026 H1 — Yes Details →
0.0.0-next.a191873 11 Feb 2026 H1 — Yes Details →

The newest 120 of 1,150 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @orpc/openapi

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33331: Stored XSS Vulnerability in @orpc/openapi via Unescaped JSON.stringify 8.2 high 1.13.9 20 Mar 2026

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 @orpc/openapi

Is @orpc/openapi safe to use?

Vulert records 1 vulnerabilities for @orpc/openapi in npm: 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 @orpc/openapi's Vulert package health score?

Vulert scores @orpc/openapi 88/100, which reads as healthy. 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 @orpc/openapi affected?

No. 1.16.1, 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.

How many vulnerabilities does @orpc/openapi have?

1 vulnerability is recorded for @orpc/openapi in the npm 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 @orpc/openapi vulnerabilities disclosed?

1 vulnerability was recorded for @orpc/openapi in the last 12 months, and the oldest entry in this database dates to 20 Mar 2026. 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 @orpc/openapi 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 @orpc/openapi for upcoming vulnerabilities?

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