@doist/twist-cli
TypeScript CLI for Twist
This report shows the evidence for @doist/twist-cli@3.0.8. 2 of 14 known versions are blocked or flagged. The newest version, 3.0.15, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe postinstall lifecycle performs unconsented mutation of foreign and broad AI-agent control surfaces. This meets the install-hook abuse blocking boundary despite skipping paths where no prior skill exists.
Decision evidence
public snapshot- The package registers a postinstall lifecycle hook.
- Postinstall imports code that updates all globally installed skills.
- The update loop overwrites every detected installed skill without a user command.
- Targeted skill locations include Claude Code, Codex, Cursor, Gemini, Pi, and the broad .agents directory.
- Skill updates write a package-controlled SKILL.md into those agent control surfaces.
- The updater overwrites the installed SKILL.md with package-controlled content.
- The updater skips agent skill paths that are not already present.
- No relevant network endpoint or remote payload loader was found in the install-time skill-update path.
- The interactive skill commands expose explicit install, update, and uninstall actions.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
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 @doist/twist-cli@3.0.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing @doist/twist-cli@3.0.8. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.