Network

Code Guardian sends no telemetry and calls no Provimedia server. Two exceptions still apply: a freshness check of its own repository, and optional registry lookups by the dependency tools. If you set up the companion skill codeguard-master, its model call through your own Claude account and, if present, its chat tool come on top (see below).

What does not happen

• No telemetry.
• No call to a Provimedia server.

Freshness check

On every prompt, at most every 10 minutes, a git fetch runs in the background against the upstream of the project's own repository. Its only purpose is to detect whether the local state is behind the remote one.

If .code-guardian-deploy.yml sets live_ssh (or, as a fallback, ssh) together with live_path, an additional SSH call git rev-parse HEAD follows against the customer's own server.

This version has no off switch, only throttling through the CG_FRISCHE_TTL environment variable, in seconds.

Dependency audits

composer audit and npm audit query their respective package registries, but only when the dependency tool actually runs.

Companion skill codeguard-master (only when set up)

The observer codeguard-master runs only if you set it up yourself. It then collects the state of the projects you register with it at the configured interval without a model, from local files and git. Network access during collection happens only through tools that are present on your machine. The template of its configuration already names a session-chat tool (~/.claude/bin/cg-chat): if it exists on your machine, the observer uses it on every run to ask who is in the chat and how many messages are waiting, and announces itself there at most every six hours. Without a configured channel, the channel is named after the first project you register. If you configure a channel, it sends its actions to your sessions through the same tool. A GitLab tool is added only if you name it in the configuration. When a fixed trigger fires anew, it calls the Claude Code command line without tools and hands it that state. This is a model call through your own Claude account and costs tokens. The observer itself sends nothing to a Provimedia server; where an existing chat or GitLab tool connects to is up to that tool.

Update check

Whether a new version is available is something the customer checks deliberately, through the update API (its own chapter). Code Guardian does not reconcile this automatically in the background.

In one sentence

Code Guardian does not phone home, but it does fetch the freshness state of its own repository in the background, and of the customer's own server when configured.