Summary
Togoder Security scanned the npm package @csstools/css-tokenizer@4.0.2 on Oct 6, 2026. An AI review of 1 source file 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 |
|---|---|---|
| dist/index.mjs | safe | No malicious patterns detected; the code is a standard CSS tokenizer implementation with only structuredClone/JSON usage and no network, filesystem, process, or dynamic-code-execution behavior. |
Frequently asked questions
Is @csstools/css-tokenizer safe to use?
Our AI source review of @csstools/css-tokenizer@4.0.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @csstools/css-tokenizer contain malware?
No malware was identified in @csstools/css-tokenizer@4.0.2 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @csstools/css-tokenizer checked?
Togoder Security downloaded the published npm package and had an AI model read its 1 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 @csstools/css-tokenizer 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 @csstools/css-tokenizer@4.0.2, cost nothing.