insecure-source-code-management
Source control and artifact exposure (.git, .svn, .hg, backups, .env)
Install / Use
npx skills add yaklang/hack-skills --skill insecure-source-code-managementInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of insecure-source-code-management
insecure-source-code-management scores 87/100 on our quality scale, 2154th of 4,702 Development & Engineering skills we index (top 46%).
Its SKILL.md is 5.1 KB long, well organised into 20 sections with 6 code examples: a solid amount of guidance for an agent.
With 2,288 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so insecure-source-code-management is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
insecure-source-code-management compared with similar skills
All 4 of these similar skills score higher than insecure-source-code-management; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| insecure-source-code-management (this skill)by yaklang | 87 | 2.3k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
Frequently asked questions
- How do I install insecure-source-code-management?
- Run
npx skills add yaklang/hack-skills --skill insecure-source-code-management. The install tabs above show the steps for each supported agent. - Which AI agents does insecure-source-code-management work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is insecure-source-code-management safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is insecure-source-code-management still maintained?
- The repository was last updated about 2 months ago, so insecure-source-code-management is actively maintained.
Skill content
View source on GitHubname: insecure-source-code-management description: >- Source control and artifact exposure (.git, .svn, .hg, backups, .env). Use when recon finds VCS paths, 403 on hidden dirs, or backup/config leaks during authorized testing.
SKILL: Insecure Source Code Management
AI LOAD INSTRUCTION: This skill covers detection and recovery of exposed version-control metadata, common backup artifacts, and related misconfigurations. Use only in authorized assessments. Treat recovered credentials and URLs as sensitive; do not exfiltrate real data beyond scope. For broad discovery workflow, cross-load recon-for-sec and recon-and-methodology when those skills exist in the workspace.
0. QUICK START
High-value paths to probe first (GET or HEAD, respect rate limits):
/.git/HEAD
/.git/config
/.svn/entries
/.svn/wc.db
/.hg/requires
/.bzr/README
/.DS_Store
/.env
Routing note: quickly probe these paths first; for full recon workflow, load methodology from recon-for-sec and recon-and-methodology before deeper testing.
1. GIT EXPOSURE
Detection
/.git/HEAD— valid repo often returns plain text like:
ref: refs/heads/main
/.git/config— may exposeremote.origin.url, user identity, or embedded credentials./.git/index,/.git/objects/— partial object store access enables reconstruction with the right tools.
403 vs 404
404— path likely absent or fully blocked at the edge.403on/.git/— directory may exist but listing is denied; still try direct file URLs:
/.git/HEAD
/.git/config
/.git/logs/HEAD
/.git/refs/heads/main
A 403 on the directory plus 200 on HEAD strongly indicates exposure.
Recovery tools (open source)
arthaud/git-dumper— dumps reachable.gittree when individual files are fetchable.internetwache/GitTools— Dumper, Extractor, Finder modules for partial/corrupt dumps.WangYihang/GitHacker— alternative recovery when standard dumpers miss edge cases.
Key files to prioritize
| Path | Why it matters |
|------|----------------|
| .git/config | Remotes, credentials, hooks paths |
| .git/logs/HEAD | Commit history, reflog-style leakage |
| .git/refs/heads/* | Branch tips, commit SHAs |
| .git/packed-refs | Packed branch/tag refs |
| .git/objects/** | Object blobs for reconstruction |
2. SVN EXPOSURE
Detection
- SVN before 1.7:
/.svn/entries— XML or text metadata listing paths and revisions. - SVN ≥ 1.7:
/.svn/wc.db— SQLite working copy database (PRAGMA table_infoafter download).
Example probe:
GET /.svn/entries HTTP/1.1
GET /.svn/wc.db HTTP/1.1
Recovery
anantshri/svn-extractor— automated extraction from exposed.svn.- Manual: download
wc.db, query withsqlite3for file paths and checksums, then request/.svn/pristine/blobs if exposed.
3. MERCURIAL EXPOSURE
Detection
/.hg/requires— small text file listing repository features; confirms Mercurial metadata.
GET /.hg/requires HTTP/1.1
GET /.hg/store/ HTTP/1.1
Recovery
sahildhar/mercurial_source_code_dumper— dumps repository when store paths are reachable.
4. OTHER LEAKS
Bazaar (Bzr)
- Probe
/.bzr/READMEand/.bzr/branch-formatfor Bazaar metadata.
macOS .DS_Store
/.DS_Storecan encode directory and filename listings.- Tools:
gehaxelt/ds-store,lijiejie/ds_store_exp— parse.DS_Storeoffline.
Backup and config artifacts
Probe (adjust for app root and naming conventions):
/.env
/backup.zip
/backup.tar.gz
/wwwroot.rar
/backup.sql
/config.php.bak
/.config.php.swp
Web server misconfiguration signal (example: NGINX)
location /.git { deny all; }— may return 403 for/.git/while still allowing or denying specific subpaths depending on rules.- 403 on a protected location can confirm the route exists; always distinguish from 404 on non-existent paths.
5. DECISION TREE
- Probe
/.git/HEAD→ref: refs/heads/pattern? → run git-dumper / GitTools / GitHacker; reviewconfigandlogs/HEADfor secrets. - Else probe
/.svn/wc.dborentries→ success? → svn-extractor or manualwc.db+ pristine recovery. - Else probe
/.hg/requires→ success? → mercurial dumper. - Else probe
/.bzr/README→ Bazaar tooling or manual path walk. - Parallel: fetch
/.DS_Store,/.env, common backup extensions on app root and parent paths. - Interpret status codes: 403 on directory + 200 on specific files → treat as high priority for file-by-file extraction.
6. RELATED ROUTING
- From recon-for-sec — scope-safe discovery, crawling, and fingerprinting before deep VCS tests.
- From recon-and-methodology — structured methodology and evidence handling.
Note: coordinate with recon skills—set scope and request rate first, then run targeted VCS/backup validation.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
