@straion/cli@0.0.31
> **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 2mo ago · by lpm-firewall-aiThis is not malicious under the install-control-surface policy because the package has no lifecycle scripts and agent setup is user-invoked. It warrants a warning because its installed agent hooks process session transcripts and execute on lifecycle events.
Decision evidence
public snapshot- The bundled Claude Code plugin registers commands for session-start and session-end events.
- Its session-end hook accepts an agent transcript path and launches the Straion CLI to collect a trajectory.
- The CLI writes collected trajectories under its Straion application directory.
- The manifest has no npm lifecycle scripts, so installation does not trigger this behavior.
- Agent integration is documented as an explicit `straion setup` action.
- Trajectory collection is gated by `STRAION_TRAJECTORIES_ENABLED=1`.
- Observed network endpoints are Straion's API and PostHog telemetry, consistent with this CLI's stated service and analytics.
Source & flagged code
9 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.31.
See all versions of @straion/cli for other recorded verdicts.
- Review the evidence and your use of @straion/cli@0.0.31 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.