LidBridge

Clean your projects. Push to GitHub. In seconds.

---

📖 What is LidBridge?

LidBridge is an open-source desktop application that helps developers clean their local project directories and publish them to GitHub — with one click.

No more manually deleting node_modules, __pycache__, .next, or target folders before sharing your code. LidBridge handles all of that automatically, detects secret files before they leak, and pushes your clean project to a new GitHub repository.

Ideal for developers preparing projects for AI code review with ChatGPT, Claude, or Gemini — clean once, push instantly, no terminal required.

---

✨ Features

Feature	Description
🧹 Smart Cleaning	Automatically removes 30+ types of junk directories and files
🔍 Secret Detection	Scans for exposed API keys, tokens, and passwords before pushing
🚀 One-Click Push	Creates a GitHub repository and pushes your code in one step
🏢 Org Support	Push to personal accounts or any GitHub Organization you belong to
📊 Project Scan	Displays file statistics before cleaning
🌍 Multilingual UI	Supports English, Arabic, French, Hindi, and Chinese
📜 Repo History	Tracks all repositories created through the app

---

🖥️ Supported Platforms

Platform	Status
Windows 10/11	✅ Fully supported
macOS	✅ Supported (requires build on macOS)
Linux	✅ Supported (requires build on Linux)

---

🏗️ Tech Stack

Layer	Technology
Desktop Framework	Tauri v2
Backend	Rust
Frontend	Next.js 14 + TypeScript
Styling	Tailwind CSS
Local Database	SQLite (via rusqlite)
Git Operations	git2 (libgit2 — no system Git required)
Analytics DB	PostgreSQL (optional, via sqlx)

---

🚀 Getting Started

Prerequisites

• Node.js ≥ 18
• Rust (stable toolchain)
• Tauri CLI prerequisites for your platform

1. Clone the Repository

git clone https://github.com/lidprex/lidbridge.git
cd lidbridge

2. Configure Environment Variables

cp .env.example .env

Open .env and fill in your values:

GITHUB_CLIENT_ID=your_github_client_id
GITHUB_CLIENT_SECRET=your_github_client_secret
DATABASE_URL=postgresql://...   # Optional — leave empty to disable analytics

3. Set Up GitHub OAuth App

1. Go to github.com/settings/developers
2. Click New OAuth App
3. Fill in:
   • Application name: LidBridge
   • Homepage URL: http://localhost:3000
   • Authorization callback URL: http://localhost:2026/callback
4. Copy the Client ID and Client Secret into your .env

4. Set Up GitHub App Private Key (Optional — for Org push)

If you want to push to GitHub Organizations via a GitHub App:

1. Go to github.com/settings/apps
2. Create or select your GitHub App
3. Generate a private key
4. Place the file at: src-tauri/src/keys/private-key.pem

⚠️ The private key is listed in .gitignore and will never be committed.

5. Install Dependencies

npm install

6. Run in Development Mode

npm run tauri dev

---

🔨 Building for Production

npm run tauri build

The installer will be generated in src-tauri/target/release/bundle/.

---

📁 Project Structure

lidbridge/
├── src/                        # Next.js frontend
│   └── app/
│       ├── page.tsx            # Main application UI
│       ├── layout.tsx          # Root layout
│       └── globals.css         # Global styles & design tokens
│
├── src-tauri/                  # Rust/Tauri backend
│   ├── src/
│   │   ├── lib.rs              # Application entry point & Tauri commands
│   │   ├── main.rs             # Binary entry point
│   │   ├── auth/               # GitHub OAuth authentication
│   │   ├── cleaner/            # Project scanning & cleaning engine
│   │   ├── db/                 # Local SQLite + optional PostgreSQL
│   │   ├── git/                # Git operations via libgit2
│   │   ├── github_app.rs       # GitHub App JWT token generation
│   │   └── keys/               # Private key storage (gitignored)
│   ├── build.rs                # Build script — bakes env vars at compile time
│   ├── Cargo.toml              # Rust dependencies
│   └── tauri.conf.json         # Tauri window & bundle configuration
│
├── .env.example                # Environment variable template
├── .gitignore                  # Protects secrets from being committed
├── package.json                # Node.js scripts & dependencies
└── README.md                   # This file

---

🧹 What Gets Cleaned?

LidBridge removes the following categories of files and directories:

Category	Examples
Version Control	.git/, .svn/, .hg/
Package Managers	node_modules/, .npm/, bower_components/
Build Outputs	dist/, build/, target/, out/, .next/
Python	__pycache__/, .venv/, .tox/, *.pyc
IDE Files	.idea/, .vscode/, .vs/
Lock Files	package-lock.json, yarn.lock, Cargo.lock
OS Artifacts	.DS_Store, Thumbs.db, desktop.ini
Archives	.zip, .tar.gz, .rar, .7z
Logs	*.log, logs/
Environment	.env, .env.local, .env.production

---

🔒 Security

LidBridge scans your project for common secret patterns before pushing:

• GitHub tokens (ghp_, gho_, ghu_, ghs_)
• OpenAI API keys (sk-...)
• AWS Access Keys (AKIA...)
• Google API keys (AIza...)
• Stripe keys (sk_live_...)
• Discord bot tokens
• Generic api_key=, password=, token= patterns

---

🤝 Contributing

1. Fork the repository
2. Create a feature branch: git checkout -b feature/my-feature
3. Commit your changes: git commit -m 'feat: add my feature'
4. Push to the branch: git push origin feature/my-feature
5. Open a Pull Request

Please make sure you do not commit .env or private-key.pem.

---

📄 License

This project is licensed under the GNU General Public License v3.0. See LICENSE.txt for the full license text.

LidBridge — Copyright (C) 2025 Lidprex Labs
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under the conditions of the GNU GPL v3.

---

🔗 Links

🌐 Website	lidprex.onrender.com
🧪 Labs	lidprex-labs.onrender.com
👤 Lead Developer	github.com/bxat01
🏢 Organization	github.com/lidprex
📦 RepoPrep	repoprep.onrender.com

---

_{Built with ❤️ by Lidprex Labs}