← Home

@storybook/jest

npm Repository Homepage
16
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

thafryershaunlloydkylegachtooppaaandelangenshilmanalexandrebodinhypnosphidanielduanigor-dvpksunkaratmeasdaygongregdomyenusulprokylesussghengeveldpagodandeancodebyalexmrmckebdannyhwwinkervsbecksrvasikarlaamalik2lshadlerphatedyannbfdylanpierceymonkeyworksdarleendenno

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Storybook monorepo uses 0.0.0 placeholder versioning; publisher/downloads confirm legitimacy. ai
phantom-deps phantom-dep:expect AI (phantom-deps): Likely used indirectly/type-only in this instrumentation wrapper; not a malware pattern. ai
source-diff source-size-tripled AI (source-diff): Explained by tsup build config change, not injected payload. ai
typosquat typosquat.levenshtein:next AI (typosquat): @storybook/jest is a scoped Storybook package; Levenshtein proximity to 'next' is coincidental, not a typosquat. ai
phantom-deps phantom-dep:@types/jest AI (phantom-deps): @types/jest is a type-only dependency loaded by convention in TS projects; not a real phantom dep. ai

Versions (showing 16 of 16)

Version Deps Published
0.2.3 4 / 11
0.2.2 4 / 11
0.2.1 4 / 11
0.2.0 4 / 11
0.1.0 4 / 7
0.0.10 4 / 7
0.0.9 4 / 7
0.0.8 4 / 7
0.0.7 4 / 7
0.0.6 3 / 7
0.0.5 3 / 4
0.0.4 3 / 4
0.0.3 4 / 4
0.0.2 4 / 3
0.0.1 4 / 3
0.0.0 4 / 2

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ghengeveld → yannbf (on 2022-02-17, known maintainer) provenance

This version was published by a different npm account (yannbf) than the most recent previously approved version (ghengeveld) on 2022-02-17, but yannbf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ghengeveld → yannbf (on 2022-02-04, known maintainer) provenance

This version was published by a different npm account (yannbf) than the most recent previously approved version (ghengeveld) on 2022-02-04, but yannbf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

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

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

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