http-status-codes

Build provenancecaution

No build attestation or trusted-publisher provenance is present, so consumers have less evidence connecting the published artifact to its source build.

Maintainerscaution

Only one registry account has publish access, leaving a thin publishing base even though the linked repository is clearly identified.

Release historycaution

The package has 40 releases over more than 13 years, but no registry release in the last three years; this indicates a meaningful maintenance slowdown.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.

Security policycaution

The repository has no security policy, leaving disclosure and maintenance expectations undocumented; this is a modest transparency gap.