nieuwenhuizen/content-security-policy

Release historydanger

The package is over eight years old, has only three releases, and has had no release in the last 12 months; the latest release was in August 2018. This is strong evidence of abandonment risk despite the short initial release interval.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. No provided maintenance signal compensates for this inactivity.

Repo popularitycaution

The repository has only two stars and one fork, indicating a small user and contributor footprint. Popularity is supporting evidence rather than decisive, but it provides no reassurance against the maintenance concerns.

Repo toolingcaution

The project uses Composer, but no security-scanning tooling was detected. This is a modest hygiene gap, not a standalone adoption blocker, because the package has no detected install-time scripts or dangerous workflows.

Security policycaution

The repository has no security policy. For a package that changes HTTP security headers, the absence of documented vulnerability-reporting guidance is a genuine transparency gap, though it is less serious than the maintenance inactivity.