expo-file-system 56.0.0-canary-20260506-326540f

Provides access to the local file system on the device.

expo-file-system@56.0.0-canary-20260506-326540f was published on 2026-05-06. 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-20260506-326540f · Latest release

Package specifications

Version56.0.0-canary-20260506-326540f
License declarationMIT
Published2026-05-06T14:01:11.617Z
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 size6339.08 KiB
Published file count182
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.ts
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies0
Repository stars52895
Repository forks14690

Install expo-file-system 56.0.0-canary-20260506-326540f

npm install expo-file-system@56.0.0-canary-20260506-326540f
pnpm add expo-file-system@56.0.0-canary-20260506-326540f
yarn add expo-file-system@56.0.0-canary-20260506-326540f

Runtime dependencies

  • None declared

Peer requirements

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.

    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