Loading page
About this tool
Analyses pasted git log output to show how commit emails, timezone offsets and commit hours expose your identity and daily routine.
Code Repository Metadata Explainer reads pasted git log output and reports the identity, location and routine it publishes: the author email attached to every commit, the UTC offset stored alongside each timestamp, the busiest eight-hour window of your day, and the share of commits landing at weekends or between midnight and 06:00. Parsing happens in your browser, and the score is a documented rubric — 30 points for identity, 20 for location, 30 for how concentrated your commit hours are, 20 for off-hours patterns. For developers who publish under their own name and would rather know what the history says about them.
Open Code Repository Metadata Explainer on AltFTool — it loads instantly in your browser.
Paste your code or data sample into the workspace.
Pick the format, conversion, or analysis you need.
Copy the polished result straight back into your project.
Paste real output — it parses both iso-strict and plain git log formats without sending anything anywhere.
Each of the four components has a published maximum and stated thresholds, so you can see how the number was reached.
Points to the noreply commit address and the push protection setting, and is honest that timestamps need a history rewrite.
Each commit records an author name, an author email and an author timestamp with the UTC offset of the machine that made it, plus the same three fields for the committer. All of it is published the moment the repository is pushed public, and it stays in the history after you change your git config.
Set a per-repository noreply address with git config user.email "ID+handle@users.noreply.github.com" and turn on the hosting platform's setting that blocks pushes exposing your real address. Existing commits keep the old address until the history is rewritten.
Yes. Git stores the committer's UTC offset in the timestamp itself, so a consistent +05:30 or -04:00 across a history pins you to one band of longitude, and a change in offset marks a move or a trip.
It replaces them with new commits that have new hashes, but the originals survive in every existing clone, in fork networks and often in the platform's cached views. Rotate any exposed credential first and treat the rewrite as damage limitation, not deletion.