@cachly-dev/mcp-server@0.10.187
Solve it once. From then on, your AI knows. Experience for coding agents, EU-hosted: an MCP server for Claude Code, Cursor, Copilot & Windsurf. Learns from every bug fix, commit and CI run.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe explicit setup path enables ongoing transfer of commit metadata through a first-party Cachly integration. Because the npm lifecycle hook does not install it and no broader control-surface change or credential theft was established, this is a warning-level capability.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user runs the package's setup command in a project containing a Git repository.
Impact
Those commit details are sent to the configured Cachly service after commits, without a separate confirmation for each commit.
Mechanism
Setup installs or updates a post-commit hook that invokes the Cachly CLI with the commit message, identifier, and changed file names.
AI rationale
The explicit setup path enables ongoing transfer of commit metadata through a first-party Cachly integration. Because the npm lifecycle hook does not install it and no broader control-surface change or credential theft was established, this is a warning-level capability.
Evidence
dist/src/index.jsdist/src/cls-hook.jsdist/src/handlers/fedbrain.js.git/hooks/post-commit
Network endpoints1
api.cachly.dev
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package postinstall prints a command for the user to run to configure the service; it does not install the Git hook itself.
- The explicit setup commands install or update a project-local post-commit hook.
- The hook invokes the Cachly CLI with commit messages, commit identifiers, and changed file names; the Cachly handler accepts these as Git learning signals, using the Cachly API by default.
- Other inspected integration locations concern Cachly-owned editor settings, credentials, plugin-version lookup, and ambient-hook files.
Evidence against
- The npm postinstall only displays setup guidance; it does not activate the hook.
- The post-commit payload contains commit metadata, not the committed file contents. The setup is a first-party project integration, and no unrelated agent-control write or credential theft was established.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsEvalFilesystemNetwork
Source & flagged code
12 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/src/autor.jsView file
1import{execFileSync as c}from"node:child_process";const f=e=>n=>{try{return n.startsWith("-")?"":c("git",["config",n],{cwd:e,encoding:"utf-8",stdio:"pipe",timeout:1500,windowsHide:...
High
Findings
2 Critical7 High5 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationdist/src/index.js
CriticalPrevious Version Dangerous Deltadist/src/einblendung.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/src/autor.js
HighSame File Env Network Executiondist/src/index.js
HighCredential Exfiltrationdist/src/index.js
HighTrigger Reachable Credential Exfiltrationdist/src/index.js
HighRuntime Package Installdist/src/cls-hook.js
HighSemantic Analysis Limiteddist/src/doctor.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/src/index.js
Affected versions and remediation
This report applies to @cachly-dev/mcp-server@0.10.187.
See all versions of @cachly-dev/mcp-server for other recorded verdicts.
- Review the evidence and your use of @cachly-dev/mcp-server@0.10.187 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.