dependency-check 1.1.3

checks which modules you have used in your code and then makes sure they are listed as dependencies in your package.json

dependency-check@1.1.3 was published on 2014-06-18. Its manifest declares 7 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: dependency-check has been deprecated in favor of the knip module

All dependency-check versions · Permanent reference to 1.1.3 · Latest release

Package specifications

Version1.1.3
License declarationBSD
Published2014-06-18T00:17:59.532Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count7
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies33
Repository stars547
Repository forks38

Install dependency-check 1.1.3

npm install dependency-check@1.1.3
pnpm add dependency-check@1.1.3
yarn add dependency-check@1.1.3

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.

Code-Review0/10 — Found 0/27 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — project is archived
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy10/10 — security policy file detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License0/10 — license file not detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Branch-Protection3/10 — branch protection is not maximal on development and all release branches

Evidence and freshness