🏆 Problem Solving Statistics

Updated: 17 January 2026 at 11:47:06 PM • Automatic

💻 Competitive Programming Journey

A comprehensive overview of problem-solving achievements across multiple platforms

---

📊 Platform Statistics

🎯 Platform	👤 Profile	✅ Solved	📈 Progress	📅 Updated On	🔄 Mode
Codeforces	MishkatIT	2602		17 January 2026
LeetCode	MishkatIT	412		17 January 2026
Vjudge	MishkatIT	347		17 January 2026
AtCoder	MishkatIT	157		17 January 2026
CodeChef	MishkatIT	126		17 January 2026
CSES	MishkatIT	66		15 January 2026
Toph	MishkatIT	37		17 January 2026
LightOJ	MishkatIT	31		17 January 2026
SPOJ	MishkatIT	18		16 January 2026
HackerRank	MishkatIT	7		17 January 2026
UVa	MishkatIT	7		17 January 2026
HackerEarth	MishkatIT	2		15 January 2026
🎖️ TOTAL		3812	100%	17 January 2026

---

🎯 Latest Solve

📅 Last Solved	🏆 Platform(s)
17 January 2026	CodeChef, Codeforces, Toph, and UVa

---

📅 Last Solved by Platform

🏆 Platform	📅 Last Solved
Codeforces	17 January 2026
CodeChef	17 January 2026
Toph	17 January 2026
UVa	17 January 2026
LeetCode	10 January 2026
AtCoder	29 November 2025
Vjudge	02 October 2025
CSES	18 August 2025
SPOJ	06 May 2025
LightOJ	12 August 2023
HackerRank	01 January 1970
HackerEarth	01 January 1970

---

🌟 Key Highlights

🥇 Top Platform	🎯 Main Focus	📚 Platforms Active
Codeforces	Competitive Programming	12
2602 Problems	Algorithm Mastery	Multi-Platform

---

🎯 Want Your Own Automated Stats Tracker?

✨ Imagine Your Problem-Solving Journey Auto-Updated Daily! ✨

Tired of manually updating your competitive programming stats?
Want a beautiful, automatically updated showcase of your achievements?
Ready to track your progress across 12+ platforms effortlessly?

🎉 You can have the same automated tracking system! 🎉

---

📚 Setup and Usage

🚀 Get Started in 5 Minutes

What you'll get: Your own GitHub README that automatically updates every day with your latest problem-solving statistics from Codeforces, LeetCode, AtCoder, and 9 other platforms!

Prerequisites

• Python 3.8 or higher
• A GitHub account
• pip (Python package manager)

Installation

1. Fork this repository 🍴

   • Visit MishkatIT/ProblemSolvingStats
   • Click the Fork button in the top-right corner
   • Now you have your own copy!

2. Clone your fork 📦

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

3. Install dependencies 📥

   pip install -r requirements.txt

4. Configure your usernames ⚙️

   Edit src/config.py and replace with your platform usernames/IDs:

   # Actual usernames/IDs used in URLs (can be IDs like '165802' for CSES)
   USER_CONFIG = {
       'Codeforces': 'YourUsername',
       'LeetCode': 'YourUsername',
       'AtCoder': 'YourUsername',
       'CSES': 'YourUserID',  # Can be a numeric ID
       # ... update all your platforms
   }
   
   # Display names shown in the README profile table (user-friendly names)
   PROFILE_DISPLAY_NAMES = {
       'Codeforces': 'YourDisplayName',
       'LeetCode': 'YourDisplayName',
       'CSES': 'YourDisplayName',  # Shows nice name even if ID is used in URL
       # ... keeps your profile looking clean and consistent
   }

   💡 Pro Tip: Use PROFILE_DISPLAY_NAMES to show a consistent name across all platforms in the README, even when some platforms require numeric IDs or lowercase usernames.

5. Run it once to test 🧪

   python3 update_stats.py

6. Enable GitHub Actions 🤖

   • Go to your repository's Actions tab
   • Click "I understand my workflows, go ahead and enable them"
   • Your stats will now update automatically every day! 🎊

Running the Scripts

Automatic Update (Recommended):

python3 update_stats.py

✨ This script will:

• 🔄 Fetch your latest statistics from all 12 platforms
• 💾 Save results to stats.json and last_known_counts.json
• 📝 Automatically generate and update your README.md
• 📊 Create beautiful progress badges and tables

Manual Update (When needed):

python3 manual_update.py

🛠️ This script will:

• 📝 Let you manually enter statistics for any platform
• 💡 Perfect when automatic fetching fails
• 🎯 Useful for platforms without APIs

Update README Only:

python3 update_readme.py

This script updates the README.md using existing data from stats.json.

---

🔄 Update Mechanisms

Automatic Updates (GitHub Actions)

• Scheduled to run daily at 11:40-11:47 PM BDT (randomized timing)
• Automatically fetches statistics from platforms with working APIs
• Failed platforms fall back to last known values with date stamps
• Updates are committed and pushed automatically to the repository

🔄 Smart Schedule Adjustment

The repository features an intelligent scheduling system that adapts to your solving patterns:

Current Status: 🟢 Active - Updates running daily (you're actively solving problems!)

How it works:

• Active Mode (Daily): Runs every day when you're consistently solving problems
• Inactive Mode (Monthly): Automatically switches to monthly updates after 90 consecutive days without solving any problems
• Automatic Recovery: Detects when you solve a new problem and immediately switches back to daily updates

Why this matters:

• Saves GitHub Actions minutes during study breaks, vacations, or busy periods
• Ensures timely updates when you're actively practicing
• No manual intervention needed - the system manages itself
• Prevents unnecessary daily runs when your stats aren't changing

The schedule check runs before each update, making the decision based on your most recent solve date across all platforms.

Manual Updates

If you need to update statistics manually:

1. Run python3 manual_update.py to input current statistics
2. The script will prompt you to visit each platform and enter the current solve count
3. Statistics are automatically saved and the README is updated

Note: Each platform shows the last update date and mode (Automatic/Manual) in the statistics table.

---

🤝 Contributing

We welcome contributions! Whether you want to report bugs, suggest features, improve documentation, or add new platform support, your help is appreciated.

Please see CONTRIBUTING.md for detailed guidelines on how to contribute to this project.

---

📁 Project Structure

ProblemSolvingStats/
├── src/                          # Shared modules (NEW)
│   ├── __init__.py              # Package initialization
│   ├── config.py                # Centralized configuration
│   ├── data_manager.py          # JSON data operations
│   └── utils.py                 # Shared utility functions
├── .github/
│   └── workflows/
│       └── update-stats.yml     # GitHub Actions workflow
├── update_stats.py              # Main statistics fetcher
├── update_readme.py             # README generator
├── manual_update.py             # Manual input script
├── requirements.txt             # Python dependencies
├── last_known_counts.json       # Cached statistics
├── .gitignore                   # Git ignore rules
└── README.md                    # This file

Key Files

• src/config.py: All configuration constants (usernames, URLs, colors, etc.)
• src/utils.py: Shared utility functions (date formatting, calculations, etc.)
• src/data_manager.py: Handles all JSON file operations
• update_stats.py: Fetches stats from 12 platforms via APIs and web scraping
• update_readme.py: Generates and updates the README with statistics
• manual_update.py: Interactive script for manual statistics input
• last_known_counts.json: Stores last successful fetch for each platform

---

🛠️ Architecture Improvements

Recent Refactoring (2026-01-16)

The codebase has been significantly refactored to improve maintainability:

✨ What Changed:

1. Created src/ module - Centralized shared code
2. Eliminated duplication - Removed 327+ lines of repeated code (~20% reduction)
3. Single source of truth - All configs now in src/config.py
4. Reusable utilities - Common functions in src/utils.py
5. Centralized data management - All JSON operations in src/data_manager.py

📊 Refactoring Statistics:

• update_stats.py: 78 lines removed (10.7% reduction)
• update_readme.py: 169 lines removed (22% reduction)
• manual_update.py: 80 lines removed (42.5% reduction)

✅ Benefits:

• Easier to maintain and update
• Consistent behavior across all scripts
• Reduced chance of bugs from duplicate code
• Clearer separation of concerns
• Better code organization

---

Continuous Learning & Growth

"The only way to do great work is to love what you do."