Vulnerability Database · npm · Package report

cross-inspect: vulnerability history, versions and safety

cross-inspect is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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.

Vulert verdict on cross-inspect 1.0.1 i

Updated on 23 Oct 2026

Good news: 1.0.1, the version you would install today, has no known vulnerabilities.

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

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

  • Current release 1.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 3,945 packages i
  • Stars 5,431 i
  • OpenSSF scorecard 4/10 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 cross-inspect, 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.0.1 05 Aug 2024 none MIT — Details →
1.0.1-rc-20240805200723-05722a8db4c5d6b61f087c9a81931f2efdc22cc1 05 Aug 2024 none MIT — Details →
1.0.1-rc-20240805200709-dfb59efa07ffcd5dba64fb8a16e7dbd47c2b0cfc 05 Aug 2024 none MIT — Details →
1.0.1-alpha-20240805200235-c7ec3748aa84fdf34ade7fa8c5f9a10a439cc688 05 Aug 2024 none MIT — Details →
1.0.1-alpha-20240805184116-0f12e0fea47a26c4d56877ed4a31af0a018ddb66 05 Aug 2024 none MIT — Details →
1.0.1-alpha-20240805183929-288c79141f31a8a877b5661a0d113cfcc20ae516 05 Aug 2024 none MIT — Details →
1.0.1-alpha-20240805145013-cd51a6957acc0c14e544e4f6c88c079df724c95e 05 Aug 2024 none MIT — Details →
1.0.1-alpha-20240805144842-131e76d507ce82e59a400bf90758e7af71493abf 05 Aug 2024 none MIT — Details →
1.0.1-rc-20240805094438-2541307bfcd1eb18776e26b4cd27c5a5cfad7463 05 Aug 2024 none MIT — Details →
1.0.1-alpha-20240805093025-467ef011556bf91b23bb3a131d0266f17b53fc19 05 Aug 2024 none MIT — Details →
1.0.1-rc-20240805092858-4b3228b201fba7e1b3396a09d178c0b037d5cd18 05 Aug 2024 none MIT — Details →
1.0.1-alpha-20240805061223-1b9bef312682f34a7144cff366c6588479087321 05 Aug 2024 none MIT — Details →
1.0.1-rc-20240804213606-fa5380888e3647e23f4943d22422c0726d8f55a4 04 Aug 2024 none MIT — Details →
1.0.0-alpha-20231115101413-0c437430 15 Nov 2023 none MIT — Details →
1.0.0-alpha-20231114144041-561a3a1b 14 Nov 2023 none MIT — Details →
1.0.0-alpha-20231114143259-fe29f508 14 Nov 2023 none MIT — Details →
1.0.0-alpha-20231114142013-8f8a34cf 14 Nov 2023 none MIT — Details →
1.0.0-alpha-20231114121221-b31e9c6a 14 Nov 2023 none MIT — Details →
1.0.0-alpha-20231114113214-4a02e22f 14 Nov 2023 none MIT — Details →
1.0.0-alpha-20231110114700-8cab08a0 10 Nov 2023 none MIT — Details →
1.0.0-alpha-20231108155036-4f89aba8 08 Nov 2023 none MIT — Details →
1.0.0-alpha-20231107131728-873949ac 07 Nov 2023 none MIT — Details →
1.0.0 30 Oct 2023 none MIT — Details →
1.0.0-rc-20231030103405-c17b32c4 30 Oct 2023 none MIT — Details →
1.0.0-rc-20231030102248-62950362 30 Oct 2023 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for cross-inspect

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 cross-inspect

Is cross-inspect safe to use?

Vulert has no vulnerabilities on record for cross-inspect in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is cross-inspect's Vulert package health score?

Vulert scores cross-inspect 71/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 cross-inspect affected?

No. 1.0.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.

Which version of cross-inspect should I use?

1.0.1 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 cross-inspect have?

0 vulnerabilities are recorded for cross-inspect in the npm ecosystem: 0 critical, 0 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 cross-inspect vulnerabilities disclosed?

0 vulnerabilities were recorded for cross-inspect in the last 12 months. 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 cross-inspect 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 cross-inspect for upcoming vulnerabilities?

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