@donotdev/expo
React Native/Expo UI components for DoNotDev framework
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:expo | AI (phantom-deps): Expo framework dependency; referenced in config and re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:expo-video | AI (phantom-deps): Expo module; config-referenced and re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:expo-router | AI (phantom-deps): Expo module; config-referenced and re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:expo-clipboard | AI (phantom-deps): Expo module; config-referenced and re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:@expo/vector-icons | AI (phantom-deps): Expo icons library; config-referenced and re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Form resolver; config-referenced and re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:expo-document-picker | AI (phantom-deps): Expo module; config-referenced and re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:react-native-safe-area-context | AI (phantom-deps): Platform-specific binary; re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:@react-native-community/datetimepicker | AI (phantom-deps): Platform-specific binary; re-exported by this UI library. | ai | |
| phantom-deps | phantom-dep:@react-native-async-storage/async-storage | AI (phantom-deps): Platform-specific binary; re-exported by this UI library. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.1.42 | 12 / 0 | |
| 0.1.1 | 14 / 0 | |
| 0.1.0 | 14 / 0 | |
| 0.0.13 | 14 / 0 | |
| 0.0.12 | 14 / 0 | |
| 0.0.11 | 14 / 0 | |
| 0.0.10 | 14 / 0 | |
| 0.0.9 | 14 / 0 | |
| 0.0.8 | 14 / 0 | |
| 0.0.7 | 14 / 0 | |
| 0.0.6 | 14 / 0 | |
| 0.0.5 | 14 / 0 | |
| 0.0.4 | 13 / 0 | |
| 0.0.3 | 13 / 0 | |
| 0.0.2 | 13 / 0 | |
| 0.0.1 | 13 / 0 |
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.