registry / noelc-css-blender / 0.0.0-stage
noelc-css-blender@0.0.0-stage
Temporary package placeholder for staged publishing
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 10d ago · by lpm-firewall-aiThe package contains only a stub manifest and a placeholder README; no executable source or lifecycle behavior was found. The inspected source does not establish an attack surface.
Static reason
No blocking static signals were detected.
Trigger
No lifecycle script or runtime entrypoint is declared.
Impact
No malicious effect was established.
Mechanism
The manifest contains package identity, a stub flag, and a description only.
AI rationale
The package contains only a stub manifest and a placeholder README; no executable source or lifecycle behavior was found. The inspected source does not establish an attack surface.
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies this as a stub placeholder and declares no scripts, dependencies, or entrypoints.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flaggedpackage.jsonView file
1{
"name": "noelc-css-blender",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Dependency Evidence
package.json identifies this as a stub placeholder and declares no scripts, dependencies, or entrypoints.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Dependency Evidencepackage.json
Affected versions and remediation
This report applies to noelc-css-blender@0.0.0-stage.
See all versions of noelc-css-blender for other recorded verdicts.
- Review the evidence and your use of noelc-css-blender@0.0.0-stage 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.