Is get-current-package safe to use?

get-current-package has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 36/100 (critical risk).

What is the latest version of get-current-package?

The latest version of get-current-package is 1.0.1, released 2025-01-12.

Does get-current-package have known vulnerabilities?

No known vulnerabilities on the latest version of get-current-package.

Is get-current-package deprecated?

No, get-current-package is actively maintained. Latest release: 1.0.1 (2025-01-12).

What are alternatives to get-current-package?

Popular alternatives to get-current-package in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does get-current-package use?

get-current-package is licensed under MIT.

get-current-package

npmv1.0.1

Get the package.json of the currently executing bin.

License MITpermissive2 versions1 maintainers1 deps

fabiospampinato/get-current-package

/ 100

Health

use with caution

[email protected] low health (36/100) — consider alternatives

Low health score (36/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (1)

find-up-json

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/get-current-package