@storybook/react-native
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): Config-file reference in established build tool; stable pattern. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): Config-file reference in established build tool; stable pattern. | ai | |
| phantom-deps | phantom-dep:esbuild-register | AI (phantom-deps): Config-file reference in established build tool; stable pattern. | ai | |
| phantom-deps | phantom-dep:@storybook/global | AI (phantom-deps): Same-org scoped dependency; stable for Storybook packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): glob is a well-known utility; normal dependency addition for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA provenance; legitimate for this org. | ai | |
| dependencies | unvetted-dep:@storybook/mcp | AI (dependencies): First-party @storybook scoped package; consistent with the Storybook ecosystem this package belongs to. | ai | |
| provenance | no-provenance | AI (provenance): Established Storybook package; lack of provenance is consistent across its release history and not a risk signal here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Interop script for loading user config files; stable pattern for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 10.4.4 | 17 / 15 | |
| 10.4.3 | 17 / 15 | |
| 10.4.2 | 17 / 15 | |
| 10.4.1 | 17 / 15 | |
| 10.4.0 | 18 / 13 | |
| 10.3.2 | 17 / 13 | |
| 10.3.1 | 17 / 13 | |
| 10.3.0 | 17 / 13 | |
| 10.2.3 | 12 / 13 | |
| 10.2.2 | 12 / 13 | |
| 10.2.1 | 12 / 13 | |
| 10.2.0 | 12 / 13 | |
| 10.1.11 | 11 / 13 | |
| 10.1.3 | 11 / 13 | |
| 10.1.2 | 11 / 13 | |
| 10.1.1 | 10 / 13 | |
| 10.1.0 | 10 / 13 | |
| 10.0.7 | 10 / 13 | |
| 10.0.6 | 10 / 13 | |
| 10.0.5 | 10 / 13 | |
| 10.0.4 | 10 / 13 | |
| 10.0.3 | 10 / 13 | |
| 10.0.2 | 10 / 13 | |
| 10.0.1 | 10 / 13 | |
| 10.0.0 | 14 / 14 |
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.