insecure-source-code-management

Detect exposed .git, .svn, and .hg metadata during authorized assessments.

5|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Yliken/ai4 --skill insecure-source-code-management-yliken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insecure-source-code-management
Source: https://github.com/Yliken/ai4/tree/main/skills/insecure-source-code-management
Command: npx skills add https://github.com/Yliken/ai4 --skill insecure-source-code-management-yliken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exposed version-control metadata and backup/config artifacts create serious security risks during authorized assessments. This skill helps identify leaks from Git, SVN, Mercurial repositories, and common backups or environment configs so teams can scope remediation safely.

Core Features & Use Cases

  • Detect exposed metadata and artifacts from .git, .svn, .hg, and backup/config files (e.g., .env, backup.zip) during authorized tests.
  • Provide guided recovery and evidence handling using open-source tooling within an approved scope.
  • Ideal for reconnaissance and risk assessment where misconfigurations or data exposures could occur on web apps, repositories, or hosting environments.

Quick Start

Probe common exposure paths such as /.git/HEAD, /.git/config, /.svn/entries, /.svn/wc.db, /.hg/requires, and /.env to identify leaks, then review results with approved tooling.

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 has exposed .git or .svn repository metadata?

To check for exposed version-control metadata, probe common paths like /.git/HEAD, /.git/config, or /.svn/entries during authorized assessments. This skill identifies leaks from Git, SVN, and Mercurial repositories to help scope remediation safely.

What is exposed version-control data and why is it a security risk during recon?

Exposed version-control data includes accessible .git, .svn, or .hg metadata and backup artifacts like .env files. These create serious security risks during recon because they leak source code, configurations, and environment secrets that attackers can exploit.

How can I detect leaked .env files and backup archives on web applications?

You can detect leaked environment files and backups by probing paths such as /.env or /backup.zip. This skill identifies misconfigurations and data exposures across web apps and hosting environments to guide safe evidence handling.

Can I recover exposed Git repository data safely within an approved testing scope?

Yes, you can recover exposed Git data safely using open-source tooling within an approved scope. This skill provides guided recovery workflows and safe data handling procedures for authorized vulnerability testing and risk assessment.

What paths should I probe to find Mercurial repository exposures on web servers?

To find Mercurial exposures, probe paths like /.hg/requires on web servers. This skill detects exposed version-control metadata across websites and server environments, supporting reconnaissance where misconfigurations are suspected.