set-repo-managed — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited set-repo-managed (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.
Sets Managed in ~/.wpf-dev-pack-mcp/state.json (preserving LastPullUtc). This flag decides how the server refreshes the clone at repoPath.
If `$0` is empty, use AskUserQuestion to ask for `true` or `false`. Do NOT proceed until a value is provided.
dotnet "${CLAUDE_PLUGIN_ROOT}/scripts/SetWpfDevPackManaged.cs" "$0"What it controls (mcp/Git/RepoRefresher.cs):
git fetch + git reset --hard origin/<branch> on repoPath. Use ONLY for a dedicated clone the server created/owns. Never set `true` when `repoPath` is your active working repo — a refresh will discard uncommitted changes and reset the branch to origin/<branch>, destroying local work.git pull --ff-only when the tree is clean, skip when dirty. Use when repoPath points at your own working clone.Surface the output verbatim. Inspect the current flag with /wpf-dev-pack:show-wpf-dev-pack-config.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.