@lingjingai/scriptctl@0.66.10
剧本阶段统一 CLI:素材转 Script v4,并兼容 Script v3 的本地写作、精修、校验和发布。
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe postinstall hook automatically installs and replaces a first-party skill in user-level agent configuration directories, creating a concrete agent extension lifecycle risk. Its narrow scope and opt-out mitigate the impact, so this supports a warning rather than a block.
Decision evidence
public snapshot- The package runs scripts/install-skill.mjs from its postinstall hook. [package.json]
- The installer targets skill directories under the user's Claude, agents, and Codex configuration folders. [scripts/install-skill.mjs]
- For each target, the installer removes the existing scriptctl directory and copies in the package's skill. [scripts/install-skill.mjs]
- An environment setting can skip installation, but the setup otherwise runs during package installation. [scripts/install-skill.mjs]
- The CLI's update command invokes npm to install this package globally, but that update is a separate user-invoked command. [dist/chunk-4MGRUUNV.js]
- The installer confines replacement to the scriptctl skill subdirectory and copies the package's own skill there.
- The installer supports environment-based opt-out and performs no network request in the inspected code.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/review-agent.jsView on unpkgFindings
Affected versions and remediation
This report applies to @lingjingai/scriptctl@0.66.10.
See all versions of @lingjingai/scriptctl for other recorded verdicts.
- Review the evidence and your use of @lingjingai/scriptctl@0.66.10 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.