@raditia/craftkit@1.52.0
AI coding skills that auto-sync across Claude Code, Cursor, Gemini CLI, and Codex CLI
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall lifecycle automatically performs setup that writes to multiple AI-tool control surfaces and can run a downloaded installer. This is an unconsented broad install-time mutation, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the npm package when its postinstall lifecycle runs.
Impact
This can modify user-level AI-tool configuration and execute downloaded code without a separate setup command.
Mechanism
The lifecycle enables setup, syncs rules, hooks, commands, and agents across four adapters, and can pipe a remote installer into the shell when RTK is missing.
Policy narrative
On package installation, postinstall invokes sync.sh with agent setup enabled. The sync modifies user-level AI-tool integrations across four adapters, including managed instruction files, and may download and run an RTK installer when the tool is missing. This establishes an automatic install-time control-surface mutation path.
AI rationale
The postinstall lifecycle automatically performs setup that writes to multiple AI-tool control surfaces and can run a downloaded installer. This is an unconsented broad install-time mutation, so the package should be blocked.
Evidence
package.jsonscripts/postinstall.shsync.sh
Network endpoints1
raw.githubusercontent.com
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 95.0% confidence with low false-positive risk.
Evidence for policy risk
- The postinstall hook automatically runs the package’s sync script with agent setup enabled.
- During that sync, the package iterates across Claude, Cursor, Gemini, and Codex adapters to install rules, hooks, commands, and agents.
- The sync migrates managed instruction blocks in user-level Claude, Gemini, and Codex files.
- When RTK is absent, setup downloads and runs a shell script from raw.githubusercontent.com.
Evidence against
- The source presents the sync as setup for CraftKit’s own skills and agent integrations.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystem
HighEntropyStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = bash scripts/postinstall.sh
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg5"scripts": {
"postinstall": "bash scripts/postinstall.sh"
},
"engines": {
High
Suspicious Lifecycle Evidence
The postinstall hook automatically runs the package’s sync script with agent setup enabled.
package.jsonView on unpkg · L5•scripts.postinstall = bash scripts/postinstall.sh
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkghooks/craftkit-read-cap.jsView file
Findings
3 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedhooks/craftkit-platform-rules.js#virtual:normalized:round1
HighSuspicious Lifecycle Evidencepackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirehooks/craftkit-read-cap.js
MediumEnvironment Vars
MediumShips Build Helperinstall.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptohooks/craftkit-transcript.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @raditia/craftkit@1.52.0.
See all versions of @raditia/craftkit for other recorded verdicts.
- Avoid installing @raditia/craftkit@1.52.0. 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.