# sonic-boom@2.8.0 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-04T16:40:52.000Z
- Files reviewed: 6
- Findings: no findings
- Report: https://security.togoder.click/npm/sonic-boom@2.8.0
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## 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.

## Findings

No findings.

## Files reviewed

- `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.

## 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.

- 4.2.1 (`4.2.1`): clean
- 4.2.0 (`4.2.0`): not scanned
- 2.8.0 (`2.8.0`): clean

## Scanned versions

- [4.2.1](https://security.togoder.click/npm/sonic-boom@4.2.1): safe, 2026-10-04T21:17:55.000Z
- [2.8.0](https://security.togoder.click/npm/sonic-boom@2.8.0): safe, 2026-10-04T16:40:52.000Z

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology