which-package-manager

Detect which package manager is used in the current project

which-package-manager@1.0.1 was published on 2025-03-25. 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 >=18.

All which-package-manager versions · Permanent reference to 1.0.1

Package specifications

Version1.0.1
License declarationMIT
Published2025-03-25T01:14:40.267Z
Node.js requirement>=18
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size15.07 KiB
Published file count5
Package typemodule
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies13
Repository starsUnknown
Repository forksUnknown

Install which-package-manager 1.0.1

npm install which-package-manager@1.0.1
pnpm add which-package-manager@1.0.1
yarn add which-package-manager@1.0.1

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.

Evidence and freshness