lastgen

Check if you started coding before or after AI agents.

Claude Code shipped publicly on February 21, 2025. If your earliest verifiable commit is before that date, you get classified as Last Gen. If it's after, AI Native.

Try it in your browser →

[!IMPORTANT] This is a novelty tool for fun. It is not a measure of skill or credibility.

Installation

npx lastgen <username>

[!TIP] Requires Node.js 22.18.0+ (uses native TypeScript execution). No build step needed.

For authenticated requests (5,000 req/hour instead of 60):

export GITHUB_TOKEN=ghp_your_token_here
npx lastgen <username>

Usage

# Classify a GitHub user
npx lastgen torvalds

# Save certificate to file
npx lastgen --json torvalds > proof.json

# Verify a saved certificate
npx lastgen verify proof.json

# Get a README badge
npx lastgen --badge torvalds

# JSON output
npx lastgen --json torvalds

# Launch web UI locally
npx lastgen serve

Options

--token <token>       GitHub personal access token
--json                Output as JSON
--badge               Output as README badge markdown
--port <port>         Port for web UI (default: 3000)
--no-color            Disable colors
-h, --help            Show help
-v, --version         Show version

Environment

GITHUB_TOKEN          GitHub token (alternative to --token)
NO_COLOR              Disable colors (any value)

Certificate

Running lastgen <username> generates a certificate like this:

+----------------------------------------------------+
|                LASTGEN CERTIFICATE                 |
+----------------------------------------------------+
| Certificate  LGC-3476-525342                       |
| Issued       2026-02-19                            |
|                                                    |
| Developer    torvalds (Linus Torvalds)             |
| Era          Last Generation Coder                 |
|              Wrote code before AI agents shipped   |
|                                                    |
| Proof Commit torvalds/linux                        |
|              319fc77 Merge tag 'bpf-fixes' of git: |
|              //git.kernel.org/pub/scm/linux/kernel |
|              /git/bpf/bpf                          |
| Commit Date  2025-02-21                            |
|                                                    |
| Hash         sha256:347605d01e5e38124b829c59efc116 |
|              6bbf97f888429ff65a3cb0d567e3440b61    |
+----------------------------------------------------+

Certificates are deterministic - same username always produces the same hash and certificate number.

README Badge

npx lastgen --badge <username>

Outputs shields.io markdown you can paste into your README:

Verification

Saved certificates can be verified against the live GitHub API:

npx lastgen verify proof.json

Checks include:

| Check | What it does | | ---------------------- | --------------------------------------------------------- | | Hash integrity | Recomputes SHA-256 hash to detect tampering | | Era classification | Confirms era matches the proof date | | Proof date | Re-derives proof date from commit and account data | | Identity | 3-way match: author login, committer login, noreply email | | Repo ownership | Reports whether commit is in a self-owned or third-party repo | | GitHub ID | Matches commit author ID against certificate | | Commit date | Fetches the commit from GitHub and compares dates | | Date consistency | Detects forged author dates via author/committer drift | | Root commit | Notes if commit has no parents (higher trust) | | GPG signature | Notes if commit is cryptographically signed |

License

MIT

[!NOTE] This project was built with assistance from LLMs. Human review and guidance provided throughout.