parse-headers

Build provenancecaution

The release has no build attestation or trusted-publisher provenance, so consumers cannot verify how the published artifact was produced. This lowers release transparency but is not a standalone health failure.

Maintainerscaution

Only one registry publishing maintainer is listed, leaving a thin publishing base and limited redundancy if maintenance stops.

Release historycaution

The package has 11 releases over roughly 12 years, but no release in the last 12 months; the latest release was about 18 months ago. Its long history provides some maturity, but current release momentum is weak.

Repo commit activitycaution

The repository had 0 commits and 0 active maintainers in the last 3 months, indicating no recent development activity. The release in the broader history partly offsets this for a small, stable package, but maintenance capacity is currently unclear.

Security policycaution

The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a hygiene gap rather than evidence that the package is unsafe.