expo-file-system 56.0.0-canary-20260409-6fc2991

Provides access to the local file system on the device.

expo-file-system@56.0.0-canary-20260409-6fc2991 was published on 2026-04-09. Its manifest declares 0 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All expo-file-system versions · Permanent reference to 56.0.0-canary-20260409-6fc2991 · Latest release

Package specifications

Version56.0.0-canary-20260409-6fc2991
License declarationMIT
Published2026-04-09T17:16:23.736Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4859.91 KiB
Published file count168
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.ts
Side effects declarationfalse
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars52895
Repository forks14690

Install expo-file-system 56.0.0-canary-20260409-6fc2991

npm install expo-file-system@56.0.0-canary-20260409-6fc2991
pnpm add expo-file-system@56.0.0-canary-20260409-6fc2991
yarn add expo-file-system@56.0.0-canary-20260409-6fc2991

Runtime dependencies

  • None declared

Peer requirements

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.

Maintained10/10 — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Code-Review9/10 — Found 29/30 approved changesets -- score normalized to 9
Security-Policy4/10 — security policy file detected
License10/10 — license file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts0/10 — binaries present in source code
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness