@storybook/semver
The semantic version parser used by npm for browser.
1
Versions
ISC
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
codebyalexdandeanpagoghengeveldkylesussusulprodomyengongregtmeasdaypksunkarandelangenshilmanalexandrebodinhypnosphidanielduanigor-dv
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic require in bin/semver.js reads the nearest package.json via find-up to self-report the CLI version — a standard, benign pattern with no user-controlled input. | ai | |
| provenance | no-provenance | AI (provenance): Highly trusted Storybook publisher with 13,952 approved packages and 0 rejections; absence of provenance is not a meaningful risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 7.3.2 | 2 / 5 |
v7.3.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.