Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
process-exists
Advanced tools
Check if a process is running
$ npm install process-exists
const processExists = require('process-exists');
(async () => {
console.log(await processExists(process.pid));
//=> true
const exists = await processExists.all([process.pid, 'foo']);
console.log(exists.get(process.pid));
//=> true
console.log(exists.get('foo'));
//=> false
console.log(processExists.filterExists(exists));
//=> [process.pid]
})();
Returns a Promise<boolean>
.
Type: number | string
Process ID or name to check.
Returns a Promise<Map>
with the process name/ID as key and the status as a boolean value.
Type: Array<number | string>
Process IDs or names to check.
Returns an Array<number | string>
with the processes that exist.
Type: Array<number | string>
Process IDs or names to check.
FAQs
Check if a process is running
The npm package process-exists receives a total of 154,031 weekly downloads. As such, process-exists popularity was classified as popular.
We found that process-exists demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.