Implementation of Structured Field Values for HTTP (RFC9651, RFC8941)
78%
Total Score
healthy
Recent releases and thorough project artifacts outweigh single-maintainer and workflow-hygiene concerns.
The release has no build attestation or trusted-publisher identity. This weakens publication transparency, though it is not evidence that the artifact is unsafe by itself.
The package uses a prepare lifecycle script. This is a modest supply-chain and installation-complexity concern, although the package has no runtime dependencies and the available build structure provides context for the script.
Only one registry account has publish access. Registry access lists do not prove maintenance capacity, but this is still a limited publishing base when considered alongside the repository's single active contributor.
The repository owner is an individual user, not an organization. That aligns with the observed single-contributor bus factor and provides no additional institutional maintenance buffer.
One contributor made 100% of the 8 recent commits. Because the owner is an individual rather than an organization, there is no shown organizational handoff capacity.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.