registry / terminal-mascot / 0.0.1-security
terminal-mascot@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection found no lifecycle hooks, entrypoints, dependencies, or code to execute. The README describes this version as a placeholder published after malicious code was removed, which is not evidence of malicious behavior in the inspected package.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
No source-backed malicious action is reachable.
Mechanism
No executable package behavior
AI rationale
Direct inspection found no lifecycle hooks, entrypoints, dependencies, or code to execute. The README describes this version as a placeholder published after malicious code was removed, which is not evidence of malicious behavior in the inspected package.
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
Evidence against
- package.json has no scripts, entrypoints, dependencies, or executable configuration.
- README.md identifies this release as a security holding placeholder.
- Only package.json and README.md are present; neither contains executable source or install-time behavior.
- No network, filesystem-write, credential, shell, eval, dynamic loading, or AI-agent configuration behavior is present.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 Low
LowNo License
Affected versions and remediation
This report applies to terminal-mascot@0.0.1-security.
See all versions of terminal-mascot for other recorded verdicts.
- Review the evidence and your use of terminal-mascot@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.