detect-package-manager 1.0.0

Detect which package you're using (yarn or npm)

detect-package-manager@1.0.0 was published on 2017-08-11. 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 detect-package-manager versions · Permanent reference to 1.0.0 · Latest release

Package specifications

Version	1.0.0
License declaration	MIT
Published	2017-08-11T14:59:12.111Z
Node.js requirement	Not declared
Type declarations	Not declared
Runtime dependency count	2
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	Not supplied
Published file count	Not supplied
Package type	Not declared
ES module entry	Not declared
Default entry	index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	17
Repository stars	89
Repository forks	11

Install detect-package-manager 1.0.0

npm install detect-package-manager@1.0.0
pnpm add detect-package-manager@1.0.0
yarn add detect-package-manager@1.0.0

Runtime dependencies

execa ^0.8.0
path-exists ^3.0.0

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.

cross-spawn@5.1.0 — indirect
execa@0.8.0 — direct
get-stream@3.0.0 — indirect
is-stream@1.1.0 — indirect
isexe@2.0.0 — indirect
lru-cache@4.1.5 — indirect
npm-run-path@2.0.2 — indirect
p-finally@1.0.0 — indirect
path-exists@3.0.0 — direct
path-key@2.0.1 — indirect
pseudomap@1.0.2 — indirect
shebang-command@1.2.0 — indirect
shebang-regex@1.0.0 — indirect
signal-exit@3.0.7 — indirect
strip-eof@1.0.0 — indirect
which@1.3.1 — indirect
yallist@2.1.2 — indirect

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-Review	1/10 — Found 3/20 approved changesets -- score normalized to 1
Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts	10/10 — no binaries found in the repo
Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies	0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing	0/10 — project is not fuzzed
License	10/10 — license file detected
Security-Policy	0/10 — security policy file not detected
Branch-Protection	0/10 — branch protection not enabled on development/release branches
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/detect-package-manager/1.0.0 — retrieved 2026-10-29T22:15:38.678Z
https://api.deps.dev/v3/projects/github.com%2Fegoist%2Fdetect-package-manager — retrieved 2026-10-29T19:53:46.329Z
https://api.deps.dev/v3/systems/npm/packages/detect-package-manager/versions/1.0.0 — retrieved 2026-10-29T22:15:39.177Z
https://api.deps.dev/v3/systems/npm/packages/detect-package-manager/versions/1.0.0:dependencies — retrieved 2026-10-29T22:15:39.206Z