VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@redwoodjs/api: vulnerability history, versions and safety

@redwoodjs/api is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Nov 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 @redwoodjs/api vulnerabilities

Vulert verdict on @redwoodjs/api 8.9.0 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 8.9.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 Nov 2022 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 16 packages i
  • Stars 17,588 i
  • OpenSSF scorecard 4/10 i
  • Last release 12 months ago 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 @redwoodjs/api, 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
8.9.0 21 Oct 2025 none MIT — Details →
8.8.1 14 Aug 2025 none MIT — Details →
8.8.0 20 Jul 2025 none MIT — Details →
8.7.0 20 Jul 2025 none MIT — Details →
8.6.3 01 Jul 2025 none MIT — Details →
8.6.2 01 Jul 2025 none MIT — Details →
8.6.2-next.11 28 Jun 2025 none MIT — Details →
9.0.0-canary.489 28 Jun 2025 none MIT — Details →
9.0.0-canary.488 28 Jun 2025 none MIT — Details →
9.0.0-canary.487 27 Jun 2025 none MIT — Details →
9.0.0-canary.486 26 Jun 2025 none MIT — Details →
9.0.0-canary.485 26 Jun 2025 none MIT — Details →
9.0.0-canary.482 22 Apr 2025 none MIT — Details →
9.0.0-canary.481 09 Apr 2025 none MIT — Details →
9.0.0-canary.480 08 Apr 2025 none MIT — Details →
8.6.2-next.0 03 Apr 2025 none MIT — Details →
8.6.1 03 Apr 2025 none MIT — Details →
8.6.1-next.11 03 Apr 2025 none MIT — Details →
7.7.5 01 Apr 2025 none MIT — Details →
7.7.5-rc.6 01 Apr 2025 none MIT — Details →
9.0.0-canary.476 01 Apr 2025 none MIT — Details →
9.0.0-canary.474 29 Mar 2025 none MIT — Details →
9.0.0-canary.473 29 Mar 2025 none MIT — Details →
9.0.0-canary.472 29 Mar 2025 none MIT — Details →
9.0.0-canary.471 29 Mar 2025 none MIT — Details →
9.0.0-canary.470 29 Mar 2025 none MIT — Details →
9.0.0-canary.469 29 Mar 2025 none MIT — Details →
8.6.1-next.0 25 Mar 2025 none MIT — Details →
8.6.0 25 Mar 2025 none MIT — Details →
8.5.1-next.50 25 Mar 2025 none MIT — Details →
9.0.0-canary.466 24 Mar 2025 none MIT — Details →
9.0.0-canary.465 21 Mar 2025 none MIT — Details →
9.0.0-canary.464 21 Mar 2025 none MIT — Details →
9.0.0-canary.463 21 Mar 2025 none MIT — Details →
9.0.0-canary.462 21 Mar 2025 none MIT — Details →
9.0.0-canary.461 20 Mar 2025 none MIT — Details →
9.0.0-canary.460 20 Mar 2025 none MIT — Details →
9.0.0-canary.459 20 Mar 2025 none MIT — Details →
9.0.0-canary.458 20 Mar 2025 none MIT — Details →
9.0.0-canary.457 20 Mar 2025 none MIT — Details →
9.0.0-canary.456 20 Mar 2025 none MIT — Details →
9.0.0-canary.455 20 Mar 2025 none MIT — Details →
9.0.0-canary.450 19 Mar 2025 none MIT — Details →
9.0.0-canary.449 17 Mar 2025 none MIT — Details →
9.0.0-canary.448 15 Mar 2025 none MIT — Details →
9.0.0-canary.445 15 Mar 2025 none MIT — Details →
9.0.0-canary.444 15 Mar 2025 none MIT — Details →
9.0.0-canary.443 15 Mar 2025 none MIT — Details →
9.0.0-canary.442 15 Mar 2025 none MIT — Details →
9.0.0-canary.441 15 Mar 2025 none MIT — Details →
9.0.0-canary.440 15 Mar 2025 none MIT — Details →
9.0.0-canary.439 14 Mar 2025 none MIT — Details →
9.0.0-canary.438 14 Mar 2025 none MIT — Details →
9.0.0-canary.437 14 Mar 2025 none MIT — Details →
9.0.0-canary.436 14 Mar 2025 none MIT — Details →
9.0.0-canary.435 14 Mar 2025 none MIT — Details →
9.0.0-canary.434 14 Mar 2025 none MIT — Details →
9.0.0-canary.433 14 Mar 2025 none MIT — Details →
9.0.0-canary.431 14 Mar 2025 none MIT — Details →
9.0.0-canary.430 13 Mar 2025 none MIT — Details →
9.0.0-canary.428 27 Feb 2025 none MIT — Details →
9.0.0-canary.427 27 Feb 2025 none MIT — Details →
9.0.0-canary.425 06 Feb 2025 none MIT — Details →
9.0.0-canary.424 06 Feb 2025 none MIT — Details →
9.0.0-canary.423 05 Feb 2025 none MIT — Details →
9.0.0-canary.422 02 Feb 2025 none MIT — Details →
9.0.0-canary.421 02 Feb 2025 none MIT — Details →
9.0.0-canary.417 02 Feb 2025 none MIT — Details →
8.5.1-next.0 26 Jan 2025 none MIT — Details →
8.5.0 26 Jan 2025 none MIT — Details →
8.4.5-next.23 26 Jan 2025 none MIT — Details →
9.0.0-canary.414 26 Jan 2025 none MIT — Details →
9.0.0-canary.412 26 Jan 2025 none MIT — Details →
9.0.0-canary.411 25 Jan 2025 none MIT — Details →
9.0.0-canary.410 25 Jan 2025 none MIT — Details →
9.0.0-canary.409 25 Jan 2025 none MIT — Details →
9.0.0-canary.408 25 Jan 2025 none MIT — Details →
9.0.0-canary.407 24 Jan 2025 none MIT — Details →
9.0.0-canary.406 24 Jan 2025 none MIT — Details →
9.0.0-canary.405 24 Jan 2025 none MIT — Details →
9.0.0-canary.404 24 Jan 2025 none MIT — Details →
9.0.0-canary.403 24 Jan 2025 none MIT — Details →
9.0.0-canary.402 23 Jan 2025 none MIT — Details →
9.0.0-canary.401 21 Jan 2025 none MIT — Details →
9.0.0-canary.400 18 Jan 2025 none MIT — Details →
8.4.5-next.8 18 Jan 2025 none MIT — Details →
9.0.0-canary.399 18 Jan 2025 none MIT — Details →
8.4.5-rc.6 18 Jan 2025 none MIT — Details →
8.4.5-rc.5 18 Jan 2025 none MIT — Details →
8.4.5-rc.4 18 Jan 2025 none MIT — Details →
8.4.5-rc.3 18 Jan 2025 none MIT — Details →
8.4.5-next.7 18 Jan 2025 none MIT — Details →
9.0.0-canary.398 18 Jan 2025 none MIT — Details →
8.4.5-rc.2 18 Jan 2025 none MIT — Details →
9.0.0-canary.397 18 Jan 2025 none MIT — Details →
8.4.5-rc.1 17 Jan 2025 none MIT — Details →
8.4.5-next.5 17 Jan 2025 none MIT — Details →
9.0.0-canary.396 17 Jan 2025 none MIT — Details →
8.4.5-rc.0 17 Jan 2025 none MIT — Details →
8.4.5-next.4 17 Jan 2025 none MIT — Details →
9.0.0-canary.395 17 Jan 2025 none — — Details →
9.0.0-canary.394 17 Jan 2025 none — — Details →
9.0.0-canary.393 17 Jan 2025 none — — Details →
9.0.0-canary.392 17 Jan 2025 none — — Details →
9.0.0-canary.391 17 Jan 2025 none — — Details →
9.0.0-canary.390 17 Jan 2025 none — — Details →
8.4.5-next.0 16 Jan 2025 none — — Details →
8.4.4 16 Jan 2025 none — — Details →
8.4.4-next.0 16 Jan 2025 none — — Details →
8.4.3 16 Jan 2025 none — — Details →
8.4.3-next.115 16 Jan 2025 none — — Details →
9.0.0-canary.386 15 Jan 2025 none — — Details →
8.4.3-next.0 15 Jan 2025 none — — Details →
9.0.0-canary.384 15 Jan 2025 none — — Details →
9.0.0-canary.382 15 Jan 2025 none — — Details →
9.0.0-canary.378 09 Jan 2025 none — — Details →
9.0.0-canary.377 08 Jan 2025 none — — Details →
9.0.0-canary.376 07 Jan 2025 none — — Details →
9.0.0-canary.375 06 Jan 2025 none — — Details →
9.0.0-canary.374 06 Jan 2025 none — — Details →

The newest 120 of 5,000 versions Vulert tracks. 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 @redwoodjs/api

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Account Takeover Vulnerability in RedwoodJS API 8.2 high 2.2.5 10 Nov 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 @redwoodjs/api

Is @redwoodjs/api safe to use?

Vulert records 1 vulnerabilities for @redwoodjs/api 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 @redwoodjs/api's Vulert package health score?

Vulert scores @redwoodjs/api 79/100, which reads as in good shape. 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 @redwoodjs/api affected?

No. 8.9.0, 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 @redwoodjs/api should I use?

8.9.0 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 @redwoodjs/api have?

1 vulnerability is recorded for @redwoodjs/api 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 @redwoodjs/api vulnerabilities disclosed?

0 vulnerabilities were recorded for @redwoodjs/api in the last 12 months, and the oldest entry in this database dates to 10 Nov 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 @redwoodjs/api 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 @redwoodjs/api for upcoming vulnerabilities?

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