Gathering detailed insights and metrics for stdout-stream
Gathering detailed insights and metrics for stdout-stream
Installations
npm install stdout-streamScore
97.9
Supply Chain
77.7
Quality
75.1
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Contributors
3
Developer
mafintosh
Developer Guide
BETA
Module System
Unable to determine the module system for this package.
Min. Node Version
Typescript Support
No
Node Version
16.16.0
NPM Version
8.11.0
Statistics
38 Stars
35 Commits
5 Forks
3 Watching
1 Branches
3 Contributors
Updated on 14 Jun 2024
Bundle Size
76.96 kB
Minified
22.71 kB
Minified + Gzipped
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
1,072,925,171
Last day
-1.2%
258,776
Compared to previous day
Last week
-0.1%
1,366,853
Compared to previous week
Last month
3.9%
5,872,797
Compared to previous month
Last year
-32.2%
78,758,969
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Dev Dependencies
1
Versions
stdout-stream
Non-blocking stdout stream
npm install stdout-stream
Rant
Try saving this example as example.js
1console.error('start'); 2process.stdout.write(new Buffer(1024*1024)); 3console.error('end');
And run the following program
node example.js | sleep 1000
The program will never print end since stdout in node currently is blocking - even when its being piped (!).
stdout-stream tries to fix this by being a stream that writes to stdout but never blocks
Usage
1var stdout = require('stdout-stream'); 2 3stdout.write('hello\n'); // write should NEVER block 4stdout.write('non-blocking\n') 5stdout.write('world\n');
stdout-stream should behave in the same way as process.stdout (i.e. do not end on pipe etc)
License
MIT
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
security policy file detected
Details
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 2/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 2 are checked with a SAST tool
Score
3.9
/10
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More