destroy a stream if possible
63%
Total Score
67
100
90
75
The package has six releases since October 2013, but its latest release was over four years ago and it had no releases in the last 12 months. This lowers confidence that new fixes will arrive promptly, though a small mature utility may change infrequently.
There were zero commits and zero active maintainers in the last three months. Combined with the old registry release, this is a meaningful sign of slowing maintenance.
There is only one open issue and one open pull request, with no issues or pull requests opened or merged in the last month. This indicates little current activity but no large visible backlog.
The repository reports no build tool and no security scanning tool. For a small plain JavaScript module this is a hygiene gap, but it is not independently severe.
The repository has no security policy. This reduces disclosure transparency, although the package's small scope and lack of runtime dependencies limit the significance of the gap.
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.