registry / postcss-processor-utils / 0.0.1-security
postcss-processor-utils@0.0.1-security
security holding package
This package appears in our research on the fake Tailwind CSS plugins, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection shows this exact version contains only a minimal manifest and a README; the README's historical claim is not executable evidence. No concrete malicious behavior is present in the package contents.
Static reason
No blocking static signals were detected.
Trigger
None; installing or importing exposes no package code because no runtime entrypoint is declared.
Impact
No package-implemented execution, persistence, exfiltration, or destructive behavior found.
Mechanism
Metadata-only placeholder package
AI rationale
Source inspection shows this exact version contains only a minimal manifest and a README; the README's historical claim is not executable evidence. No concrete malicious behavior is present in the package contents.
Evidence
package.jsonREADME.md
Decision evidence
public snapshotAI called this Clean at 99.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- README.md contains an unverified historical claim that a prior package release was removed for malware.
Evidence against
- package.json has no scripts, bin, main, module, browser, dependencies, or executable entrypoints.
- The package tree contains only package.json and README.md.
- No source code, install-time hook, network endpoint, credential access, shell execution, or file mutation mechanism is present.
Behavioral surface
NoLicense
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
2 Low
LowNo License
LowAi Review Evidence
Affected versions and remediation
This report applies to postcss-processor-utils@0.0.1-security.
See all versions of postcss-processor-utils for other recorded verdicts.
- Review the evidence and your use of postcss-processor-utils@0.0.1-security before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.