VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@replit/crosis: vulnerability history, versions and safety

@replit/crosis is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 88 releases, first recorded in Jan 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 M1
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 @replit/crosis vulnerabilities

Vulert verdict on @replit/crosis 13.7.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 13.7.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 12 Jan 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Last release 8 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 @replit/crosis, 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
13.7.0 27 Jan 2026 none MIT — Details →
13.5.1 11 Apr 2024 none MIT — Details →
13.5.0 22 Mar 2024 none MIT — Details →
13.4.1 21 Mar 2024 none MIT — Details →
13.3.1 20 Nov 2023 none MIT — Details →
13.3.0 20 Nov 2023 none MIT — Details →
13.2.0 08 Aug 2023 none MIT — Details →
13.1.1 08 Jul 2023 none MIT — Details →
13.1.0 07 Jul 2023 none MIT — Details →
13.0.0 06 Jul 2023 none MIT — Details →
12.0.1 08 May 2023 none MIT — Details →
12.0.0 03 Apr 2023 none MIT — Details →
11.0.0 16 Mar 2023 none MIT — Details →
10.2.0 07 Mar 2023 none MIT — Details →
10.1.3 07 Mar 2023 none MIT — Details →
10.1.2 06 Mar 2023 none MIT — Details →
10.1.1 01 Mar 2023 none MIT — Details →
10.1.0 27 Feb 2023 none MIT — Details →
10.0.0 26 Feb 2023 none MIT — Details →
9.2.1 24 Feb 2023 none MIT — Details →
9.2.0 18 Feb 2023 none MIT — Details →
9.1.2 17 Nov 2022 none MIT — Details →
9.1.1 28 Sep 2022 none MIT — Details →
9.1.0 25 Aug 2022 none MIT — Details →
9.0.4 17 Aug 2022 none MIT — Details →
9.0.3 01 Aug 2022 none MIT — Details →
9.0.2 18 Jul 2022 none MIT — Details →
9.0.1 05 Jul 2022 none MIT — Details →
9.0.0 02 Jun 2022 none MIT — Details →
8.0.0 19 May 2022 none MIT — Details →
7.3.2 19 May 2022 none MIT — Details →
7.3.1 07 Jan 2022 none MIT — Details →
7.3.0 17 Dec 2021 M1 MIT Yes Details →
7.2.0 14 Jul 2021 M1 MIT Yes Details →
7.1.1 08 Jul 2021 M1 MIT Yes Details →
7.1.0 05 Jul 2021 M1 MIT Yes Details →
7.0.0 01 Jul 2021 M1 MIT Yes Details →
6.3.0 19 Mar 2021 M1 MIT Yes Details →
6.2.0 16 Mar 2021 M1 MIT Yes Details →
6.1.0 13 Jan 2021 M1 MIT Yes Details →
6.0.4 29 Dec 2020 M1 MIT Yes Details →
6.0.1 29 Dec 2020 M1 MIT Yes Details →
6.0.0 29 Dec 2020 M1 MIT Yes Details →
6.0.0-beta.36 14 Dec 2020 M1 non-standard Yes Details →
6.0.0-beta.35 11 Dec 2020 M1 non-standard Yes Details →
5.2.3 10 Dec 2020 M1 non-standard Yes Details →
5.2.2 23 Nov 2020 M1 non-standard Yes Details →
6.0.0-beta.34 23 Nov 2020 M1 non-standard Yes Details →
5.2.1 19 Nov 2020 M1 non-standard Yes Details →
6.0.0-beta.33 19 Nov 2020 M1 non-standard Yes Details →
6.0.0-beta.32 09 Nov 2020 M1 non-standard Yes Details →
6.0.0-beta.31 02 Nov 2020 M1 non-standard Yes Details →
6.0.0-beta.30 20 Oct 2020 M1 non-standard Yes Details →
6.0.0-beta.29 15 Oct 2020 M1 non-standard Yes Details →
6.0.0-beta.28 18 Sep 2020 M1 non-standard Yes Details →
6.0.0-beta.27 17 Sep 2020 M1 non-standard Yes Details →
6.0.0-beta.26 14 Sep 2020 M1 non-standard Yes Details →
6.0.0-beta.25 11 Sep 2020 M1 non-standard Yes Details →
6.0.0-beta.24 04 Sep 2020 M1 non-standard Yes Details →
5.2.0 04 Sep 2020 M1 non-standard Yes Details →
6.0.0-beta.23 31 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.22 31 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.21 31 Aug 2020 M1 non-standard Yes Details →
5.1.1 18 Aug 2020 M1 non-standard Yes Details →
5.1.0 18 Aug 2020 M1 non-standard Yes Details →
5.0.5 13 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.20 13 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.19 13 Aug 2020 M1 non-standard Yes Details →
5.0.4 11 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.18 11 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.17 11 Aug 2020 M1 non-standard Yes Details →
5.0.3 11 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.16 11 Aug 2020 M1 non-standard Yes Details →
5.0.2 11 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.15 11 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.14 07 Aug 2020 M1 non-standard Yes Details →
6.0.0-beta.13 15 Jul 2020 M1 non-standard Yes Details →
6.0.0-beta.12 14 Jul 2020 M1 non-standard Yes Details →
6.0.0-beta.11 08 Jul 2020 M1 non-standard Yes Details →
6.0.0-beta.10 02 Jul 2020 M1 non-standard Yes Details →
6.0.0-beta.9 29 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.8 29 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.7 29 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.6 26 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.5 23 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.4 23 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.3 22 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.2 19 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.1 16 Jun 2020 M1 non-standard Yes Details →
6.0.0-beta.0 09 Jun 2020 M1 non-standard Yes Details →
5.0.1 15 May 2020 M1 non-standard Yes Details →
4.1.3 14 May 2020 M1 non-standard Yes Details →
4.1.2 14 May 2020 M1 non-standard Yes Details →
4.1.1 14 May 2020 M1 non-standard Yes Details →
4.1.0 13 May 2020 M1 non-standard Yes Details →
4.1.0-beta.0 13 May 2020 M1 non-standard Yes Details →
4.0.1 25 Feb 2020 M1 non-standard Yes Details →
4.0.0 25 Feb 2020 M1 non-standard Yes Details →
3.0.2 18 Feb 2020 M1 non-standard Yes Details →
3.0.1-beta.2 14 Feb 2020 M1 non-standard Yes Details →
3.0.1-beta.0 14 Feb 2020 M1 — Yes Details →
2.3.0 29 Jan 2020 M1 — Yes Details →
2.2.0 05 Dec 2019 M1 — Yes Details →
2.1.0 31 Oct 2019 M1 — Yes Details →
2.0.1 17 Oct 2019 M1 — Yes Details →
2.0.0 17 Oct 2019 M1 — Yes Details →
1.0.5 15 Oct 2019 M1 — Yes Details →
1.0.4 15 Oct 2019 M1 — Yes Details →
1.0.3 14 Oct 2019 M1 — Yes Details →
1.0.2 14 Oct 2019 M1 — Yes Details →
1.0.1 14 Oct 2019 M1 — Yes Details →
0.3.2 10 Oct 2019 M1 — Yes Details →
0.3.1 10 Oct 2019 M1 — Yes Details →
0.3.0 10 Oct 2019 M1 — Yes Details →
0.2.0 10 Oct 2019 M1 — Yes Details →
0.1.3 03 Oct 2019 M1 — Yes Details →
0.1.2 01 Oct 2019 M1 — Yes Details →
0.1.1 21 Sep 2019 M1 — Yes Details →
0.1.0 21 Sep 2019 M1 — Yes Details →
0.0.1 21 Sep 2019 M1 — Yes Details →

All 120 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 @replit/crosis

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-21671: Potential exposure of tokens to an Unauthorized Actor in @replit/crosis 6.5 medium 7.3.1 12 Jan 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 @replit/crosis

Is @replit/crosis safe to use?

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

Vulert scores @replit/crosis 82/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 @replit/crosis affected?

No. 13.7.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 @replit/crosis should I use?

13.7.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 @replit/crosis have?

1 vulnerability is recorded for @replit/crosis in the npm ecosystem: 0 critical, 0 high, 1 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 @replit/crosis vulnerabilities disclosed?

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

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