strip-dirs

Remove leading directory components from a path, like tar's --strip-components option

strip-dirs@3.0.0 was published on 2018-09-14. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All strip-dirs versions · Permanent reference to 3.0.0

Package specifications

Version3.0.0
License declarationISC
Published2018-09-14T02:43:06.645Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size6.11 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies3
Repository stars8
Repository forks1

Install strip-dirs 3.0.0

npm install strip-dirs@3.0.0
pnpm add strip-dirs@3.0.0
yarn add strip-dirs@3.0.0

Runtime dependencies

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.

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.

SAST0/10 — no SAST tool detected
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness