readdir-scoped-modules

Like `fs.readdir` but handling `@org/module` dirs as if they were a single entry.

readdir-scoped-modules@1.1.0 was published on 2019-06-28. Its manifest declares 4 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.

Deprecated: This functionality has been moved to @npmcli/fs

All readdir-scoped-modules versions · Permanent reference to 1.1.0

Package specifications

Version1.1.0
License declarationISC
Published2019-06-28T19:01:48.455Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4.81 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entryreaddir.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies6
Repository stars3
Repository forks6

Install readdir-scoped-modules 1.1.0

npm install readdir-scoped-modules@1.1.0
pnpm add readdir-scoped-modules@1.1.0
yarn add readdir-scoped-modules@1.1.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.

Maintained0/10 — project is archived
Code-Review0/10 — Found 1/15 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy0/10 — security policy file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness