git-repo@0.13.0
VERIFIEDPublisher claims: "Git repository and SourceGit integration. Topics — clone (ghq), conflict-dry-run (isolated merge test), credential-helper (multi-account HTTPS token), doctor (hook health & compliance audit — Tier 1 Base + Tier 2 Conditional taxonomy), fix-worktree (bare repo recovery), githooks (hook silently never runs — hooksPath precedence, passthrough chain, install trade-off), isolate-hunk (stage own edit amid unrelated content), merge-duplicate, patrol (batch inspect), prune (safely remove merged worktrees & gone branches), rebase-audit (accidental-revert detection during an active rebase), rename-worktree, safe-relocate (relocate commits onto a clean base branch), sourcegit, ssh-key (multi-account SSH map), tidy (repo tidy pipeline: prune → temp-rebase-reset uncommitted triage → commit-tidy → diff-merge), to-bare, to-ghq (formerly migrate), move-worktree (register/reclaim merged PR), worktree (inventory + reuse + create), worktree-drift-sync (mirror fix across worktrees safely), worktree-register (metadata register/relink). Use when: "reuse worktree", "repo tidy", "repository tidy", "tidy worktrees", "prune worktrees", "prune merged", "multi-account clone", "Repository not found", "wrong account", "concurrent uncommitted edit", "accidental revert", "githooks ignored", "hook not running", "core.hooksPath", "hook not firing", "repo doctor", "hook health", "diagnose hooks", "check hooks" triggers." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-10-29 and scored it 80/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.