Gathering detailed insights and metrics for sendmessage
Gathering detailed insights and metrics for sendmessage
Send a cross process message if message channel is connected.
Installations
npm install sendmessageDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Min. Node Version
>= 18.19.0
Node Version
18.20.5
NPM Version
10.8.2
Score
98.1
Supply Chain
89.1
Quality
76.7
Maintenance
100
Vulnerability
100
License
Releases
3
Languages
2
JavaScript
TypeScript
JavaScript (70.91%)
TypeScript (29.09%)
Developer
node-modules
Download Statistics
Total Downloads
10,318,051
Last Day
3,598
Last Week
30,976
Last Month
138,300
Last Year
1,678,833
GitHub Statistics
MIT License
27 Stars
22 Commits
2 Forks
17 Watchers
2 Branches
23 Contributors
Updated on Dec 11, 2024
Bundle Size
1.35 kB
Minified
632.00 B
Minified + Gzipped
Maintainers
1
Package Meta Information
Latest Version
3.0.1
Package Id
sendmessage@3.0.1
Unpacked Size
17.54 kB
Size
4.80 kB
File Count
11
NPM Version
10.8.2
Node Version
18.20.5
Published on
Dec 11, 2024
Total Downloads
Cumulative downloads
Total Downloads
10,318,051
sendmessage
Send a cross process message if message channel is connected. Avoid channel closed error throw out.
Install
1npm install sendmessage --save
Usage
master.js
1import { fork } from 'node:child_process'; 2import { sendmessage } from 'sendmessage'; 3 4const worker = fork('./worker.js'); 5 6sendmessage(worker, { hi: 'this is a message to worker' });
worker.js
1import { sendmessage } from 'sendmessage'; 2 3sendmessage(process, { hello: 'this is a message to master' });
API
#sendmessage(childProcess, message)
Send a cross process message.
If a process is not child process, this will just call process.emit('message', message) instead.
- childProcess: child process instance
- message: the message need to send
1sendmessage(process, { hello: 'this is a message to master' });
You can switch to process.emit('message', message) using process.env.SENDMESSAGE_ONE_PROCESS
License
Contributors
Made with contributors-img.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
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
SAST tool is not run on all commits -- score normalized to 3
Details
- Warn: 2 commits out of 6 are checked with a SAST tool
Reason
Found 2/22 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
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/nodejs.yml:1
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Score
4.3
/10
Last Scanned on 2025-06-30
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