Fetch API compliant HTTP Server adapter
84%
Total Score
healthy
Healthy: sustained releases, active repository work, and npm provenance outweigh concentrated contributions and workflow hygiene gaps.
The repository owner is an individual rather than an organization, so the concentrated contributor activity is not offset by explicit organizational ownership.
Four contributors were active, but one contributor made 86% of recent commits; that concentration creates some continuity risk despite the presence of other contributors.
The repository has no security policy, leaving vulnerability reporting and handling expectations less transparent for users and maintainers.
Version 0.13.0 is not a prerelease, but the recent prerelease share is 0.9 and the package remains below major version 1, so API stability may be less predictable.
All five workflows were analyzed with no untrusted checkouts or script injection, and permissions are not broadly writable. However, four high-confidence unpinned-image findings and 14 of 36 unpinned action references leave build reproducibility and workflow supply-chain hygiene weaker.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tslib Version ^2.6.3 | — | — |
@whatwg-node/fetch Version ^0.12.0 | — | — |
@envelop/instrumentation Version ^1.0.0 | — | — |
@whatwg-node/disposablestack Version ^0.1.0 | — | — |
@whatwg-node/promise-helpers Version ^2.0.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.