Replay
Travel through repository states that actually existed.
RepoRewind 0.2Local Git archaeology
See how your codebase became itself.
Replay real repository history, follow the commits behind a rebuild, compare two eras, and present the evidence. Your source stays on your machine.
- Read-onlyNo Git mutation
- Local-firstNo source upload
- Evidence-linkedCommits and paths
Current erav3.0.0
Commit19 / 25
Tracetimeline/core.ts
Selected evidence
Move timeline engine into the streaming core
9e31c2a · 6 paths changed
v1.0
v2.0
rebuild
v3.0
Use your repository
One command. Nothing uploaded.
Requires Git and Node.js 24, or Node.js 22.13+. The first run downloads RepoRewind from npm.
cd /path/to/your/repository
npx reporewind .Investigate
Search commits, paths, people, releases, and branch tips.
Compare
Pin two eras and follow rename-aware structural change.
Present
Export a reviewed story with privacy choices and checksums.
The guided rebuild
Follow one trace through three releases.
A deterministic 25-commit repository gives you one clear question: what changed when the timeline system was rebuilt?
Open the interactive case-
01
Pin v2.0.0
Preserve the city before the structural change.
-
02
Find the rebuild
Search the commit and jump to its path evidence.
-
03
Travel to v3.0.0
Watch the old import layer become visible ruins.
-
04
Compare the eras
Inspect construction, deletion, and the rename chain.
Small trust boundary
Your history stays yours.
RepoRewind reads Git metadata and numeric diffs—not source contents—and sends no repository data.
- Analyzer reads
- Git metadata + numeric diffs
- Viewer binds
- 127.0.0.1 + private session
- Application sends
- Nothing
- Public export
- Review first, then save
Your repository already has the story.