VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@vrite/sdk: vulnerability history, versions and safety

@vrite/sdk is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 6 releases, first recorded in Oct 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 M2
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 @vrite/sdk vulnerabilities

Vulert verdict on @vrite/sdk 0.5.0-alpha.0 i

Updated on 23 Oct 2026

Good news: 0.5.0-alpha.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

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

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

  • Current release 0.5.0-alpha.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 13 Oct 2023 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 2,005 i
  • Last release 26 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 @vrite/sdk, 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
0.5.0-alpha.0 06 Aug 2024 none MIT — Details →
0.4.10 08 Jul 2024 none MIT — Details →
0.4.9 07 Jul 2024 none MIT — Details →
0.4.8 05 Jul 2024 none MIT — Details →
0.4.8-beta.3 01 Jul 2024 none MIT — Details →
0.4.8-beta.2 28 Jun 2024 none MIT — Details →
0.4.8-beta.1 27 Jun 2024 none MIT — Details →
0.4.7 11 Jun 2024 none MIT — Details →
0.4.6 11 May 2024 none MIT — Details →
0.4.5 07 May 2024 none MIT — Details →
0.4.4 06 May 2024 none MIT — Details →
0.4.3 01 May 2024 none MIT — Details →
0.4.2 17 Apr 2024 none MIT — Details →
0.4.1 29 Feb 2024 none MIT — Details →
0.4.0 06 Feb 2024 none MIT — Details →
0.3.8 06 Feb 2024 none MIT — Details →
0.3.7 05 Feb 2024 none MIT — Details →
0.3.6 05 Feb 2024 none MIT — Details →
0.3.5 31 Jan 2024 none MIT — Details →
0.3.4 31 Jan 2024 none MIT — Details →
0.3.3 30 Jan 2024 none MIT — Details →
0.3.2 29 Jan 2024 none MIT — Details →
0.3.1 22 Jan 2024 none MIT — Details →
0.3.0 10 Oct 2023 none MIT — Details →
0.2.0 13 Sep 2023 C1 M2 MIT Yes Details →
2023.8.18-beta 18 Aug 2023 none MIT — Details →
2023.8.11-beta 11 Aug 2023 none MIT — Details →
2023.7.17-beta 17 Jul 2023 none MIT — Details →
2023.7.13-beta 13 Jul 2023 none MIT — Details →
2023.6.30-beta 30 Jun 2023 none MIT — Details →
2023.6.27-beta 27 Jun 2023 none MIT — Details →
2023.6.26-beta.3 26 Jun 2023 none MIT — Details →
2023.6.26-beta.2 26 Jun 2023 none MIT — Details →
2023.6.26-beta 26 Jun 2023 none MIT — Details →
2023.6.22-beta.4 22 Jun 2023 none MIT — Details →
2023.6.15-beta.4 15 Jun 2023 none MIT — Details →
2023.6.15-beta.3 15 Jun 2023 none MIT — Details →
2023.6.15-beta.2 15 Jun 2023 none MIT — Details →
2023.6.15-beta 15 Jun 2023 none MIT — Details →
2023.6.13-beta 13 Jun 2023 none MIT — Details →
2023.6.9-beta 09 Jun 2023 none MIT — Details →
2023.6.8-beta 08 Jun 2023 none MIT — Details →
2023.5.31-beta 31 May 2023 none MIT — Details →
2023.5.30-beta.2 30 May 2023 none MIT — Details →
2023.5.30-beta 30 May 2023 none MIT — Details →
2023.5.26-beta 26 May 2023 none MIT — Details →
2023.5.23-beta 23 May 2023 none MIT — Details →
2023.5.21-beta 21 May 2023 none MIT — Details →
2023.5.18-beta 18 May 2023 none MIT — Details →
2023.5.17-beta 17 May 2023 none MIT — Details →
2023.5.16-beta 16 May 2023 none MIT — Details →
2023.3.10-beta 10 Mar 2023 none MIT — Details →
0.0.5-beta 07 Mar 2023 C1 M2 MIT Yes Details →
0.0.4-beta 03 Mar 2023 C1 M2 MIT Yes Details →
0.0.3-beta 03 Mar 2023 C1 M2 MIT Yes Details →
0.0.2-beta 01 Mar 2023 C1 M2 MIT Yes Details →
0.0.1-beta 01 Mar 2023 C1 M2 MIT Yes Details →

All 57 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3

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

03 Vulnerabilities

Recorded vulnerabilities for @vrite/sdk

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2023-5572: Server-Side Request Forgery (SSRF) in @vrite/sdk 10.0 critical 0.3.0 13 Oct 2023
CVE-2023-5571: Improper Input Validation in @vrite/sdk 6.5 medium 0.3.0 13 Oct 2023
CVE-2023-5573: Allocation of Resources Without Limits or Throttling in @vrite/sdk 4.7 medium 0.3.0 13 Oct 2023

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 @vrite/sdk

Is @vrite/sdk safe to use?

Vulert records 3 vulnerabilities for @vrite/sdk in npm: 1 critical, 0 high, 2 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 @vrite/sdk's Vulert package health score?

Vulert scores @vrite/sdk 70/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 @vrite/sdk affected?

No. 0.5.0-alpha.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 @vrite/sdk should I use?

0.5.0-alpha.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 @vrite/sdk have?

3 vulnerabilities are recorded for @vrite/sdk in the npm ecosystem: 1 critical, 0 high, 2 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 @vrite/sdk vulnerabilities disclosed?

0 vulnerabilities were recorded for @vrite/sdk in the last 12 months, and the oldest entry in this database dates to 13 Oct 2023. 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 @vrite/sdk 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 @vrite/sdk for upcoming vulnerabilities?

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