registry / @raditia/craftkit / 1.53.0
@raditia/craftkit@1.53.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 install lifecycle and upstream installer execution create a real lifecycle setup risk, but the inspected behavior is consistent with first-party CraftKit setup. Classify as a warning for agent extension lifecycle risk, not as a confirmed attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package with npm on macOS or Linux.
Impact
Installs or configures tools and CraftKit-owned agent content in the user's environment; no evidence here shows credential collection or exfiltration.
Mechanism
The postinstall script invokes sync.sh with setup enabled; when RTK is absent, sync.sh runs its GitHub installer, then proceeds with CraftKit sync.
AI rationale
The install lifecycle and upstream installer execution create a real lifecycle setup risk, but the inspected behavior is consistent with first-party CraftKit setup. Classify as a warning for agent extension lifecycle risk, not as a confirmed attack.
Evidence
package.jsonscripts/postinstall.shsync.shhooks/craftkit-platform-rules.js
Network endpoints1
raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs a postinstall script that starts CraftKit sync automatically.
- During that setup, if RTK is missing, the script downloads and executes its installer from GitHub.
- The sync targets supported agent configuration and skill locations, with a migration limited to files containing CraftKit’s legacy managed-block marker.
- The inspected hook reads platform rules from CraftKit’s own staging directory.
Evidence against
- The RTK installer runs only when the explicit setup path is active and RTK is absent.
- The inspected configuration migration checks for CraftKit’s legacy marker before rewriting those files.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 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 unpkg•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
13L14: const path = require('path');
L15: const { BIG_LINES, overLines } = require(path.join(__dirname, 'craftkit-filesize.js'));
Medium
Dynamic Require
Package source references dynamic require/import behavior.
hooks/craftkit-read-cap.jsView on unpkg · L13Findings
2 High6 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedhooks/craftkit-platform-rules.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirehooks/craftkit-read-cap.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperinstall.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptohooks/craftkit-transcript.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @raditia/craftkit@1.53.0.
See all versions of @raditia/craftkit for other recorded verdicts.
- Review the evidence and your use of @raditia/craftkit@1.53.0 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.