GitHub + GitLab + local Git

Your code has been keeping a diary.

Gitrospective combines the activity visible on GitHub and GitLab with the Git history on your computer. You get a private calendar of the projects you worked on.

  • Read-only access
  • Source code stays local
  • Cloud and local history
  • Private archive
Personal work archive 2012 to 2026

14 years in code

4,831 active days
GitHub GitLab Local Git

01 / The missing record

The green graph leaves a lot out.

GitHub can show one part of your work. GitLab may hold another. Old experiments can exist only as local clones. Gitrospective reads the dates that remain available and puts them on the same calendar.

What GitHub history includes

02 / Sources

What each source contributes.

01

Cloud record

GitHub

Annual calendars, repositories, commits, pull requests, issues, reviews and restricted totals exposed to your account.

About GitHub history
02

Cloud record

GitLab

Membership and contributed projects, plus the commits, merge requests and issues authored by your account.

About GitLab history

03 / Import

How the archive is built.

  1. 01

    Connect an account

    Sign in with GitHub or GitLab. Gitrospective only makes read requests.

  2. 02

    Add local repositories

    Run the CLI on any computer that still has useful Git history.

  3. 03

    Match remotes

    Matching cloud mirrors contribute zero local commits to the combined total.

  4. 04

    Browse by year

    Open a year to see its active days, projects and organizations.

See exactly how it works

04 / Data

What leaves your computer.

Provider tokens are encrypted in the database. The local scanner uploads dates, counts, project names and normalized remotes. It skips source code and commit messages.

Read the privacy and data principles

Start with the history you still have.

Open your archive.

Open your archive Start with a developer year in review