npmpackage.info

Gathering detailed insights and metrics for detect-package-manager

Other packages similar to detect-package-manager

package-manager-detector

0.2.5

Package manager detector

preferred-pm

4.0.0

Detects what package manager was used for installation

detect-file

1.0.0

Detects if a file exists and returns the resolved filepath.

@alcalzone/pak

0.11.0

Programmatic wrapper around popular Node.js package managers

Gathering detailed insights and metrics for detect-package-manager

detect-package-manager

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

3.0.2

MIT

TypeScript

421,683,493 3

Installations

npm install detect-package-manager

Score

94.4

Supply Chain

87.6

Quality

78.4

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

5

Total

9

Closed

1

Merged

3

Issues

Open

6

Total

9

Closed

3

Releases

v3.0.2

Published on 05 May 2024

v3.0.1

Published on 04 Sept 2023

v3.0.0

Published on 04 Sept 2023

v2.0.1

Published on 24 Oct 2021

v2.0.0

Published on 24 Oct 2021

View all 5 releases

Developer

egoist

Developer Guide

BETA

Module System

CommonJS, ESM

Min. Node Version

>=12

Typescript Support

Yes

Node Version

20.12.2

NPM Version

10.5.0 Statistics

74 Stars

20 Commits

7 Forks

4 Watching

2 Branches

4 Contributors

Updated on 08 Oct 2024

Languages

TypeScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

421,683,493

Last day

-2.6%

584,265

Compared to previous day

Last week

3.6%

3,019,047

Compared to previous week

Last month

4.4%

12,846,265

Compared to previous month

Last year

15.3%

201,413,782

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

execa

Dev Dependencies

@types/node ava sucrase tsup typescript uvu

Versions

detect-package-manager

How does this work?

When there's yarn.lock, package-lock.json, pnpm-lock.yaml, or bun.lockb in current working directory, it will skip other operations and directly resolve yarn, npm, pnpm, or bun.
When there's no lockfile found, it checks if yarn, pnpm, or bun command exists. If so, it resolves yarn, pnpm, or bun otherwise npm.
Results are cached.

Install

1yarn add detect-package-manager

Usage

1const { detect } = require("detect-package-manager");
2
3detect().then((pm) => {
4  console.log(pm);
5  //=> 'yarn', 'npm', or 'pnpm', 'bun'
6});

API

detect([opts])

Arguments:
- opts.cwd: string Optional, defaults to ., the directory to look up yarn.lock, package-lock.json, or pnpm-lock.yaml.
- opts.includeGlobalBun: boolean Optional, defaults to false, whether to check if bun exists in PATH.
Returns: Promise<PM>

It returns a Promise resolving the name of package manager, could be npm, yarn, or pnpm, bun.

getNpmVersion([pm])

Arguments:
- pm: string Optional, defaults to npm, could be npm, yarn, or pnpm, bun
Returns: Promise<string>

It returns a Promise resolving the version of npm or the package manager you specified.

clearCache()

Returns: void

Clear cache.

Contributing

Fork it!
Create your feature branch: git checkout -b my-new-feature
Commit your changes: git commit -am 'Add some feature'
Push to the branch: git push origin my-new-feature
Submit a pull request :D

Author

detect-package-manager © EGOIST, Released under the MIT License.
Authored and maintained by EGOIST with help from contributors (list).

github.com/egoist · GitHub @EGOIST · Twitter @_egoistlily

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Security-Policy

Determines if the project has published a security policy.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More