@storybook/addon-ondevice-controls
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Storybook org migrated to GitHub Actions CI publishing with SLSA attestation; legitimate pipeline transition. | ai | |
| dependencies | unvetted-dep:@storybook/react-native-ui-common | AI (dependencies): First-party Storybook sibling package; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:react-native-modal-datetime-picker | AI (dependencies): Well-known React Native community package; no malware indicators. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 10.4.4 | 6 / 4 | |
| 10.4.3 | 6 / 4 | |
| 10.4.2 | 6 / 4 | |
| 10.4.1 | 6 / 4 | |
| 10.4.0 | 6 / 4 | |
| 10.3.2 | 6 / 4 | |
| 10.3.1 | 6 / 4 | |
| 10.3.0 | 6 / 4 | |
| 10.2.3 | 6 / 3 | |
| 10.2.2 | 6 / 3 | |
| 10.2.1 | 6 / 3 | |
| 10.2.0 | 6 / 3 | |
| 10.1.11 | 6 / 2 | |
| 10.1.3 | 6 / 2 | |
| 10.1.2 | 6 / 2 | |
| 10.1.1 | 6 / 2 | |
| 10.1.0 | 6 / 2 | |
| 10.0.7 | 6 / 2 | |
| 10.0.6 | 6 / 2 | |
| 10.0.5 | 6 / 2 | |
| 10.0.4 | 6 / 2 | |
| 10.0.3 | 6 / 2 | |
| 10.0.2 | 6 / 2 | |
| 10.0.1 | 5 / 2 | |
| 10.0.0 | 6 / 2 |
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 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.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.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.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.