Node.js Streams, a user-land copy of the stream library from Node.js
78%
Total Score
healthy
The current release has strong project backing, but repository commits have been absent for three months.
No build attestation or trusted-publisher identity was detected. The release is otherwise tied to a matching, actively maintained repository, so this is a transparency gap rather than a severe risk.
The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance warning, though the current release, merged pull requests, and organizational backing provide some compensation.
The repository uses several build tools, but no security-scanning tools were detected. That leaves a modest transparency and defensive-maintenance gap.
All four workflows were analyzed successfully, use read-only permissions, and have no untrusted checkouts, script injection, or audit findings. However, all 12 action references are unpinned, which weakens build reproducibility and action-integrity controls.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
buffer Version ^6.0.3 | — | — |
events Version ^3.3.0 | — | — |
process Version ^0.11.10 | — | — |
string_decoder Version ^1.3.0 | — | — |
abort-controller Version ^3.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.