@straion/cli@0.0.29
> **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-aiSource shows explicit agent setup and session-end trajectory collection, with no npm lifecycle trigger or concrete malicious behavior established. The guarded agent configuration capability warrants a warning under the agent integration policy.
Decision evidence
public snapshot- The manifest exposes `straion` as a CLI and has no install lifecycle hook, so agent setup is not triggered by npm installation.
- The CLI defines agent configuration paths, including the Claude Code plugin directory and the user-level OpenCode configuration paths.
- Agent setup is activated by the explicit `straion setup` command; agent IDs can be supplied or selected interactively.
- The Claude Code session-end hook invokes `straion trajectory collect` with the session ID and transcript path.
- The inspected source does not establish an unconsented install-time agent configuration change or a concrete malicious action.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/agent-integrations/plugins/claude-code/straion-plugin/hooks/session-end.jsView on unpkg · L8Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/cli.jsView on unpkg · L552Findings
Affected versions and remediation
This report applies to @straion/cli@0.0.29.
See all versions of @straion/cli for other recorded verdicts.
- Review the evidence and your use of @straion/cli@0.0.29 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.