@expo/configure-splash-screen

Supplementary module for 'expo-splash-screen' providing cli configuration command

@expo/configure-splash-screen@0.6.0 was published on 2021-09-21. Its manifest declares 8 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=12.

All @expo/configure-splash-screen versions · Permanent reference to 0.6.0

Package specifications

Version0.6.0
License declarationMIT
Published2021-09-21T22:03:24.312Z
Node.js requirement>=12
Type declarationsNot declared
Runtime dependency count8
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size256.90 KiB
Published file count92
Package typeNot declared
ES module entryNot declared
Default entry./build/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies36
Repository stars2669
Repository forks473

Install @expo/configure-splash-screen 0.6.0

npm install @expo/configure-splash-screen@0.6.0
pnpm add @expo/configure-splash-screen@0.6.0
yarn add @expo/configure-splash-screen@0.6.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review2/10 — Found 7/30 approved changesets -- score normalized to 2
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Maintained0/10 — project is archived
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts4/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License0/10 — license file not detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Security-Policy0/10 — security policy file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness