camoo/http-header-parser

Tests, release notes, a clear MIT license, and a small dependency footprint improve transparency and adoption confidence. The missing security policy and unpinned workflow actions leave maintenance and build hygiene concerns.

Latest 1.0.1

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both published in June 2023, with no releases in the last 12 months. This is a meaningful sign of inactivity, although the latest release includes documented compatibility and bug fixes.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push in June 2023. This materially increases abandonment risk for a package assessed years after its last development activity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a hygiene gap rather than evidence that the release is unsafe.

Security policy

The repository has no security policy. That weakens vulnerability-reporting transparency, though it is less serious for a small, narrowly scoped parser than for a security-sensitive platform.

Workflow audit

The single workflow was fully analyzed and uses read-only permissions, with no dangerous triggers or audit findings. However, all four referenced actions are unpinned, leaving avoidable build-integrity exposure.