@applicaster/zapp-react-native-ui-components
Applicaster Zapp React Native ui components for the Quick Brick App
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-router-native | AI (dependencies): react-router-native is a well-known routing library; its use in a React Native UI components package is expected and benign. | ai | |
| phantom-deps | phantom-dep:react-router-native | AI (phantom-deps): Platform-specific or re-exported dep; phantom import is expected in a UI components library. | ai | |
| dependencies | unvetted-dep:@applicaster/applicaster-types | AI (dependencies): Same-org monorepo dependency; consistent versioning pattern across all @applicaster/* packages. | ai | |
| dependencies | unvetted-dep:@applicaster/zapp-react-native-redux | AI (dependencies): Same-org monorepo dependency; consistent versioning pattern across all @applicaster/* packages. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo publisher; provenance absence is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@applicaster/applicaster-types | AI (phantom-deps): Same-org type-only package; phantom-dep false positive for TypeScript type declarations. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 14.0.28 | 8 / 0 | |
| 14.0.27 | 8 / 0 | |
| 14.0.26 | 8 / 0 | |
| 14.0.25 | 8 / 0 | |
| 14.0.24 | 8 / 0 | |
| 14.0.23 | 8 / 0 | |
| 14.0.22 | 8 / 0 | |
| 14.0.21 | 8 / 0 | |
| 14.0.20 | 8 / 0 | |
| 14.0.19 | 8 / 0 | |
| 14.0.15 | 8 / 0 | |
| 14.0.10 | 8 / 0 | |
| 13.0.19 | 8 / 1 |
v14.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.