@twing/cli@0.2.30
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall path is limited to global installs or an explicit machine-setup flag, but it configures this package’s agent integrations for machine-wide use. This is a guarded first-party integration lifecycle risk, so warn rather than block.
Decision evidence
public snapshot- The package runs a postinstall script that starts machine setup only for global installs or when explicitly passed the machine-setup flag.
- Machine setup writes Claude Code resolver wiring and installs the package’s OpenCode plugin, creating persistent user-level agent integrations.
- The OpenCode setup preserves an unrelated existing plugin file and leaves it untouched.
- The lifecycle exits for ordinary project dependency installs; its machine-wide setup is gated to global installs or an explicit flag.
- The inspected setup integrates this package’s own agent tooling and does not establish exfiltration, destructive behavior, or permission bypass.
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@0.2.30.
See all versions of @twing/cli for other recorded verdicts.
- Review the evidence and your use of @twing/cli@0.2.30 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.