← Home

expo-splash-screen-command

npm Repository Homepage

Supplementary module for 'expo-splash-screen' providing installation command

4
Versions
MIT
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

brentvatne

Keywords

react-nativeexpoexpo-splash-screenexpo-splash-screen-command

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@expo/commander AI (dependencies): @expo/commander is Expo's own fork of commander, used throughout the official Expo toolchain. Expected dependency for this package. ai
publish-pattern rapid-publish AI (publish-pattern): Expo monorepo releases publish many packages in rapid succession via automated pipelines; rapid publish is expected and not a malicious signal for this publisher. ai
phantom-deps phantom-dep:inquirer AI (phantom-deps): inquirer is a declared runtime dependency in package.json for this CLI tool; phantom-dep finding reflects indirect/conditional usage, not a real risk. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.3 9 / 4
0.1.2 10 / 3
0.1.1 10 / 3
0.1.0 10 / 3

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

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.