langbyyi/cyberstrikeai-src/insecure-source-code-management
Claude Code and agent skill by langbyyi/cyberstrikeai-src
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install langbyyi/cyberstrikeai-src/insecure-source-code-managementSKILL.md
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):
中文路由提示:快速扫这些路径;若需完整侦察流程,从 recon-for-sec、recon-and-methodology 技能载入方法论后再深入。
1. GIT EXPOSURE
Detection
- `/.git/HEAD` — valid repo often returns plain text like:
- `/.git/config` — may expose
remote.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.
- `403` on `/.git/` — directory may exist but listing is denied; still try direct file URLs:
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:
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.
Recovery
- `sahildhar/mercurial_source_code_dumper` — dumps repository when store paths are reachable.
4. OTHER LEAKS
Bazaar (Bzr)
- Probe `/.bzr/README` and `/.bzr/branch-format` for Bazaar metadata.
macOS .DS_Store
- `/.DS_Store` can 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):
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.db` or `entries` → success? → svn-extractor or manual
wc.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](../recon-and-methodology/SKILL.md) — scope-safe discovery, crawling, and fingerprinting before deep VCS tests.
- From [recon-and-methodology](../recon-and-methodology/SKILL.md) — structured methodology and evidence handling.
中文:与侦察类技能联动——先定范围与速率,再针对 VCS/备份做定向验证。
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/insecure-source-code-management/SKILL.md
Popularity
- Repository stars
- 128
- Repository forks
- 5
- 7-day trend score
- 24
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 22 Oct 2026, 14 days ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/langbyyi/cyberstrikeai-src/insecure-source-code-management)