Summary
Togoder Security scanned the npm package blakejs@1.2.1 on Oct 4, 2026. An AI review of 6 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| blake2b.js | safe | Cleared by Jev triage; no further analysis needed |
| blake2s.js | safe | Cleared by Jev triage; no further analysis needed |
| index.js | safe | Cleared by Jev triage; no further analysis needed |
| test_blake2b.js | safe | No malicious patterns detected; the file is a legitimate test suite for the BLAKE2b hashing implementation, with no network, process, credential, or filesystem abuse beyond local test vector reading. |
| test_blake2s.js | safe | No malicious patterns detected; this is a standard BLAKE2s hash test file. |
| util.js | safe | Cleared by Jev triage; no further analysis needed |
Frequently asked questions
Is blakejs safe to use?
Our AI source review of blakejs@1.2.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does blakejs contain malware?
No malware was identified in blakejs@1.2.1 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 blakejs checked?
Togoder Security downloaded the published npm package and had an AI model read its 6 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 blakejs 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 blakejs@1.2.1, cost nothing.