Hindsight
v2026.06 open-sourceThe section your link pointed to isn't on Hindsight's page any more, so we've brought you to the top.
Hindsight is a free tool that parses web artifacts from Google Chrome, Chromium-based browsers, and Mozilla Firefox profiles for forensic analysis.
hindsight.py -i "C:\Users\Investigator\AppData\Roaming\Mozilla\Firefox\Profiles\abc123.default" -b Firefox -o firefox_case hindsight.py -i "C:\Users\Suspect\AppData\Local\Google\Chrome\User Data\Default" -o chrome_case -f XLSX hindsight --input chrome_history.sqlite --output results.jsonl -f jsonl hindsight -i C:\Users\JohnDoe pip install pyhindsight
Summary
Hindsight is a free, open-source dfir tool for parsing browser artifacts from Google Chrome, Chromium-based browsers (Edge, Brave, Vivaldi, Tor Browser), and Mozilla Firefox, pulling history, downloads, cache, bookmarks, autofill, saved passwords, cookies, extensions, and local storage into a single correlated timeline. It runs as a command-line tool (hindsight.py or a packaged .exe) or through a bundled local web UI, and installs via pip. It is built for forensic examiners and incident responders reconstructing user activity from a disk image or live profile rather than for continuous monitoring. Output goes to XLSX, JSONLJSONLA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory., or SQLite for further review in a spreadsheet or case-management workflow, which places it in the category of browser-artifact parsers used alongside broader dfir toolkits. Its history goes back to 2014, and with 20 contributors, over a hundred commits and eight releases in the past year, and a release only 44 days old, it is actively maintained.
Hindsight is a free tool that parses web artifacts from Google Chrome, Chromium-based browsers, and Mozilla Firefox profiles for forensic analysis.
How Hindsight helps
What did a user actually do on this machine, in what order?
pulls history, downloads, cache, bookmarks, autofill, passwords, cookies, and local storage out of a Chrome or Firefox profile and correlates them into a single timeline, so browsing, downloading, and form activity line up against each other by time
Which browser extensions were installed, and what could they access?
reads extension records alongside manifest and permission details, listing installed extensions with the permissions and content scripts each one held
What did the user delete that might still be recoverable?
recovers bookmarks from daily backup snapshots and reconstructs download and browsing entries from cache and session data even when the live history no longer shows them
Was this a Chrome-family browser or Firefox, and does that change what gets pulled?
auto-detects the browser type from the profile structure and parses the matching set of databases for that browser, whether that's the Chromium history and cookie files or Firefox's places, cookies, and form history stores
What third-party tracking or cross-site state did a site leave behind in the browser?
parses Chrome's DIPS database and the cookie store's extra fields to surface third-party cookie interactions and popup-related tracking activity tied to specific sites
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Hindsight, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Hindsight puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
13 entries
No entries match these filters.
- July 20261
- May 20261
- January 20261
- March 20251
- November 20241
- March 20231
- December 20211
- April 20211
- January 20211
- August 20191
- March 20191
- March 20171
- November 20151
Project health
Issue, contributor and maintainer activity in obsidianforensics/hindsight, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 ±0 vs prior 12 months
- Maintainers 2 +2 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 2
- Commits / month 39
- Stars 1,506
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.