which-pm-lockfile

Check if a project uses yarn, npm, or pnpm

which-pm-lockfile@2.1.0 was published on 2023-07-24. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^14.13.1 || >=16.0.0.

All which-pm-lockfile versions · Permanent reference to 2.1.0

Package specifications

Version	2.1.0
License declaration	MIT
Published	2023-07-24T23:44:51.336Z
Node.js requirement	^14.13.1 \|\| >=16.0.0
Type declarations	Bundled declarations
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	7.91 KiB
Published file count	4
Package type	module
ES module entry	Not declared
Default entry	.auto/build/index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	54
Repository stars	2
Repository forks	0

Install which-pm-lockfile 2.1.0

npm install which-pm-lockfile@2.1.0
pnpm add which-pm-lockfile@2.1.0
yarn add which-pm-lockfile@2.1.0

Runtime dependencies

file-structure ^1.6.2
root-pkg-dir ^1.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.

anymatch@3.1.3 — indirect
binary-extensions@2.3.0 — indirect
braces@3.0.3 — indirect
char-to-string@1.0.0 — indirect
chokidar@3.6.0 — indirect
deepmerge@4.3.1 — indirect
detect-newline@3.1.0 — indirect
dir-exists-safe@1.1.0 — indirect
ends-with-string@1.0.1 — indirect
file-exists-safe@1.1.0 — indirect
file-structure@1.6.2 — direct
fill-range@7.1.1 — indirect
fs-safe@1.2.0 — indirect
fsevents@2.3.3 — indirect
glob-parent@5.1.2 — indirect
is-binary-path@2.1.0 — indirect
is-extglob@2.1.1 — indirect
is-glob@4.0.3 — indirect
is-number@7.0.0 — indirect
locate-path@7.2.0 — indirect
make-executable@1.0.2 — indirect
marked@2.1.3 — indirect
marked@4.3.0 — indirect
merge-json-file@1.0.1 — indirect
normalize-path@3.0.0 — indirect
p-limit@4.0.0 — indirect
p-locate@6.0.0 — indirect
parse-json-object@2.0.1 — indirect
parse-lcov@1.0.4 — indirect
picomatch@2.3.2 — indirect
read-dir-safe@1.0.1 — indirect
read-file-safe@1.0.10 — indirect
read-json-safe@2.0.2 — indirect
read-lcov-safe@1.0.2 — indirect
read-md-safe@1.0.5 — indirect
readdirp@3.6.0 — indirect
remove-dir-safe@1.0.1 — indirect
remove-file-safe@1.0.1 — indirect
root-pkg-dir@1.0.0 — direct
root-pkg-json@1.0.2 — indirect
stringify-json-object@1.0.7 — indirect
terminating-newline@1.2.4 — indirect
to-regex-range@5.0.1 — indirect
types-eslintrc@1.0.3 — indirect
types-json@1.2.2 — indirect
types-pkg-json@1.2.1 — indirect
types-tsconfig@1.2.1 — indirect
watch-dir-safe@1.0.2 — indirect
watch-file-safe@1.0.1 — indirect
write-dir-safe@1.0.1 — indirect
write-file-safe@1.3.1 — indirect
write-json-safe@2.1.0 — indirect
write-md-safe@1.2.0 — indirect
yocto-queue@1.2.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	0/10 — Found 0/21 approved changesets -- score normalized to 0
Binary-Artifacts	10/10 — no binaries found in the repo
Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- 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
Security-Policy	0/10 — security policy file not detected
License	0/10 — license 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/which-pm-lockfile/2.1.0 — retrieved 2026-10-31T08:58:37.780Z
https://api.deps.dev/v3/systems/npm/packages/which-pm-lockfile/versions/2.1.0:dependencies — retrieved 2026-10-31T08:58:38.130Z
https://api.deps.dev/v3/systems/npm/packages/which-pm-lockfile/versions/2.1.0 — retrieved 2026-10-31T08:58:38.192Z
https://api.deps.dev/v3/projects/github.com%2Fbconnorwhite%2Fwhich-pm-lockfile — retrieved 2026-10-31T08:58:38.594Z