skalpel
Behavioral graph for AI-assisted coding — learns how you work and steers Claude Code + Codex in real time.
This report shows the evidence for skalpel@4.0.19. 2 of 39 known versions are blocked or flagged. The newest version, 4.0.54, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete unconsented postinstall mutation of a foreign AI-agent control surface, not merely a user-invoked integration. The source establishes transcript access through that installed control path.
Decision evidence
public snapshot- package.json runs postinstall.mjs on install.
- postinstall.mjs invokes install.mjs --statusline-only without user confirmation.
- install.mjs stages hook code in ~/.skalpel/hooks and writes ~/.claude/settings.json statusLine.
- The staged statusline reads Claude transcript content from the provided transcript_path.
- Full installation wires Claude/Codex prompt hooks and uploads completed Claude transcripts to graph.skalpel.ai.
- postinstall does not wire prompt/session hooks or modify Codex config.
- Transcript upload path requires a later full install/login and authenticated identity.
- Network destinations are named first-party Skalpel and Google/Cognito endpoints.
Source & flagged code
6 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 unpkgFindings
Affected versions and remediation
This report applies to skalpel@4.0.19.
The versions list below shows the verdict for each recorded version.
- Avoid installing skalpel@4.0.19. 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.