@atlashub/smartstack-cli@5.10.0
SmartStack Claude Code automation toolkit - GitFlow, EF Core migrations, prompts and more
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe scanner's exfiltration label overstates the observed flow: the token is sent to Anthropic's API rather than an unrelated endpoint. However, explicit installation creates a persistent Claude integration that reads credentials, so it warrants a warning under the extension-lifecycle policy.
Decision evidence
public snapshot- `ss install` deploys templates into `~/.claude` or `./.claude`.
- Install registers a recurring Claude `statusLine` command and PreToolUse hooks.
- The deployed statusline reads `~/.claude/.credentials.json` accessToken.
- It sends that bearer token to `api.anthropic.com/api/oauth/usage`.
- The npm postinstall only prints a Windows PATH hint.
- Credential use is limited to Anthropic's documented-looking usage endpoint, not a package-controlled host.
- Statusline deployment and config mutation require explicit `ss install`; no lifecycle path reaches it.
- Installer preserves a foreign status line unless `--force` is supplied.
- No hidden payload download, eval, or unrelated credential receiver was found.
Source & flagged code
16 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @atlashub/smartstack-cli@5.10.0.
See all versions of @atlashub/smartstack-cli for other recorded verdicts.
- Review the evidence and your use of @atlashub/smartstack-cli@5.10.0 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.