@phanthy/phanthy-codeo@0.2.5
⚠ Under reviewPhanthy Code coding agent for the terminal
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the flagged UI markers and WebAssembly worker have package-aligned explanations. Several declared runtime dependencies lack source in this snapshot, so the available evidence is insufficient to mark the package clean or malicious.
Decision evidence
public snapshot- The manifest maps the CLI to a Bun entrypoint and lists six runtime dependencies.
- The flagged invisible direction markers wrap displayed file paths in the UI.
- A UI asset module references the flagged audio file, but offline analysis could not classify its bytes.
- The flagged worker uses dynamic code generation in a WebAssembly bridge.
- No concrete attack behavior was established in the inspected source.
- Some declared runtime dependency sources were unavailable in this package snapshot, leaving their behavior unresolved.
Source & flagged code
9 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/opentui-tree-sitter-worker.jsView on unpkg · L2Package source references dynamic require/import behavior.
Findings
Affected versions and remediation
This report applies to @phanthy/phanthy-codeo@0.2.5.
See all versions of @phanthy/phanthy-codeo for other recorded verdicts.
- Review the evidence and your use of @phanthy/phanthy-codeo@0.2.5 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.