← Home

@applicaster/zapplicaster-cli

npm Repository Homepage

CLI Tool for the zapp app and Quick Brick project

9
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

applicaster-devsmeirmanrzapp-ciapplicaster-external-devs

Keywords

ApplicasterZappCLIQuick Brick

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@applicaster/zapp-react-dom-cli-template AI (phantom-deps): Same-org CLI template; likely loaded dynamically by the CLI tool rather than statically imported. ai
phantom-deps phantom-dep:@applicaster/zapp-react-native-cli-template AI (phantom-deps): Same-org CLI template; likely loaded dynamically by the CLI tool rather than statically imported. ai
phantom-deps phantom-dep:@applicaster/zapp-react-native-tvos-cli-template AI (phantom-deps): Same-org CLI template; likely loaded dynamically by the CLI tool rather than statically imported. ai
phantom-deps phantom-dep:@applicaster/zapp-react-native-android-tv-cli-template AI (phantom-deps): Same-org CLI template; likely loaded dynamically by the CLI tool rather than statically imported. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Referenced in config files; stable false positive for this CLI package. ai
semgrep semgrep:dynamic-require AI (semgrep): CLI tool loading package.json and user-specified modules by design; pattern is stable across versions. ai

Versions (showing 9 of 9)

Version Deps Published
14.0.28 15 / 0
14.0.27 15 / 0
14.0.26 15 / 0
14.0.25 15 / 0
14.0.24 15 / 0
14.0.23 15 / 0
14.0.21 15 / 0
14.0.20 15 / 0
14.0.19 15 / 0

v14.0.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.23

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.