@openclaw/fs-safe

Capability-style filesystem roots for Node.js apps that handle untrusted relative paths.

@openclaw/fs-safe@0.26.13 was published on 2026-10-24. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=22.

All @openclaw/fs-safe versions · Permanent reference to 0.26.13

Package specifications

Version0.26.13
License declarationMIT
Published2026-10-24T07:48:44.970Z
Node.js requirement>=22
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count11
Minified size324.82 KiB
Minified + gzip91.16 KiB
Unpacked distribution size3940.29 KiB
Published file count707
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies23
Repository stars62
Repository forks31

Install @openclaw/fs-safe 0.26.13

npm install @openclaw/fs-safe@0.26.13
pnpm add @openclaw/fs-safe@0.26.13
yarn add @openclaw/fs-safe@0.26.13

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

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.

Evidence and freshness