tessriOverview
Captured 2026-11-15fbb6833c

tessri

2026-11-15 17:38:10 UTC · commit fbb6833, 77 commits

17,994
lines of code in 132 files (Python 16,922)

Code by status

  • Active 17,994 lines (100%) touched in the last 90 days
Unreachable code
0.0%
0 orphan files, 0 lines
Changed in 90 days
100%
17,994 lines are active
People
1 of 1
committed in the last 180 days; bus factor 1
No active owner
0.0%
0 files, 0 lines
Changed in 30 days
26,714
lines (new against the 30 days before) in 43 commits
Module cycles
1
2 of 4 modules are in one
Reachability coverage
91.7%
of production code could be analysed

Where to look first

Each list is the top of a longer table further down. Treat them as questions to check, not verdicts.

Probably unused

No orphan files: everything analysed is reached from an entry point or a test.

All 0 candidates

Nobody active maintains

Every live file has someone active maintaining it.

Ownership

Dependencies to untangle

  • tessri → tessri/analyzers3 imports; cut to break cycle 1

Module graph

Changing fastest

  • tessri11,528 lines (new), 0.0% by outsiders, 31 commits
  • tests8,936 lines (new), 0.0% by outsiders, 39 commits
  • tools2,636 lines (new), 0.0% by outsiders, 21 commits
  • site1,996 lines (new), 0.0% by outsiders, 16 commits

Review load

Directories

Where the code is, how much of it is alive, and who maintains it. Click a heading to sort.

DirectoryCodeStatus mix (orphan share sorts)OwnersState
tessri8,500Tianyi Zhang 100%owned
tests6,532Tianyi Zhang 100%owned
tools1,890Tianyi Zhang 100%owned
site1,072Tianyi Zhang 100%owned

How the modules fit together

4 modules, 4 dependencies, 1 cycles, from 164 imports. An arrow A → B means a file in A imports a file in B. Users sit on the left, what they build on to the right. Red arrows are the cuts that break a cycle.

dependency (thicker = more imports)cut to break a cycleno active ownerbar under a name: code by status
tools → tessri: 17 imports from 4 filestessri/analyzers → tessri: 4 imports from 3 filestessri → tessri/analyzers: 3 imports from 3 files (cut to break cycle 1)tools → tessri/analyzers: 2 imports from 2 filestools: 6 files, 1,890 lines; uses 2 modules, used by 0tools6 files, 1,890 linestessri/analyzers: 5 files, 1,124 lines; uses 1 modules, used by 2; in cycle 1analyzerstessritessri: 32 files, 7,376 lines; uses 1 modules, used by 2; in cycle 1tessri32 files, 7,376 lines

Cycle 1: 2 modules

tessri, tessri/analyzers. 7 imports among them. Removing or inverting these 1 dependencies (3 imports) leaves no cycle; it is a heuristic for a few, light edges, not a proof of the minimum.

FromToImportsFor example
tessritessri/analyzers3tessri/analyze.py → tessri/analyzers/__init__.py

All modules

ModuleFilesCodeUsesUsed byCycleOwnersState
tessri327,376121Tianyi Zhang 100%owned
tessri/analyzers51,124121Tianyi Zhang 100%owned
tools61,89020-Tianyi Zhang 100%owned
site111600-Tianyi Zhang 100%owned

What does a change reach?

Choose a file or folder to see related code and candidate tests.

Who maintains it

Read from git: every commit credits its author with the files it touched, and a commit loses half its weight per year, so an owner is whoever has been maintaining a file lately. It shows who changed the code, not who is accountable, and it cannot see who reviewed. 1 authors, 1 committed in the last 180 days; the fewest people who together hold half the code: 1.

Who holds the code

PersonCode heldShareLast commitSilent forState
Tianyi Zhang17,994100.0%2026-11-150d agoactive

Live code nobody active maintains

0 lines (0.0%) in 0 files. Someone needs to be assigned before it is changed.

None: every live file has an active maintainer.

Review load

The last 30 days (2026-10-16 to 2026-11-15) against the 30 before. Git records who changed code, not who reviewed it, so this is how much review the changes ask for, not how much happened.

  • 26,714 lines changed in code files (new against 0 before), in 43 commits across 6 areas by 1 person.
  • 8,681 lines of configuration and docs are not counted.

Where the changes landed

Areas are directories, split by size. Click a heading to sort.

  • By an owner the author is among the people who maintain the area
  • By someone else an owner should see it
  • Bots and ignored authors
AreaChanged linesAgainst beforeCommitsPeopleBy othersWho changed itOwnersState
tessri11,528
new3110.0%Tianyi Zhang 100%Tianyi Zhang 100%owned
tests8,936
new3910.0%Tianyi Zhang 100%Tianyi Zhang 100%owned
tools2,636
new2110.0%Tianyi Zhang 100%Tianyi Zhang 100%owned
site1,996
new1610.0%Tianyi Zhang 100%Tianyi Zhang 100%owned
tessri/analyzers1,562
new910.0%Tianyi Zhang 100%Tianyi Zhang 100%owned
repolife56
new41-Tianyi Zhang 100%-no history

Largest changes

The hardest to review: one commit, many lines.

CommitDateAuthorLinesFilesMostly inSubject
7b755652026-10-29Tianyi Zhang3,24724tessriInitial commit: repolife, a repository liveness report for coding agents
f8d42192026-11-01Tianyi Zhang2,26616tessriAdd structured why, meta block, reversible integration and SARIF output
fa3f0252026-10-30Tianyi Zhang1,74412tessriAdd triage and check: what to look at first, and what a change did to the structure
62f5ad02026-10-30Tianyi Zhang1,4548tessriAdd a single-file HTML report
532b71d2026-10-29Tianyi Zhang1,21010tessriAdd module dependency graph and change-impact analysis
922381d2026-11-06Tianyi Zhang1,09721tessriPrepare 0.3.0: the old name goes, `--since` defaults to the default branch, `--repo` everywhere, `in
c72f7722026-11-04Tianyi Zhang1,0974siteAdd the site: a landing page and the guide, built with nothing installed
3eb4f0c2026-11-01Tianyi Zhang97612tessriImprove impact evidence and the offline report workspace
b9428632026-11-15Tianyi Zhang96216testsOne pass over each tree, and a cache of what the analyzers read: a warm scan in a quarter of the tim
88a1b942026-11-05Tianyi Zhang9349tessriServe the questions as MCP tools and point each agent at the server
78fdaf02026-10-29Tianyi Zhang92012tessriAdd ownership: who maintains each part of the repository
8a6de452026-10-30Tianyi Zhang87311tessriAdd review load: how much code changed lately, where, and who can look
94a41752026-11-12Tianyi Zhang7855siteThe site's design assets: self-hosted type, Lucide icons, cards, highlighted code with copy buttons,
c0283612026-11-09Tianyi Zhang7768tessriHooks for Claude Code and Codex: `tessri hook`, installed by `integration install --agent claude-hoo
58e2a0a2026-11-10Tianyi Zhang6695toolsThe backtest behind the triage order and the one-import review set, published: `tools/backtest.py`

Where the change is

The files changed most often in the last year: where review effort goes, and where a small mistake is most likely to be touched again.

FileCommits in a yearAuthorsCodeLast commitStatusOwner
tessri/cli.py2012772026-11-15ActiveTianyi Zhang
tessri/templates.py1912742026-11-15ActiveTianyi Zhang
tools/build_site.py1619322026-11-15ActiveTianyi Zhang
site/index.html1611562026-11-15ActiveTianyi Zhang
site/tessri.css1018002026-11-15ActiveTianyi Zhang
tessri/report.py1012102026-11-11ActiveTianyi Zhang
tessri/since.py914272026-11-11ActiveTianyi Zhang
tessri/modules.py814022026-11-12ActiveTianyi Zhang
tessri/gitlog.py813192026-11-04ActiveTianyi Zhang
tessri/triage.py812992026-11-12ActiveTianyi Zhang
tessri/analyze.py812042026-11-15ActiveTianyi Zhang
tessri/config.py81622026-11-15ActiveTianyi Zhang
tessri/analyzers/__init__.py81492026-11-15ActiveTianyi Zhang
tessri/integration.py717442026-11-09ActiveTianyi Zhang
tests/test_integration.py717362026-11-09ActiveTianyi Zhang

Cleanup candidates

No orphan files and nothing reachable only from tests.

Read this with care

  • Reachability is static. Dynamic dispatch, plugin discovery and consumers outside this repository are invisible: treat ORPHAN as a candidate, and run `tessri why <file>` before deleting anything.
  • If this repository is a library, public modules that nothing inside it imports look orphaned. List them under `keep` in .tessri.toml.
  • Ownership is inferred from git commit authors (recent commits weigh more; `.mailmap` merges identities). It shows who has been changing the code, not who is accountable, and an owner counts as gone after 180 days without a commit anywhere in the repository.
  • No reachability analyzer for: CSS, HTML. Those files only get volume and activity.
Snapshot and settings
Code snapshot
Files read at generation time; Git HEAD is a history reference, not a clean-worktree assertion
Captured
2026-11-15T17:38:10Z
Repository
/home/runner/work/tessri/tessri
History HEAD
fbb6833c5c7e97f41172831d0927bba57e7120b6
History reference
fbb6833c5c7e97f41172831d0927bba57e7120b6
Analyzers
javascript, python
Active window
90 days
Dormant after
365 days
Owner gone after
180 days without a commit
Review window
30 days
Volume and activity only
CSS (1), HTML (1)
Go to a file or view