expo-asset 0.0.1-canary-20240415-0868fc4
An Expo universal module to download assets and pass them into other APIs
expo-asset@0.0.1-canary-20240415-0868fc4 was published on 2024-04-15. Its manifest declares 4 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All expo-asset versions · Permanent reference to 0.0.1-canary-20240415-0868fc4 · Latest release
Package specifications
| Version | 0.0.1-canary-20240415-0868fc4 |
|---|---|
| License declaration | MIT |
| Published | 2024-04-15T18:43:20.669Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 4 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 152.29 KiB |
| Published file count | 113 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | build/index.js |
| Side effects declaration | ["*.fx.js","*.fx.web.js"] |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 52895 |
| Repository forks | 14690 |
Install expo-asset 0.0.1-canary-20240415-0868fc4
npm install expo-asset@0.0.1-canary-20240415-0868fc4 pnpm add expo-asset@0.0.1-canary-20240415-0868fc4 yarn add expo-asset@0.0.1-canary-20240415-0868fc4
Runtime dependencies
- md5-file ^3.2.3
- invariant ^2.2.4
- expo-constants 0.0.1-canary-20240415-0868fc4
- @react-native/assets-registry ~0.74.80
Peer requirements
- expo *
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-asset/0.0.1-canary-20240415-0868fc4 — retrieved 2026-10-29T08:11:18.744Z
- https://api.deps.dev/v3/projects/github.com%2Fexpo%2Fexpo — retrieved 2026-10-29T05:55:21.158Z