@straion/cli@0.0.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 4mo ago · by lpm-firewall-aiThe suspicious primitives are consistent with a Straion CLI: token auth, GraphQL calls, analytics, local config, and opt-in agent setup. Source inspection found no install-time execution, hidden exfiltration, real embedded secret, or unconsented AI-agent control-surface mutation.
Decision evidence
public snapshot- User-invoked `straion setup` can install AI-agent plugins/hooks under agent config dirs.
- Session-end hook scripts execute `straion trajectory collect` and may read agent transcript paths when `STRAION_TRAJECTORIES_ENABLED=1`.
- CLI reads tokens from `--token`/`STRAION_API_KEY` and stores login credentials under `~/.straion/credentials.enc`.
- `package.json` has no lifecycle scripts; bin is `dist/cli.js` only.
- `dist/components/pat-input.test.js` contains synthetic PAT-looking test strings, not a real embedded secret.
- Network use is package-aligned: GraphQL API defaults to `https://api.straion.app`; analytics uses PostHog host `https://us.i.posthog.com`.
- Agent/plugin installation is behind interactive setup/explicit setup command and selection, not install-time or import-time execution.
- No evidence of broad credential harvesting, destructive behavior, persistence outside declared agent integrations, or hidden payload loading.
Source & flagged code
2 flaggedPackage contains a critical-looking secret pattern.
dist/components/pat-input.test.jsView on unpkg · L45GitHub personal access token in dist/components/pat-input.test.js
dist/components/pat-input.test.jsView on unpkg · L45Findings
Affected versions and remediation
This report applies to @straion/cli@0.0.20.
See all versions of @straion/cli for other recorded verdicts.
- Review the evidence and your use of @straion/cli@0.0.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.