npmreport

npm gives maintainers mechanisms to verifiably establish how a package was published.

Staged publishing
Published through npm's staged flow, prepared and reviewed before it goes live. npm docs ↗
Trusted publisher
Published from CI over OIDC, with no long-lived npm token to leak or steal. npm docs ↗
Provenance
A signed link from the published package back to the exact source commit and build. npm docs ↗
None
No verifiable signal. The release rests on the maintainer's account and token alone, so a compromise there can ship malware unnoticed.

In the summary, staged publishing and trusted publisher both count as strong trust; provenance is a weaker positive; none is the one to check.

Audit of vitest, generated . This is a read-only snapshot.
Run your own audit →

Audit of vitest

Re-run this audit
Tracking daily next
Share to Bluesky

Progress over time

Strong trust
92.6% (25) staged or trusted
Any trust
92.6% (25) incl. provenance
No trust signal
7.4% (2) no trust metadata detected
Strong trust Any trust No trust signal
0%50%100%7/138/249/5
  1. 25/27 any trust
  2. ...
    25/27 any trust
  3. ...
    25/27 any trust
  4. [viewing]
    25/27 any trust
  5. 25/27 any trust
  6. ...
    25/27 any trust
  7. 25/27 any trust
  8. ...
    25/27 any trust
  9. 25/27 any trust
  10. 25/27 any trust
  11. 25/27 any trust
  12. 25/27 any trust
  13. 25/27 any trust
  14. 25/27 any trust
  15. ...
    25/27 any trust
  16. 21/23 any trust
In scope
27
Staged publish
20
Trusted publisher
5
Provenance only
0
No trust signal
2
Deprecated latest
1
27 packages · click a column to sort
Package trust level report
vitest-browser-react2.3.0staged publishGitHub Actions1,296,498—
vitest-browser-vue3.1.0staged publishGitHub Actions136,679—
vitest-browser-svelte3.1.0staged publishGitHub Actions259,440—
@vitest/browser5.0.0staged publishGitHub Actions11,357,661—
vitest5.0.0staged publishGitHub Actions99,878,658—
@vitest/snapshot5.0.0staged publishGitHub Actions101,153,679—
@vitest/expect5.0.0staged publishGitHub Actions?—
@vitest/spy5.0.0staged publishGitHub Actions120,761,869—
@vitest/pretty-format5.0.0staged publishGitHub Actions128,012,591—
@vitest/mocker5.0.0staged publishGitHub Actions98,074,315—
@vitest/ui5.0.0staged publishGitHub Actions12,691,694—
@vitest/browser-preview5.0.0staged publishGitHub Actions?—
@vitest/browser-playwright5.0.0staged publishGitHub Actions8,205,804—
@vitest/coverage-v85.0.0staged publishGitHub Actions?—
@vitest/utils5.0.0staged publishGitHub Actions128,173,015—
@vitest/coverage-istanbul5.0.0staged publishGitHub Actions2,734,957—
@vitest/web-worker5.0.0staged publishGitHub Actions?—
@vitest/istanbul-lib-source-maps1.0.1trusted publisherGitHub Actions1,419—
@vitest/istanbul-lib-report1.0.1trusted publisherGitHub Actions?—
@vitest/istanbul-lib-instrument1.0.1trusted publisherGitHub Actions1,431—
@vitest/istanbul-lib-coverage1.0.1trusted publisherGitHub Actions1,870—
@vitest/runner4.1.11staged publishGitHub Actions99,375,235—
@vitest/ws-client4.1.11staged publishGitHub Actions140—
@vitest/browser-webdriverio4.1.11staged publishGitHub Actions29,430—
@vitest/eslint-plugin1.6.27noneveritemm3,768,501—
vite-node6.0.0trusted publisherGitHub Actions42,247,393—
@vitest/coverage-c80.33.0noneoreanno143,294DEPRECATED

npm.report · No affiliation or endorsement by npm, Inc.

Made by Philippe Serhal