tme-error@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe inspected `0.0.1-security` artifact contains only a minimal manifest and a holding notice; its README refers to removed prior malicious code, not executable content in this version.
Static reason
No blocking static signals were detected.
Trigger
None.
Impact
No package-originated impact identified.
Mechanism
No executable behavior.
AI rationale
The inspected `0.0.1-security` artifact contains only a minimal manifest and a holding notice; its README refers to removed prior malicious code, not executable content in this version.
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` says an earlier package release was removed for malicious code.
Evidence against
- `package.json` has no lifecycle scripts or executable entrypoints.
- Only `package.json` and `README.md` are present.
- No install/import code, network endpoints, file access, shell execution, or payload files exist.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
2 Low
LowNo License
LowAi Review Evidence
Affected versions and remediation
This report applies to tme-error@0.0.1-security.
See all versions of tme-error for other recorded verdicts.
- Review the evidence and your use of tme-error@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.