Is @octotask/get-private-key safe to use?

@octotask/get-private-key has no known vulnerabilities on the latest version (1.1.2). DepScope rates its health at 38/100 (critical risk).

What is the latest version of @octotask/get-private-key?

The latest version of @octotask/get-private-key is 1.1.2, released 2024-11-17.

Does @octotask/get-private-key have known vulnerabilities?

No known vulnerabilities on the latest version of @octotask/get-private-key.

Is @octotask/get-private-key deprecated?

No, @octotask/get-private-key is actively maintained. Latest release: 1.1.2 (2024-11-17).

What are alternatives to @octotask/get-private-key?

Popular alternatives to @octotask/get-private-key in npm include: ?, semver, debug, ansi-styles, brace-expansion.

What license does @octotask/get-private-key use?

@octotask/get-private-key is licensed under ISC.

@octotask/get-private-key

npmv1.1.2

Get private key from a path, environment variables, or a `*.pem` file in the current working directory

License ISCpermissive1 versions1 maintainers0 deps7 weekly dl

octotask/get-private-key

/ 100

Health

use with caution

@octotask/[email protected] low health (38/100) — consider alternatives

Moderate health score (38/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@octotask/get-private-key