@storybook/addon-console
Show console output like logs, errors, and warnings in the Storybook
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from usulpro to ndelangen reflects legitimate Storybook org takeover; ndelangen is a known Storybook core maintainer with strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are recognized Storybook team members; this is a legitimate organizational transfer of a community addon to the Storybook core team. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @storybook/global is the Storybook org's own scoped replacement for the 'global' package; a routine internal ecosystem migration, not a suspicious dependency. | ai | |
| dependencies | unvetted-dep:@storybook/global | AI (dependencies): @storybook/global is a first-party Storybook org package used widely across the Storybook ecosystem; not a real risk for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher ndelangen is a core Storybook maintainer with 13,930 approved packages; maintainer consolidation is expected for Storybook org packages. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 1 / 44 | |
| 2.0.0 | 1 / 42 | |
| 1.2.3 | 1 / 33 | |
| 1.2.2 | 1 / 34 | |
| 1.2.1 | 1 / 34 | |
| 1.2.0 | 1 / 34 | |
| 1.1.1 | 1 / 47 | |
| 1.1.0 | 1 / 47 | |
| 1.0.10 | 1 / 47 | |
| 1.0.9 | 1 / 49 | |
| 1.0.8 | 1 / 49 | |
| 1.0.7 | 1 / 49 | |
| 1.0.6 | 1 / 49 | |
| 1.0.5 | 1 / 49 | |
| 1.0.4 | 1 / 34 | |
| 1.0.3 | 2 / 33 | |
| 1.0.2 | 2 / 33 | |
| 1.0.1 | 2 / 33 | |
| 1.0.0 | 1 / 33 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-05-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.