Is builtin-status-codes safe to use?

builtin-status-codes has no known vulnerabilities on the latest version (3.0.0). DepScope rates its health at 62/100 (moderate risk).

What is the latest version of builtin-status-codes?

The latest version of builtin-status-codes is 3.0.0, released 2016-06-29.

Does builtin-status-codes have known vulnerabilities?

No known vulnerabilities on the latest version of builtin-status-codes.

Is builtin-status-codes deprecated?

No, builtin-status-codes is actively maintained. Latest release: 3.0.0 (2016-06-29).

What are alternatives to builtin-status-codes?

Popular alternatives to builtin-status-codes in npm include: debug, lru-cache, string-width, commander, picomatch.

What license does builtin-status-codes use?

builtin-status-codes is licensed under MIT.

builtin-status-codes

npmv3.0.0

The map of HTTP status codes from the builtin http module

License MITpermissive3 versions1 maintainers0 deps10,187,221 weekly dl

bendrucker/builtin-status-codes

/ 100

Health

safe to use

[email protected] is safe to use (health: 62/100)

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.5 KBminified

0.8 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Quality signals

Download trend

stable(0%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/builtin-status-codes