Is content-security-policy safe to use?

content-security-policy has no known vulnerabilities on the latest version (0.3.4). DepScope rates its health at 48/100 (high risk).

What is the latest version of content-security-policy?

The latest version of content-security-policy is 0.3.4, released 2020-08-12.

Does content-security-policy have known vulnerabilities?

No known vulnerabilities on the latest version of content-security-policy.

Is content-security-policy deprecated?

No, content-security-policy is actively maintained. Latest release: 0.3.4 (2020-08-12).

What are alternatives to content-security-policy?

Popular alternatives to content-security-policy in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does content-security-policy use?

License information for content-security-policy is not declared in the registry metadata.

content-security-policy

npmv0.3.4

Middleware to add Content-Security-Policy header.

9 versions1 maintainers0 deps4,192 weekly dl

samuelerdtman/content-security-policy

/ 100

Health

use with caution

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

Moderate health score (48/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.6 KBminified

0.7 KB gzipped

0 direct dependencies

side effects

🌟

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/content-security-policy