📅Code Age Visualizer🔒 100% local

Reads the last-modified timestamp of every source file you select and sorts them oldest first, colour-banding each one as recent (under 7 days), this month (7 to 30 days), older (30 to 365 days) or stale (over a year). The table shows the file name, the modification date, the days since and the band, with counts per band above it. Reading happens from the File objects the picker hands over, so nothing is uploaded and file contents are never parsed.

How to use it

1. Open the file picker and select the source files to check - more than one is allowed.
2. Press Analyze.
3. Read the band counts in the header, then the table, which is ordered longest-untouched first.

Worked example

When to use it

• Deciding which modules to read first when you pick up an unfamiliar repository.
• Building the case for archiving or deleting a directory nobody has edited in a year.
• Spotting the file that should be under constant change - a migration, a pricing table - but has not moved since a refactor.

What it does not do

• A timestamp says when a file was written, not whether it matters: a lockfile is "recent" after every install, a correct and finished module is "stale".
• A fresh git clone resets timestamps, so run it on the working copy you have been using, not a new checkout.
• Age alone is not a deletion argument - know what depends on the file first.
• The picker only offers the source extensions the page accepts, and no contents are read, so it cannot tell an empty stub from a 2000-line module.