repo-bleed - GitLite

KO | EN

gitlite — search

#php #kotlin #mcp #security #ai-agents #rag #proxy #pytorch #typescript #graphql

repo-bleed

(★ 9)

High-speed Git history forensic scanner. Detects and locates leaked API keys, Stripe secrets, and credentials buried deep within repository commit patches.

파일 탐색기

ZIP 다운로드

- - python-package-conda.yml
- repo_bleed-1.0.0-py3-none-any.whl
- repo_bleed-1.0.0.tar.gz
- - __init__.cpython-313.pyc
  - cli.cpython-313.pyc
  - rules.cpython-313.pyc
  - scanner.cpython-313.pyc
- __init__.py
- cli.py
- rules.py
- scanner.py
- dependency_links.txt
- entry_points.txt
- PKG-INFO
- requires.txt
- SOURCES.txt
- top_level.txt
bleed.py
dummy_config.py
index.html
pyproject.toml
README.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

# 프로젝트 배지

License: MIT
Python 3.7+
Release
React
Git

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

**REPO-BLEED** is a high-speed, zero-memory-overhead security utility designed to scan entire Git repository histories for leaked API keys, tokens, and private credentials. It features a tactical "nuke" protocol that surgically rewrites the Git commit tree to permanently obliterate compromised files from existence.

---

## ⚡ Core Architecture & Logic

Repo-Bleed is engineered to handle massive, enterprise-scale repositories without crashing system memory.

* **Zero-Overhead Streaming:** Instead of loading the Git history into RAM, the engine utilizes `subprocess.Popen` to create a direct data stream. It reads the Git patch tree line-by-line via a Python generator loop, evaluating and instantly discarding data to maintain near-zero memory footprint.
* **Pre-Compiled Heuristics:** Utilizes pre-compiled Regex engines to detect AWS Access Keys, Stripe APIs, RSA Private Keys, and generic secret assignments `(api_key, token, secret)`.
* **Tactical Payload Destruction (Nuke):** Automates the dangerous `git filter-branch` protocol. After rewriting the history to scrub the target file, it forces immediate garbage collection (`git reflog expire` and `git gc --prune=now`) to shred orphaned memory objects from the local `.git` database.

---

## 🚀 Execution & CLI Protocol
```bash
### 1. Installation
Clone the repository and install the CLI globally via the provided `pyproject.toml` build system:

git clone [https://github.com/GiTaDi-CrEaTe/repo-bleed.git](https://github.com/GiTaDi-CrEaTe/repo-bleed.git)
cd repo-bleed
pip install .

2. Stream Scan (Detection)

Run the scanner in any local Git repository. The engine will parse the entire commit tree across all branches for exposed signatures.
Bash

# Scan the current directory
repo-bleed scan

# Scan a specific repository path
repo-bleed scan /path/to/target/repo

3. Tactical Nuke (Eradication)

If a leak is detected, use the nuke command to rewrite history and destroy the target file across all branches and commits.
Bash

repo-bleed nuke backend/config/secrets.yml

⚠️ WARNING: This is a destructive action. You must run git push origin --force --all afterward to overwrite the remote server.
🌐 Web Dashboard (React/Vite)

Repo-Bleed is currently being integrated with a high-performance React 19 dashboard for visual threat tracking. To boot the local frontend environment:
Bash

cd repo-bleed-web
npm install
npm run dev

⚙️ Tech Stack

Core Engine: Python 3, subprocess pipes, Pre-compiled re modules

Version Control Interface: Native Git CLI commands, Git Garbage Collection

Frontend UI: React 19, Vite, Tailwind CSS (In Development)

Author: Adi