leetvault

Mirror your LeetCode account (accepted submissions + source code + metadata) into a normalized SQLite database and a GitHub repository with an auto-generated README dashboard.

Sync is account-based, driven by your authenticated LeetCode session — not a browser extension. Your LeetCode account is the single source of truth. Free and open source; the only external services involved are LeetCode and GitHub.

Install

pip install leetvault

Requires Python 3.11+. See docs/DEVELOPER.md for an editable/dev install.

Quickstart

leetvault login                                          # paste LEETCODE_SESSION + csrftoken
leetvault config repo_url https://github.com/you/repo.git # optional: enable GitHub push
leetvault import                                          # one-time full history
leetvault sync                                             # incremental, run anytime
leetvault watch                                             # or: poll automatically

Commands

leetvault login — store your LEETCODE_SESSION + csrftoken (and optionally a GitHub PAT) in the OS keyring.
leetvault import [--keep-all] — full history import of every accepted submission (resumable, one-time per site).
leetvault sync [--keep-all] — incremental sync of new accepted submissions since the last run.
leetvault watch — poll LeetCode and sync automatically (--interval, default 90s).
leetvault status — show session validity/expiry and sync state.
leetvault logout — remove stored credentials.
leetvault config — get/set persistent configuration (repo URL, DB path, dedup window, ...).

`--keep-all`

By default, import/sync keep only the newest accepted submission per problem within a rolling 24-hour window (dedup_window_seconds in leetvault config, default 86400) — solving the same problem twice in one sitting doesn't clutter history with near-duplicate attempts. --keep-all disables that and stores every accepted submission individually:

leetvault sync --keep-all      # one-off: keep everything from this run onward
leetvault import --keep-all    # same, for the initial full-history import

To make this the permanent default instead of retyping the flag every time:

leetvault config dedup_window_seconds 0

--keep-all only changes how future submissions are processed — it can't retroactively recover a submission an earlier (non---keep-all) run already deduped, since sync only walks forward from the last submission it saw. See docs/TROUBLESHOOTING.md if you hit that.

What gets stored

A normalized SQLite database (problems, submissions, source code, topics, sync state) plus a disk layout per problem:

Problems/<slug>/
  latest.<ext>          the most recent accepted submission
  history/submission_<id>.<ext>   every kept accepted submission
  metadata.json          difficulty, topics, runtime/memory percentiles, ...
  notes.md                yours - never overwritten once created
README.md                 auto-generated dashboard: progress, streaks, full solutions table,
                          and clickable topic tags that jump to a per-topic problem list

Deduplicated by default within a 24h window — see --keep-all above to change that.

Honest limits

watch is polling (default 90s, configurable), not a real-time push — LeetCode has no public webhook/streaming API.
LeetCode may Cloudflare-challenge automated HTTP clients; leetvault fails gracefully rather than faking success.
Storing session cookies for automated access may be against LeetCode's Terms of Service. Use at your own risk, against your own account only.
LeetCode has no official API — every endpoint leetvault uses is reverse-engineered and could change without notice.

Docs

docs/ARCHITECTURE.md — data flow, module responsibilities, and every place live API behavior diverged from initial assumptions.
docs/DEVELOPER.md — dev setup, project layout, running checks.
docs/FAQ.md
docs/TROUBLESHOOTING.md
CONTRIBUTING.md
CHANGELOG.md

License

MIT — see LICENSE.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

leetvault-0.2.0.tar.gz (42.4 kB view details)

Uploaded Aug 4, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

leetvault-0.2.0-py3-none-any.whl (26.3 kB view details)

Uploaded Aug 4, 2026 Python 3

File details

Details for the file leetvault-0.2.0.tar.gz.

File metadata

Download URL: leetvault-0.2.0.tar.gz
Upload date: Aug 4, 2026
Size: 42.4 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for leetvault-0.2.0.tar.gz
Algorithm	Hash digest
SHA256	`b4513a0860423ecdb747fb0937f150336ce75cb0eda9e6ea15f696a35ee37c2b`
MD5	`22552acdb030dbf56d2e9664bf7a989c`
BLAKE2b-256	`1cb4a35475308e1b8168283ef924d8a87b308fbb367c5d2ad202dda40b38e8d0`

See more details on using hashes here.

Provenance

The following attestation bundles were made for leetvault-0.2.0.tar.gz:

Publisher: publish.yml on priyadip/LeetVault

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: leetvault-0.2.0.tar.gz
- Subject digest: b4513a0860423ecdb747fb0937f150336ce75cb0eda9e6ea15f696a35ee37c2b
- Sigstore transparency entry: 2340388079
- Sigstore integration time: Aug 4, 2026
Source repository:
- Permalink: priyadip/LeetVault@cefd8e494e9e26491a5097ea9b7e49799f9aafce
- Branch / Tag: refs/tags/v0.2.0
- Owner: https://github.com/priyadip
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: publish.yml@cefd8e494e9e26491a5097ea9b7e49799f9aafce
- Trigger Event: push