expo-modules-cli 0.4.0
Command-line tools for developing Expo modules.
expo-modules-cli@0.4.0 was published on 2026-10-28. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^22.13.0 || ^24.3.0 || ^26.0.0 || >=27.0.0.
All expo-modules-cli versions · Permanent reference to 0.4.0 · Latest release
Package specifications
| Version | 0.4.0 |
|---|---|
| License declaration | MIT |
| Published | 2026-10-28T15:31:34.614Z |
| Node.js requirement | ^22.13.0 || ^24.3.0 || ^26.0.0 || >=27.0.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 139.57 KiB |
| Published file count | 43 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | build/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | Unknown |
| Repository stars | 52895 |
| Repository forks | 14690 |
Install expo-modules-cli 0.4.0
npm install expo-modules-cli@0.4.0 pnpm add expo-modules-cli@0.4.0 yarn add expo-modules-cli@0.4.0
Runtime dependencies
- arg ^5.0.2
- @babel/parser ^7.20.0
Peer requirements
- None declared
Optional dependencies
- None declared
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.
| Maintained | 10/10 — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10 |
|---|---|
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Code-Review | 9/10 — Found 29/30 approved changesets -- score normalized to 9 |
| Security-Policy | 4/10 — security policy file detected |
| License | 10/10 — license file detected |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Branch-Protection | 6/10 — branch protection is not maximal on development and all release branches |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 0/10 — binaries present in source code |
| Pinned-Dependencies | 9/10 — dependency not pinned by hash detected -- score normalized to 9 |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/expo-modules-cli/0.4.0 — retrieved 2026-10-29T07:55:02.282Z
- https://api.deps.dev/v3/projects/github.com%2Fexpo%2Fexpo — retrieved 2026-10-29T05:55:21.158Z
- https://api.deps.dev/v3/systems/npm/packages/expo-modules-cli/versions/0.4.0 — retrieved 2026-10-29T07:11:32.726Z (stale snapshot; refresh pending)