Is next-secure-headers safe to use?

next-secure-headers has no known vulnerabilities on the latest version (2.2.0). DepScope rates its health at 41/100 (high risk).

What is the latest version of next-secure-headers?

The latest version of next-secure-headers is 2.2.0, released 2021-02-25.

Does next-secure-headers have known vulnerabilities?

No known vulnerabilities on the latest version of next-secure-headers.

Is next-secure-headers deprecated?

No, next-secure-headers is actively maintained. Latest release: 2.2.0 (2021-02-25).

What are alternatives to next-secure-headers?

Popular alternatives to next-secure-headers in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does next-secure-headers use?

next-secure-headers is licensed under MIT.

next-secure-headers

npmv2.2.0

Sets secure response headers for Next.js.

License MITpermissive5 versions1 maintainers0 deps

jagaapple/next-secure-headers

/ 100

Health

use with caution

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

Moderate health score (41/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/next-secure-headers