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

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/1310/24
  1. 25/27 any trust
  2. 25/27 any trust
  3. ...
    25/27 any trust
  4. ...
    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. 25/27 any trust
  17. 25/27 any trust
  18. ... [viewing]
    25/27 any trust
    1. [viewing]
  19. 25/27 any trust
  20. ...
    25/27 any trust
  21. ...
    25/27 any trust
  22. ...
    25/27 any trust
  23. 25/27 any trust
  24. 25/27 any trust
  25. ...
    25/27 any trust
  26. 25/27 any trust
  27. ...
    25/27 any trust
  28. 25/27 any trust
  29. 25/27 any trust
  30. 25/27 any trust
  31. 25/27 any trust
  32. 25/27 any trust
  33. 25/27 any trust
  34. ...
    25/27 any trust
  35. 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-webdriverio5.0.0staged publishGitHub Actions21,710—
vitest-browser-react2.3.0staged publishGitHub Actions992,592—
vitest-browser-vue3.1.0staged publishGitHub Actions133,914—
vitest-browser-svelte3.1.0staged publishGitHub Actions169,921—
@vitest/browser5.0.0staged publishGitHub Actions8,953,494—
vitest5.0.0staged publishGitHub Actions77,062,981—
@vitest/snapshot5.0.0staged publishGitHub Actions72,196,140—
@vitest/expect5.0.0staged publishGitHub Actions84,772,574—
@vitest/spy5.0.0staged publishGitHub Actions91,586,823—
@vitest/pretty-format5.0.0staged publishGitHub Actions93,448,058—
@vitest/mocker5.0.0staged publishGitHub Actions75,632,524—
@vitest/ui5.0.0staged publishGitHub Actions10,290,350—
@vitest/browser-preview5.0.0staged publishGitHub Actions1,003,001—
@vitest/browser-playwright5.0.0staged publishGitHub Actions6,477,833—
@vitest/coverage-v85.0.0staged publishGitHub Actions29,446,354—
@vitest/utils5.0.0staged publishGitHub Actions93,171,572—
@vitest/coverage-istanbul5.0.0staged publishGitHub Actions2,145,798—
@vitest/web-worker5.0.0staged publishGitHub Actions102,752—
@vitest/istanbul-lib-source-maps1.0.1trusted publisherGitHub Actions85,208—
@vitest/istanbul-lib-report1.0.1trusted publisherGitHub Actions2,291,007—
@vitest/istanbul-lib-instrument1.0.1trusted publisherGitHub Actions85,112—
@vitest/istanbul-lib-coverage1.0.1trusted publisherGitHub Actions2,290,232—
@vitest/runner4.1.11staged publishGitHub Actions71,172,481—
@vitest/ws-client4.1.11staged publishGitHub Actions421—
@vitest/eslint-plugin1.6.27noneveritemm2,670,848—
vite-node6.0.0trusted publisherGitHub Actions29,979,703—
@vitest/coverage-c80.33.0noneoreanno97,980DEPRECATED