Universal WHATWG Fetch API for Node, Browsers and React Native
62%
Total Score
50
100
90
67
50
The release has no build attestation, staged publishing, or trusted-publisher identity. This weakens publication transparency but does not by itself show that the release is unsafe.
A prepare script runs during package installation, adding some installation complexity. No other lifecycle-script evidence is provided, so this is a modest concern rather than a severe risk.
The package has 52 releases over roughly 9 years, but none in the last 12 months; its latest registry release was in December 2024. This points to slowing maintenance rather than abandonment by itself.
There were zero commits and zero active maintainers in the last three months. Combined with no recent registry releases, this lowers confidence in current maintenance capacity.
There were no new or closed issues or pull requests in the last month, with 24 open issues and 3 open pull requests. This is a mild sign of limited current activity, though not proof of abandonment.
| Title | Versions | Severity |
|---|---|---|
CVE-2022-1365 cross-fetch is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor in versions 3.0.0 - 3.1.5 and 0.0.0 - 2.2.6. | 0.0.0 - 2.2.63.0.0 - 3.1.5 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
node-fetch Version ^2.7.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.