HTTP2 client, just with the familiar `https` API
61%
Total Score
50
100
90
75
50
No build provenance attestation or trusted-publisher metadata was observed. This limits publication transparency, though it is not by itself evidence that the release is unsafe.
The package has 59 releases and a mature history, but its latest release was nearly three years ago and it had no releases in the last 12 months. This indicates substantially slowed maintenance.
The repository had zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the clearest maintenance concern.
There were no new or closed issues or pull requests in the last month, with 13 open issues remaining. This is consistent with reduced project activity.
No build tools or security scanning tools were detected in the repository. This is a transparency and maintenance-hygiene gap, though the repository still has tests and CI.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
quick-lru Version ^5.1.1 | — | — |
resolve-alpn Version ^1.2.0 | — | — |
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.