Togoder security

npm package security report

sonic-boom@2.8.0 security report

No malicious code found.

No issues Version 2.8.0 Files reviewed 6 Size 47.1 KB Scanned

Summary

Togoder Security scanned the npm package sonic-boom@2.8.0 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.

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
bench.js safe No malicious patterns detected
check.js safe No malicious patterns detected
example.js safe No malicious patterns detected
fixtures/firehose.js safe No malicious patterns detected
index.js safe No malicious patterns detected; this is the legitimate SonicBoom file writer library from pinojs.
test.js safe This is a legitimate test suite for the SonicBoom logging library; all file operations, child processes, and module loading are standard test practices with no malicious intent.

Affected version ranges

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

2.8.04.2.1
VersionsVerdictCountRangeTop findings
4.2.1 No issues 1 4.2.1
4.2.0 Not scanned 1 4.2.0
2.8.0 No issues 1 2.8.0

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

Scanned versions of sonic-boom

VersionVerdictFilesScanned
4.2.1 No issues 5 Oct 4, 2026
2.8.0 No issues 6 Oct 4, 2026

Frequently asked questions

Is sonic-boom safe to use?

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

Does sonic-boom contain malware?

No malware was identified in sonic-boom@2.8.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 sonic-boom 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 sonic-boom 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 sonic-boom@2.8.0, cost nothing.

Related security reports