@straion/cli@0.1.20
> **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 8d ago · by lpm-firewall-aiThe manifest and entrypoint describe a CLI without an install lifecycle hook. The flagged execution and data-handling signals resolve to subcommand execution, gated local trajectory collection, user-invoked integration setup, and git notes sent to the selected push remote; no attack was established.
Decision evidence
public snapshot- The manifest exposes a CLI binary; inspection found no lifecycle-script entry.
- The flagged spawn path starts a subcommand with inherited standard input, output, and error streams.
- Trajectory collection requires STRAION_TRAJECTORIES_ENABLED=1 and writes a local JSON file.
- The audit hook passes the pushed remote to an explicit git-note push.
- Setup is an invoked CLI command that presents agent integrations for selection and setup.
- The agent setup runner updates Straion integrations through its setup flow.
- The entrypoint imports the CLI bundle; no install-time execution path was found.
- Command-output handling resolves to CLI and git operations; no hidden exfiltration path was established.
- Setup and trajectory collection are user-invoked or gated, and no confirmed attack surface remains.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/audit-Esx3Pe_q.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @straion/cli@0.1.20.
See all versions of @straion/cli for other recorded verdicts.
- Review the evidence and your use of @straion/cli@0.1.20 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.