Skip to content
Ahmadraza970Public

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

Β 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 

Repository files navigation

πŸ” ProofCode

Find Real Security Bugs. Patch Code. Prove The Fix.

ProofCode is an AI-powered code security platform designed to help developers identify vulnerabilities, understand security issues, generate automated patches, and verify whether those fixes actually work.

Instead of stopping at vulnerability detection or AI-generated suggestions, ProofCode creates a verification loop:

Detect β†’ Explain β†’ Patch β†’ Re-scan β†’ Test β†’ Verify


🚨 The Problem

Modern developers increasingly use AI coding assistants and rapid "vibe coding" to build applications.

This makes development faster β€” but it can also introduce security vulnerabilities that are difficult to identify manually.

Traditional tools often create another problem:

Finding a vulnerability doesn't automatically mean the developer knows how to fix it correctly.

And an AI-generated patch shouldn't simply be trusted.

Developers need a system that can answer:

"Was the vulnerability actually fixed?"


πŸ’‘ Our Solution

ProofCode analyzes a codebase, detects security vulnerabilities, explains the findings, generates fixes, and then verifies the modified code through re-scanning and testing.

The workflow

Codebase
   ↓
Repository Analysis
   ↓
Security Detection
   ↓
Vulnerability Explanation
   ↓
AI-Generated Patch
   ↓
Re-scan
   ↓
Test Execution
   ↓
Verified Result

✨ Key Features

πŸ” Vulnerability Detection

Analyze a project and identify potentially dangerous code patterns and security vulnerabilities.

πŸ€– AI-Assisted Patching

Generate automated patches for detected security issues.

πŸ”„ Re-scan After Fix

The patched code is analyzed again instead of assuming the generated fix is correct.

πŸ§ͺ Test Verification

Run the project's tests after applying patches to provide additional confidence in the result.

πŸ“Š Security Health Score

Track the security state of a project through an easy-to-understand score.

πŸ“Έ Snapshot Timeline

Keep track of different analysis states and security improvements over time.

πŸ”Œ Developer API

Access ProofCode capabilities through a developer-facing REST API.


🎬 Example

In our demo, ProofCode analyzes an Express Payments & User API project.

Before

Security Score: 40/100

The project contains multiple security vulnerabilities, including examples such as:

  • Unsafe dynamic code execution
  • Cross-site scripting risks

After Automated Patching

Security Score: 93/100

ProofCode reports:

5 open security vulnerabilities fixed

The codebase is then re-scanned and tested to verify the resulting state.


🧠 Why ProofCode?

Most AI coding tools focus on:

"Can AI generate or modify this code?"

ProofCode focuses on:

"Can we verify that the security problem was actually fixed?"

That's the core idea behind ProofCode.

Detect β‰  Fix β‰  Verify

A vulnerability scanner can detect a problem.

An AI coding assistant can generate a patch.

ProofCode connects these steps into a single workflow and adds verification.


πŸ—οΈ Architecture

                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚     Developer       β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
                              β–Ό
                 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                 β”‚   ProofCode Dashboard  β”‚
                 β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
                 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                 β”‚                         β”‚
                 β–Ό                         β–Ό
        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”       β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
        β”‚ Repository Inputβ”‚       β”‚  Developer API  β”‚
        β”‚ ZIP / GitHub    β”‚       β”‚                 β”‚
        β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜       β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                 β”‚                         β”‚
                 β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚ Repository Analysis β”‚
                   β”‚    / AST Layer      β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚ Security Detection  β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚   AI Patch Engine   β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚    Re-scan Code     β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚   Test Execution    β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚ Verification Result β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ› οΈ Tech Stack

Update this section to exactly match the technologies used in your implementation.

Frontend

  • React
  • TypeScript
  • Vite
  • Tailwind CSS

Backend / API

  • REST API
  • Repository analysis pipeline

Security / Analysis

  • AST-based code analysis
  • Security vulnerability detection
  • Automated patch generation
  • Re-scanning and verification

AI

  • AI-assisted vulnerability explanation
  • AI-assisted patch generation

πŸš€ Getting Started

1. Clone the repository

git clone https://github.com/YOUR_USERNAME/proofcode.git
cd proofcode

2. Install dependencies

npm install

3. Configure environment variables

Create a .env file and add the required configuration:

# Add your project-specific environment variables here

4. Start the development server

npm run dev

Open the local development URL shown in your terminal.


πŸ“‚ Project Structure

proofcode/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ components/
β”‚   β”œβ”€β”€ pages/
β”‚   β”œβ”€β”€ services/
β”‚   └── ...
β”œβ”€β”€ public/
β”œβ”€β”€ README.md
β”œβ”€β”€ package.json
└── ...

Update the structure above to match the actual repository before publishing.


🎯 Use Cases

ProofCode can be useful for:

  • πŸ‘¨β€πŸ’» Individual developers
  • ⚑ AI-assisted / vibe coding workflows
  • 🏒 Startups
  • πŸ” Security-conscious development teams
  • πŸ§ͺ Development and testing workflows
  • πŸ”Œ Developer platforms integrating security checks

πŸ† Hackathon Pitch

The Problem

AI makes it easier than ever to write software β€” but faster code generation can also introduce security problems.

The Solution

ProofCode creates an automated loop that:

Finds β†’ Explains β†’ Fixes β†’ Re-scans β†’ Tests β†’ Verifies

The Difference

We don't want developers to blindly trust an AI-generated patch.

We want to prove the fix.


πŸ—ΊοΈ Roadmap

Phase 1 β€” Current

  • Repository analysis
  • Vulnerability detection
  • Vulnerability explanations
  • Automated patching
  • Re-scanning
  • Test verification
  • Security scoring
  • Snapshot history
  • Developer API

Phase 2 β€” Next

  • Pull Request security scanning
  • CI/CD integration
  • More programming languages
  • Improved patch confidence scoring
  • Continuous repository monitoring

Phase 3 β€” Vision

Build an automated security layer for AI-generated software that continuously checks whether code remains secure as it evolves.


🀝 Contributing

Contributions, ideas, and feedback are welcome.

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Test your changes
  5. Open a pull request

⚠️ Disclaimer

ProofCode is a developer security tool and should be used as one layer of a broader secure-development process.

Automated analysis and patches should be reviewed and validated before being used in production environments.


πŸ‘₯ Team

Built with ❀️ for the hackathon.

ProofCode

Don't just generate code.

Prove it's secure. πŸ”


πŸ“œ License

Add your chosen open-source license here.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages