cortex-version-check — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cortex-version-check (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Check whether the active cortex runtime is current before suggesting a restart or redeploy.
${CLAUDE_PLUGIN_ROOT}/scripts/check-runtime-current.sh <optional-args>
# Note: if this script is missing, run: docker inspect $(docker compose ps -q cortex) --format '{{.Image}}'If CLAUDE_PLUGIN_ROOT is not available or the script is missing, stop with a clear failure: "plugin root unavailable; cannot run bundled version checker". Do not guess a source checkout path. Suggest the user run cortex-redeploy to restore plugin artifacts.
--pull only when the user asks to refresh Docker image metadata first. In Docker mode, --pull pulls the compose image before comparing the running container image ID to the local compose image ID. Without --pull, Docker mode only proves the running container matches the image already present in the local cache.dockerCURRENT, STALE, or FAILSTALE, include the exact fix printed by the checker. If the verdict is FAIL, include what the checker could not inspect.Keep the answer compact and evidence-based. Do not infer freshness from source files alone; use the checker output as the source of truth.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.