registry / stella-ai-cli / 0.0.1-security
stella-ai-cli@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection shows only a minimal manifest and explanatory README, with no code or install/runtime execution path. The current `0.0.1-security` contents are clean despite the README noting a prior malicious release was removed.
Static reason
No blocking static signals were detected.
Trigger
None.
Impact
No package-originated runtime, install-time, network, or filesystem impact established.
Mechanism
No executable package behavior.
AI rationale
Direct inspection shows only a minimal manifest and explanatory README, with no code or install/runtime execution path. The current `0.0.1-security` contents are clean despite the README noting a prior malicious release was removed.
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` contains only package metadata; no scripts, entrypoints, dependencies, or binary fields.
- Package file inventory contains only `package.json` and `README.md`; no executable source or payload files.
- `README.md` describes this release as a security holding placeholder.
- No lifecycle hooks, network endpoints, credential access, shell execution, or persistence mechanisms were found.
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 stella-ai-cli@0.0.1-security.
See all versions of stella-ai-cli for other recorded verdicts.
- Review the evidence and your use of stella-ai-cli@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.