@scarn/cli@0.8.1
Scarn runs AI agents over your backlog, on your machines. This CLI links your repo, designs pipelines with an agent, and runs the workers that execute them.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe install hook’s network request is a fallback to retrieve the package’s matching binary from the npm registry, and it does not send host or credential data. The flagged bundle’s credential use is scoped to GitHub repository and container registry operations within the CLI’s devcontainer functionality.
Decision evidence
public snapshot- The postinstall hook only attempts recovery when the matching platform binary is missing; it fetches that binary from the npm registry and writes it under dist/.
- The CLI is described as running devcontainer workers; its bundled devcontainer tooling uses GITHUB_TOKEN for GitHub repository requests.
- The wrapper passes the devcontainer bundle path to the CLI binary, consistent with that bundled tooling serving the package’s stated purpose.
- The package has a postinstall hook that may make a network request and write a binary during installation.
- The bundle can read GITHUB_TOKEN and execute child processes as part of devcontainer operations.
Source & flagged code
11 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 @scarn/cli@0.8.1.
See all versions of @scarn/cli for other recorded verdicts.
- Review the evidence and your use of @scarn/cli@0.8.1 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.