@storybook/addon-onboarding
Storybook Onboarding: Help new users learn how to write stories
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/Onboarding-C7P3S53K.js | AI (source-diff): Standard bundler minification output for a Storybook UI addon; not malicious obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): storybook-bot is the known Storybook CI publisher with a large approved track record; transition from GitHub Actions is expected. | ai | |
| source-diff | obfuscated-file:dist/Onboarding-INVFN5QI.js | AI (source-diff): Standard esbuild minified bundle output for a Storybook addon; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/Onboarding-LKCUBABR.js | AI (source-diff): Standard bundler minification output for a Storybook addon; not obfuscation. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 10.4.6 | 0 / 6 | |
| 10.4.5 | 0 / 6 | |
| 10.4.4 | 0 / 6 | |
| 10.4.3 | 0 / 6 | |
| 10.4.2 | 0 / 6 | |
| 10.4.1 | 0 / 6 | |
| 10.4.0 | 0 / 6 | |
| 10.3.6 | 0 / 6 | |
| 10.3.5 | 0 / 6 | |
| 10.3.4 | 0 / 6 | |
| 10.3.3 | 0 / 6 | |
| 10.3.2 | 0 / 6 | |
| 10.3.1 | 0 / 6 | |
| 10.3.0 | 0 / 6 | |
| 10.2.19 | 0 / 6 | |
| 10.2.18 | 0 / 6 | |
| 10.2.17 | 0 / 6 | |
| 10.2.16 | 0 / 6 | |
| 10.2.15 | 0 / 6 | |
| 10.2.14 | 0 / 6 | |
| 10.2.13 | 0 / 6 | |
| 10.2.12 | 0 / 6 | |
| 10.2.11 | 0 / 6 | |
| 10.2.10 | 0 / 6 | |
| 10.2.9 | 0 / 6 | |
| 10.2.8 | 0 / 6 | |
| 10.2.7 | 0 / 6 | |
| 10.2.6 | 0 / 6 | |
| 10.2.5 | 0 / 6 | |
| 10.2.4 | 0 / 6 | |
| 10.2.3 | 0 / 6 | |
| 10.2.2 | 0 / 6 | |
| 10.2.1 | 0 / 6 | |
| 10.2.0 | 0 / 6 | |
| 10.1.11 | 0 / 6 | |
| 10.1.10 | 0 / 6 | |
| 10.1.9 | 0 / 6 | |
| 10.1.8 | 0 / 6 | |
| 10.1.7 | 0 / 6 | |
| 10.1.6 | 0 / 6 | |
| 10.1.5 | 0 / 6 | |
| 10.1.4 | 0 / 6 | |
| 10.1.3 | 0 / 6 | |
| 10.1.2 | 0 / 6 | |
| 10.1.1 | 0 / 6 | |
| 10.1.0 | 0 / 6 | |
| 10.0.8 | 0 / 6 | |
| 10.0.7 | 0 / 6 | |
| 10.0.6 | 0 / 6 | |
| 10.0.5 | 0 / 6 | |
| 10.0.4 | 0 / 6 |
v10.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.