@straion/cli@0.1.8
> **Note:** This CLI is currently in early access. Features may change and we appreciate your feedback. For questions or issues, please contact [support@straion.com](mailto:support@straion.com).
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe flagged source does not establish a concrete malicious behavior: package.json exposes a CLI without lifecycle hooks, the agent configuration bytes are part of explicit setup code, and the network reference inspected is the PostHog client host. The scanner hints alone do not establish command-output exfiltration or Trojan Source behavior.
Decision evidence
public snapshot- The manifest exposes a CLI through bin/straion.mjs and declares no install lifecycle hooks.
- The flagged agent configuration bytes identify per-agent configuration paths; the inspected surrounding code sets up agent integrations through explicit setup functions.
- The flagged automode bundle contains PostHog client code with its default analytics host; inspection found no command-output exfiltration path in that file.
- The agent setup bundle begins with ordinary PostHog chunk instrumentation, with no Trojan Source character in the inspected bytes.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/automode-CoouHyXt.jsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/automode-CoouHyXt.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @straion/cli@0.1.8.
See all versions of @straion/cli for other recorded verdicts.
- Review the evidence and your use of @straion/cli@0.1.8 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.