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/269/8
  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. [viewing]
    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
18
Trusted publisher
7
Provenance only
0
No trust signal
2
Deprecated latest
1
27 packages · click a column to sort
Package trust level report
@vitest/istanbul-lib-source-maps1.0.0trusted publisherGitHub Actions445—
@vitest/istanbul-lib-report1.0.0trusted publisherGitHub Actions417—
@vitest/istanbul-lib-instrument1.0.0trusted publisherGitHub Actions?—
@vitest/istanbul-lib-coverage1.0.0trusted publisherGitHub Actions463—
@vitest/coverage-istanbul4.1.11staged publishGitHub Actions?—
vitest4.1.11staged publishGitHub Actions95,242,555—
@vitest/ui4.1.11staged publishGitHub Actions12,447,230—
@vitest/spy4.1.11staged publishGitHub Actions115,282,542—
@vitest/pretty-format4.1.11staged publishGitHub Actions?—
@vitest/utils4.1.11staged publishGitHub Actions122,817,373—
@vitest/mocker4.1.11staged publishGitHub Actions?—
@vitest/runner4.1.11staged publishGitHub Actions94,697,940—
@vitest/snapshot4.1.11staged publishGitHub Actions96,797,212—
@vitest/expect4.1.11staged publishGitHub Actions112,614,783—
@vitest/ws-client4.1.11staged publishGitHub Actions991—
@vitest/browser4.1.11staged publishGitHub Actions9,956,380—
@vitest/browser-playwright4.1.11staged publishGitHub Actions?—
@vitest/browser-preview4.1.11staged publishGitHub Actions970,884—
@vitest/coverage-v84.1.11staged publishGitHub Actions35,936,524—
@vitest/web-worker4.1.11staged publishGitHub Actions145,490—
@vitest/browser-webdriverio4.1.11staged publishGitHub Actions32,144—
@vitest/eslint-plugin1.6.27noneveritemm3,531,408—
vitest-browser-svelte3.0.0staged publishGitHub Actions282,762—
vitest-browser-react2.2.0trusted publisherGitHub Actions1,384,022—
vite-node6.0.0trusted publisherGitHub Actions41,260,411—
vitest-browser-vue2.1.0trusted publisherGitHub Actions136,915—
@vitest/coverage-c80.33.0noneoreanno?DEPRECATED

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

Made by Philippe Serhal