← Home

flags

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

matheussmatt.strakavercel-release-botzeit-bot

Keywords

feature flagsNext.jsreacttoolbaroverridesSvelteKit

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Vercel migrated publishing to GitHub Actions CI with SLSA attestation; consistent with org-level CI pipeline change. ai
maintainer-change maintainer-added AI (maintainer-change): matheuss is a known Vercel engineer; maintainer rotation within Vercel org is expected. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer rotation within Vercel org; no indication of hostile takeover given SLSA attestation and unchanged repo. ai

Versions (showing 7 of 7)

Version Deps Published
4.1.0 2 / 10
4.0.6 2 / 10
4.0.5 2 / 10
4.0.4 2 / 10
4.0.3 2 / 11
4.0.2 2 / 11
4.0.1 2 / 13

v4.1.0

2 findings
HIGH Publisher changed: vercel-release-bot → GitHub Actions (on 2026-06-05) provenance

This version was published by a different npm account than previous versions on 2026-06-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.