Summary
Togoder Security scanned the npm package spdx-license-ids@3.0.22 on Oct 6, 2026. An AI review of 0 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
No per-file summaries were stored for this scan.
Affected version ranges
None of the 2 scanned versions of spdx-license-ids are flagged high or critical. The latest scanned version, 3.0.23, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 3.0.22 – 3.0.23 | No issues | 2 | >=3.0.22 <=3.0.23 | |
| 3.0.10 | Not scanned | 1 | 3.0.10 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of spdx-license-ids
Frequently asked questions
Is spdx-license-ids safe to use?
Our AI source review of spdx-license-ids@3.0.22 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does spdx-license-ids contain malware?
No malware was identified in spdx-license-ids@3.0.22 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 spdx-license-ids checked?
Togoder Security downloaded the published npm package and had an AI model read its 0 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 spdx-license-ids 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 spdx-license-ids@3.0.22, cost nothing.