expo 0.1.3
expo@0.1.3 was published on 2013-06-12. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.8.0.
All expo versions · Permanent reference to 0.1.3 · Latest release
Package specifications
| Version | 0.1.3 |
|---|---|
| License declaration | Not declared |
| Published | 2013-06-12T19:44:23.900Z |
| Node.js requirement | >=0.8.0 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index |
| Side effects declaration | Not declared |
| Direct advisories | 2 |
| Resolved graph dependencies | 8 |
| Repository stars | 52895 |
| Repository forks | 14690 |
Install expo 0.1.3
npm install expo@0.1.3 pnpm add expo@0.1.3 yarn add expo@0.1.3
Runtime dependencies
- js-yaml 2.x
- commander 1.1.x
- supervisor 0.5.x
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.
- argparse@0.1.16 — indirect
- commander@1.1.1 — direct
- esprima@1.0.4 — indirect
- js-yaml@2.1.3 — direct
- keypress@0.1.0 — indirect
- supervisor@0.5.7 — direct
- underscore@1.7.0 — indirect
- underscore.string@2.4.0 — indirect
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.
Known direct advisories
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/0.1.3 — retrieved 2026-10-29T11:06:55.203Z
- 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/versions/0.1.3 — retrieved 2026-10-29T11:06:55.718Z
- https://api.deps.dev/v3/systems/npm/packages/expo/versions/0.1.3:dependencies — retrieved 2026-10-29T11:06:55.740Z