Summary
Togoder Security scanned the npm package crc-32@1.2.2 on Oct 4, 2026. An AI review of 2 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 |
|---|---|---|
| crc32.js | safe | No malicious patterns detected; the file implements a standard CRC32 checksum algorithm with no network, filesystem, process, or obfuscation concerns. |
| crc32c.js | safe | No malicious patterns detected; the code is a standard CRC32C checksum implementation from the SheetJS project. |
Scanned versions of crc-32
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.2.2 | No issues | 2 | Oct 4, 2026 |
Frequently asked questions
Is crc-32 safe to use?
Our AI source review of crc-32@1.2.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does crc-32 contain malware?
No malware was identified in crc-32@1.2.2 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 crc-32 checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 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 crc-32 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 crc-32@1.2.2, cost nothing.