insecure-source-code-management

Detect and recover exposed version-control metadata and backup artifacts on web targets.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/lNwNl/Praxis --skill insecure-source-code-management-lnwnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: insecure-source-code-management
Source: https://github.com/lNwNl/Praxis/tree/main/skills/insecure-source-code-management
Command: npx skills add https://github.com/lNwNl/Praxis --skill insecure-source-code-management-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web servers often accidentally expose version-control directories (.git, .svn, .hg) and backup files, leaking full source code, credentials, and configuration. This Skill provides a structured workflow to detect these exposures and recover the underlying repository data during authorized security assessments. ## Core Features & Use Cases - VCS Exposure Detection: Probe high-value paths like /.git/HEAD, /.svn/wc.db, and /.hg/requires, and interpret 403 vs 404 responses to confirm hidden directories exist. - Repository Recovery: Use open-source tools such as git-dumper, GitTools, GitHacker, svn-extractor, and Mercurial dumpers to reconstruct source trees from partial object access. - Backup and Config Leak Discovery: Probe for .env files, backup archives, .DS_Store, and editor swap files that leak secrets and directory listings. - Use Case: During an authorized web penetration test, recon returns a 403 on /.git/. Use this Skill to confirm exposure via /.git/HEAD, dump the repository with git-dumper, and extract credentials from .git/config and commit logs. ## Quick Start Probe the target for /.git/HEAD and /.git/config, then follow the decision tree to dump and analyze any exposed repository.

Frequently Asked Questions about insecure-source-code-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a website exposes its .git directory?▼

Request /.git/HEAD and look for a response like "ref: refs/heads/main", then try /.git/config. A 403 on the /.git/ directory combined with a 200 on specific files strongly indicates the repository is exposed and recoverable.

What tools can recover source code from an exposed .git directory?▼

Use arthaud/git-dumper to dump reachable .git trees, internetwache/GitTools for partial or corrupt dumps, and WangYihang/GitHacker for edge cases standard dumpers miss. Prioritize .git/config, logs/HEAD, and packed-refs for credentials and history.

How do I extract files from an exposed .svn directory?▼

For SVN before 1.7, fetch /.svn/entries; for 1.7 and later, download /.svn/wc.db and query it with sqlite3. Use anantshri/svn-extractor for automation, or request /.svn/pristine/ blobs manually if exposed.

What does a 403 on /.git/ mean during testing?▼

A 403 on the directory usually means it exists but listing is denied, unlike a 404 which indicates absence. Continue probing direct file URLs like /.git/HEAD and /.git/config, since server rules such as NGINX deny blocks may still allow specific subpaths.

Is it legal to dump exposed git repositories from websites?▼

Only within authorized security assessments with defined scope. This Skill explicitly restricts use to authorized testing, requires respecting rate limits, and treats recovered credentials and URLs as sensitive data that must not be exfiltrated beyond scope.