@twing/cli@1.3.11
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found guarded first-party machine onboarding, while ordinary dependency installs do not wire agent settings. The scanner’s execution and agent-integration hints are consistent with this product setup and test support; they do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines a postinstall hook that runs postinstall.cjs.
- The postinstall guard permits machine wiring only for a global install or an explicit --machine-setup argument; other installs exit without wiring.
- Machine setup connects the resolver, OpenCode plugin, and Codex hooks as first-party onboarding.
- The resolver target is a fixed twing path under the user home directory.
- The Codex integration targets the user’s Codex configuration path.
- The inspected OpenCode adapter builds a descriptor from the session ID and selected environment and directory values.
- test-support.js uses child processes to initialize throwaway Git test repositories.
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.3.11.
See all versions of @twing/cli for other recorded verdicts.
- Review the evidence and your use of @twing/cli@1.3.11 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.