loader1@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection found no executable source or lifecycle hooks. The README's historical claim does not establish malicious behavior in loader1@0.0.1-security.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
None established
Mechanism
No executable package behavior
AI rationale
Direct inspection found no executable source or lifecycle hooks. The README's historical claim does not establish malicious behavior in loader1@0.0.1-security.
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 states this is a security holding package replacing removed malicious code.
Evidence against
- package.json contains only package metadata; no scripts, dependencies, or entrypoints.
- README.md and package.json are the only package files present.
- No install-time, runtime, network, filesystem, shell, or dynamic-loading code exists.
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 loader1@0.0.1-security.
See all versions of loader1 for other recorded verdicts.
- Review the evidence and your use of loader1@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.