@applicaster/zapp-react-dom-app
Zapp App Component for Applicaster's Quick Brick React Native 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:@applicaster/zapp-react-dom-ui-components | AI (dependencies): Internal Applicaster dependency; same publisher and ecosystem as this package. | ai | |
| dependencies | unvetted-dep:@applicaster/zapp-react-native-redux | AI (dependencies): Internal Applicaster dependency; same publisher and ecosystem as this package. | ai | |
| dependencies | unvetted-dep:videojs-contrib-eme | AI (dependencies): Standard videojs EME plugin; consistent with this package's video player functionality. | ai | |
| provenance | no-provenance | AI (provenance): Long-established Applicaster package; lack of Sigstore provenance is consistent across all 5518 versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:react-router-dom | AI (phantom-deps): react-router-dom is a declared dep used via config/routing setup; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:video.js | AI (phantom-deps): video.js is a declared runtime dep used via config; phantom-dep heuristic fires on config-referenced packages. | ai | |
| phantom-deps | phantom-dep:typeface-montserrat | AI (phantom-deps): Font package declared as dep, referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:videojs-contrib-quality-levels | AI (phantom-deps): videojs plugin declared as dep, referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:videojs-contrib-eme | AI (phantom-deps): videojs plugin declared as dep, referenced in config files; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 14.0.28 | 10 / 0 | |
| 14.0.24 | 10 / 0 | |
| 14.0.23 | 10 / 0 | |
| 14.0.21 | 10 / 0 | |
| 14.0.20 | 10 / 0 | |
| 14.0.19 | 10 / 0 | |
| 14.0.18 | 10 / 0 | |
| 14.0.16 | 10 / 0 | |
| 14.0.14 | 10 / 0 | |
| 14.0.10 | 10 / 0 | |
| 14.0.0 | 10 / 0 | |
| 13.0.22 | 11 / 0 | |
| 13.0.19 | 11 / 0 | |
| 13.0.18 | 11 / 0 |
v14.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.