valid-directory 1.1.0

Check whether or not a directory and its descendants are valid

valid-directory@1.1.0 was published on 2019-11-13. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.

All valid-directory versions · Permanent reference to 1.1.0 · Latest release

Package specifications

Version1.1.0
License declarationMIT
Published2019-11-13T07:20:10.074Z
Node.js requirement>=8
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size17.30 KiB
Published file count8
Package typeNot declared
ES module entryNot declared
Default entrysource/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies6
Repository stars1
Repository forks0

Install valid-directory 1.1.0

npm install valid-directory@1.1.0
pnpm add valid-directory@1.1.0
yarn add valid-directory@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.

Maintained4/10 — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review0/10 — Found 0/10 approved changesets -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy10/10 — security policy file detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST6/10 — SAST tool is not run on all commits -- score normalized to 6

Evidence and freshness