Togoder security

npm package security report

process-warning@5.1.0 security report

No malicious code found.

No issues Version 5.1.0 Files reviewed 5 Size 8.2 KB Scanned

Summary

Togoder Security scanned the npm package process-warning@5.1.0 on Oct 4, 2026. An AI review of 5 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

0
critical
0
high
0
medium
0
low

Findings

No findings. The reviewer saw nothing malicious or risky in this version.

Files reviewed

FileVerdictWhat the reviewer saw
benchmarks/warn.js safe No malicious patterns detected; the file is a standard benchmark script using the local package's createWarning function.
eslint.config.js safe No malicious patterns detected
examples/example.js safe No malicious patterns detected
index.js safe No malicious patterns detected; the code is a benign utility for creating and managing process warnings.
types/index.tst.ts safe Cleared by Jev triage; no further analysis needed

Affected version ranges

None of the 2 scanned versions of process-warning are flagged high or critical. The latest scanned version, 5.1.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.

1.0.05.1.0
VersionsVerdictCountRangeTop findings
5.1.0 No issues 1 5.1.0
5.0.0 Not scanned 1 5.0.0
1.0.0 Needs review 1 1.0.0

Full list, including published versions not scanned yet: version ranges API.

Scanned versions of process-warning

VersionVerdictFilesScanned
5.1.0 No issues 5 Oct 4, 2026
1.0.0 Needs review 3 Oct 4, 2026

Frequently asked questions

Is process-warning safe to use?

Our AI source review of process-warning@5.1.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.

Does process-warning contain malware?

No malware was identified in process-warning@5.1.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.

How was process-warning checked?

Togoder Security downloaded the published npm package and had an AI model read its 5 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.

How do I scan process-warning together with the rest of my dependencies?

Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in process-warning@5.1.0, cost nothing.

Related security reports