Code Archive
Automatically sync coding solutions to GitHub from any platform. One dashboard for streaks, heatmaps, and unified performance stats.
As of June 2026, Code Archive has 1 users in the Developer Tools category.
Usersno change0%
1
1
Ratingno change0%
—
— reviews
Reviewsno change0%
—
Version
1.0.0
Manifest V3
History
4 snapshotsTracking since Apr 9, 2026.
Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
| Date | Users | Rating | Reviews | Version |
|---|---|---|---|---|
| Apr 9, 2026 | — | — | — | 1.0.0 |
| Apr 20, 2026 | — | — | — | 1.0.0 |
| Apr 25, 2026 | — | — | — | 1.0.0 |
| Jun 2, 2026 | — | — | — | 1.0.0 |
| Now | 1 | — | — | 1.0.0 |
Permissions & access
- Permissions
- storagenotificationsidentity
- Host access
- https://leetcode.com/*, https://codeforces.com/*, https://github.com/*, https://api.github.com/*
Screenshots
About
Code Archive is a developer tool for competitive programmers who take their craft seriously. Every solution you write deserves to be preserved — with context, with history, and with the depth of a proper engineering record. When you submit a solution on LeetCode or Codeforces, Code Archive detects the successful submission, extracts the full source code, and commits it to your GitHub repository — automatically, silently, and exactly the way you configured it. No copy-pasting. No context-switching. No forgetting to save that clean accepted solution before you close the tab. HOW IT WORKS: Install the extension, connect your GitHub account, and keep coding. The moment a submission is accepted, Code Archive commits your solution in the background. By the time you look up, the solution is already in your repository — with the problem name, difficulty, language, and runtime in the commit message, and a structured README alongside the code file. GITHUB SETUP: Connect via GitHub OAuth in one click, or enter a Personal Access Token manually. Either method authenticates directly with the GitHub API — your credentials are stored locally in Chrome and are never processed by any external server. Repository configuration gives you two modes: → Single repository — all solutions from all platforms land in one repo, organised into sub-folders per platform and problem. Clean and consolidated. → Per-platform repositories — each platform writes to a dedicated repo. Ideal if you want a clean separation between your LeetCode practice and your competitive Codeforces record. COMMIT FORMAT: Every commit message is generated from the problem's own metadata. You control exactly what goes into it. Choose your commit style: • Conventional commits → feat(leetcode): Two Sum — Easy — Runtime 98% • Simple format → Two Sum — Easy — O(n) Toggle individual fields on or off: • Problem difficulty (Easy / Medium / Hard, or rating band on Codeforces) • Runtime and memory performance percentages • Direct link to the original problem AUTOMATED README GENERATION: Every solution receives a structured README file committed alongside the source code. The README is built from the problem's own metadata and each field is individually configurable: • Problem link — direct URL back to the original problem page • Difficulty label • Problem topics and tags • Runtime and memory acceptance percentages • Problem hints, committed privately to your own repository The README turns each entry in your repository from a bare code file into a self-documented record — readable, searchable, and meaningful long after the contest is over. PLATFORM MANAGEMENT: Enable or disable platforms independently. If you only want to archive LeetCode solutions, turn Codeforces off — the popup adapts instantly to show only your active platforms. Drag and drop platform cards to reorder them in the popup tab strip. A live preview in the settings page shows you exactly what the popup will look like before you save. No guessing. Currently supported: • LeetCode — all difficulty tiers, per-difficulty folder structure • Codeforces — solutions organised by rating band (800–1199, 1200–1999, 2000+) Coming soon: GeeksForGeeks, CodeChef, Coding Ninjas, and more. STATS DASHBOARD: The full-year stats dashboard aggregates your complete submission history into a single analytics view. Everything is cross-platform by default, with a platform filter to drill into a single source when needed. ACTIVITY HEATMAP: A full 52-week calendar grid. Each square represents one day; colour intensity scales with the number of solutions committed that day. The heatmap gives you an honest, unadorned view of your consistency over the entire year — the kind of accountability a scoreboard does not provide. STREAKS: • Current streak — consecutive days with at least one committed solution • Longest streak — the best run you have sustained this year • Active days — distinct days with at least one submission in the current year SUBMISSION TOTALS: Year-to-date count across all active platforms, updating live as new solutions are archived. Filtered independently when a specific platform is selected. SUBMISSION CHART: A bar chart of your submission volume plotted over time. Visualise your productive periods, identify idle stretches, and correlate activity with performance improvement. LANGUAGE BREAKDOWN: A ranked breakdown of every programming language used across all your archived solutions — from your primary language down to the occasional experiment. Proportions update dynamically when the platform filter changes. PLATFORM TREND CHART: Submission volume over time, broken down by platform side by side. Switch between yearly, monthly, and weekly granularity with independent drill-down controls. Understand where your practice time goes, how it has shifted between platforms, and which periods drove the most growth. All stats are computed locally from your archived submission history. Nothing leaves your browser. NOTIFICATIONS: Choose how Code Archive notifies you after each sync: • All activity — a notification on every successful push, and on any failure • Errors only — silent on success; you are notified only if something goes wrong • Disabled — no notifications; all activity is still logged in the popup PRIVACY: Code Archive has no backend. It does not collect, transmit, or store any data on external servers. Your GitHub token is stored in Chrome's encrypted sync storage. It is used solely to authenticate calls to the GitHub API on your behalf — it is never read, cached, or relayed by Code Archive. Your solution code is committed directly from your browser to your own GitHub repository. No third party ever receives it. Settings can be exported as a JSON file at any time from the Advanced settings page. The export deliberately excludes your GitHub token. This gives you a portable backup of your preferences that can be restored on a new machine. ADVANCED SETTINGS: • Export your full configuration as a JSON file (token excluded for security) • Import a previously exported configuration to restore preferences • Clear all extension data and return to defaults • Debug mode for diagnosing sync issues with detailed console logging Code Archive is built for developers who treat their solutions as a body of work worth keeping — not just a score on a leaderboard. If you are working through LeetCode problem sets, building a Codeforces competitive record, or simply want every accepted solution preserved with full context, Code Archive makes that automatic.
Technical
- Version
- 1.0.0
- Manifest
- V3
- Size
- 145KiB
- Min Chrome
- 88
- Languages
- 1
- Featured
- No
Metadata
- ID
- opgilphfmkcgihomjllcamlmphiddjbm
- Developer ID
- uc89f68f34219184d72fcdb9eb6d34ec6
- Developer Email
- [email protected]
- Created
- Apr 9, 2026
- Last Updated (Store)
- Apr 9, 2026
- Last Scraped
- Jun 8, 2026
- Website
- nipunrathore.com
Data sourced from the Chrome Web Store · last verified Jun 8, 2026.