Summary
Togoder Security scanned the npm package @bramus/specificity@2.4.2 on Oct 6, 2026. An AI review of 10 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 |
|---|---|---|
| bin/cli.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/index.cjs | safe | No malicious patterns detected; the code is a CSS parser and specificity calculator with no network, filesystem, process, or dynamic execution behavior. |
| dist/index.js | safe | No malicious patterns detected; the code is a standard CSS selector parser and specificity calculator with no exfiltration, credential harvesting, obfuscation, or dynamic execution. |
| src/core/calculate.js | safe | Cleared by Jev triage; no further analysis needed |
| src/core/index.js | safe | Cleared by Jev triage; no further analysis needed |
| src/index.js | safe | Cleared by Jev triage; no further analysis needed |
| src/util/compare.js | safe | Cleared by Jev triage; no further analysis needed |
| src/util/filter.js | safe | Cleared by Jev triage; no further analysis needed |
| src/util/index.js | safe | Cleared by Jev triage; no further analysis needed |
| src/util/sort.js | safe | Cleared by Jev triage; no further analysis needed |
Scanned versions of @bramus/specificity
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 2.4.2 | No issues | 10 | Oct 6, 2026 |
Frequently asked questions
Is @bramus/specificity safe to use?
Our AI source review of @bramus/specificity@2.4.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @bramus/specificity contain malware?
No malware was identified in @bramus/specificity@2.4.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 @bramus/specificity checked?
Togoder Security downloaded the published npm package and had an AI model read its 10 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 @bramus/specificity 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 @bramus/specificity@2.4.2, cost nothing.