← Home

msw-storybook-addon

npm Repository
9
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

itadityakettanaitoyannbf

Keywords

storybook-addonapimockhttpgraphqlwebsocketssenetworkrequestintercept

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:is-node-process AI (phantom-deps): Small runtime dep likely consumed in bundled tsup output; not a risk signal. ai
provenance missing-githead AI (provenance): Expected when switching to GitHub Actions trusted publisher flow. ai
publish-pattern dormant-publish AI (publish-pattern): Gap precedes CI/CD migration; provenance confirms legitimate maintainer-driven release. ai

Versions (showing 9 of 9)

Version Deps Published
3.0.0 0 / 18
2.0.7 1 / 6
2.0.6 1 / 6
2.0.5 1 / 6
2.0.4 1 / 6
2.0.3 1 / 6
2.0.2 1 / 6
2.0.1 1 / 6
2.0.0 1 / 6

v3.0.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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.

INFO Publisher changed: kettanaito → GitHub Actions (on 2026-07-24, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (kettanaito) on 2026-07-24, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.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.

v2.0.0

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.