Implement comprehensive dead code detection system for Carbon Credit platform

[Copilot]

Overview

This PR implements a comprehensive dead code detection system that identifies unused code, dead files, and potential optimizations across all components of the Carbon Credit platform (React frontend, Python backend, and Solidity smart contracts).

Problem Statement

The codebase lacked tooling to detect:

• Unused functions, variables, and imports
• Dead files that are not referenced anywhere
• Unused dependencies
• Unreachable code paths

Solution

Added a multi-component dead code analysis system with the following tools:

Frontend (React/JavaScript)

• unimported: Finds unused files and dependencies
• depcheck: Analyzes dependency usage
• ts-unused-exports: Detects unused exports

Backend (Python/Flask)

• vulture: Finds dead code with confidence scoring
• unimport: Detects unused imports
• pyflakes: Identifies unused variables and code quality issues

Smart Contracts (Solidity)

• Custom analysis: Scans for unused functions, variables, and events
• depcheck: Analyzes dependency usage
• solhint support: Optional enhanced linting

Key Features

🔧 Easy to Use

# Run complete analysis across all components
npm run analyze:dead-code

# Or analyze individual components
npm run analyze:frontend
npm run analyze:backend  
npm run analyze:contracts

📊 Comprehensive Reports

• Structured JSON reports for programmatic use
• Human-readable TXT reports for manual review
• HTML dashboard with consolidated results
• Confidence scoring to prioritize findings

🎯 Current Findings

• Frontend: 9 unused dependencies, 2 unimported files
• Backend: 58 potential issues (27 dead code, 11 unused imports, 20 code quality issues)
• Smart Contracts: 1 unused dependency, detailed analysis of 15 functions and 11 variables

Files Added

• analyze-dead-code.sh - Main orchestration script
• client/analyze-dead-code.js - Frontend analysis
• backend/analyze-dead-code.py - Backend analysis
• smartContracts/analyze-dead-code.js - Smart contracts analysis
• DEAD_CODE_ANALYSIS.md - Comprehensive documentation
• package.json - Root-level npm scripts

Usage Examples

Complete Analysis

./analyze-dead-code.sh

Component-Specific Analysis

cd client && npm run analyze:dead-code
cd backend && python3 analyze-dead-code.py
cd smartContracts && node analyze-dead-code.js

Report Structure

dead-code-reports/
├── consolidated-report.json
├── index.html
├── frontend/
│   ├── unimported-analysis.txt
│   ├── depcheck-analysis.json
│   └── summary.json
├── backend/
│   ├── vulture-analysis.txt
│   ├── unimport-analysis.txt
│   └── pyflakes-analysis.txt
└── smartcontracts/
    ├── contracts-analysis.json
    └── dependencies-analysis.json

CI/CD Integration

The system is designed for easy CI/CD integration:

- name: Run Dead Code Analysis
  run: |
    chmod +x ./analyze-dead-code.sh
    ./analyze-dead-code.sh

Benefits

1. Improved Code Quality: Identify and remove unused code
2. Reduced Bundle Size: Remove unused dependencies
3. Better Maintainability: Cleaner codebase with less dead code
4. Automated Detection: Regular analysis prevents accumulation of dead code
5. Actionable Reports: Confidence scoring helps prioritize cleanup efforts

Safety Features

• Confidence scoring: Tools provide confidence levels for safe removal
• Non-destructive: Analysis only identifies issues, doesn't modify code
• Comprehensive documentation: Clear guidance on interpreting results
• Backup recommendations: Suggests testing before removing code

Next Steps

1. Review the generated reports in dead-code-reports/
2. Prioritize high-confidence findings for cleanup
3. Integrate into CI/CD pipeline for ongoing monitoring
4. Use findings to optimize bundle sizes and improve performance

The analysis reveals significant opportunities for code cleanup, particularly in the backend where 58 potential issues were identified with varying confidence levels.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• binaries.soliditylang.org
  • Triggering command: node /home/REDACTED/work/Carbon-Credit/Carbon-Credit/smartContracts/node_modules/.bin/hardhat test (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
carbon-credit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 17, 2025 10:30am