@twing/cli@1.0.1
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install lifecycle can write machine-wide agent configuration, creating a real but guarded agent integration risk. The source supports a warning for package-owned agent setup, not a confirmed attack warranting a publish block.
Decision evidence
public snapshot- The postinstall hook runs machine setup only for a global npm install or when passed the machine-setup flag.
- That setup wires Claude Code and OpenCode integrations and marks the installation as managed.
- The OpenCode integration writes a plugin under the user's OpenCode plugin directory; the resolver writes machine-wide Claude settings.
- The integration is package-owned agent setup, and the lifecycle trigger is guarded by an explicit machine-install condition.
- Ordinary dependency installs exit before machine setup runs.
- The inspected setup code contains no credential forwarding or unrelated remote payload execution.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/opencode-adapter.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @twing/cli@1.0.1.
See all versions of @twing/cli for other recorded verdicts.
- Review the evidence and your use of @twing/cli@1.0.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.