repowiserepowise
Sign in
onyks-os/transparenttorproxy
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseonyks-os/transparenttorproxy
TR
TR

onyks-os / transparenttorproxy

pythonmaincf7350514.0K linessynced 10h ago

Code health

7.5out of 10Good

This codebase scores 7.5 out of 10 on defect risk, which we rate good. It also scores maintainability 8.6 and static performance risk 9.9 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 17 of 136 files are git hotspots, and they average 5.8.

Full health report →
Documentation108pages0 with model-written prose, 108 built from the indexDead code6exportsUnused exports that nothing in the graph reaches
Lines of code
14.0K
Files
136
Symbols
588
Modules
7
Languages
7

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • SPDX-License-Identifier: MITactive · 10h ago
  • systemd-resolved DNS Bypassactive · 10h ago
  • Bring Your Own Daemon (BYOD) Architectureactive · 10h ago
  • Ruleset Testing with Network Sandbox Engine (NSE)active · 10h ago
  • Subprocess Network Orchestrationactive · 10h ago
  • Tor Bridge and Pluggable Transports Supportactive · 10h ago

Needs attention

43 open
  • medium severity. ProposedCreate maintainership guidelinesAuto-proposed decision awaiting review
  • medium severity. ProposedDocument dependency management policyAuto-proposed decision awaiting review
  • medium severity. ProposedUse Sigstore signing with GitHub OIDCAuto-proposed decision awaiting review
  • medium severity. ProposedAdd GitHub Actions workflow for automated releaseAuto-proposed decision awaiting review
  • medium severity. ProposedWatchdog finite state machine using transitions libraryAuto-proposed decision awaiting review

Where the risk concentrates

All 17 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
cli.pyttp98.7th02bus factor 19
tor_install.pyttp97.3th02bus factor 112
start.pyttp/commands96.0th01bus factor 14
test_tor_install.pytests94.7th02bus factor 112
test_watchdog.pytests93.3th02bus factor 110

Composition

Open the graph →
python 46%markdown 38%shell 8%yaml 5%makefile 1%Other 1%

Explore this codebase

  • Docs108 pages across 7 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files136 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 4 entry points→
  • Code healthPer-file scores, 489 open findings, coverage and refactoring targets→
  • Knowledge graphEntities, communities, and the paths between them→
  • Change couplingFiles that keep changing together, mined from commit history→
  • CommitsChange-risk ranked history with agent provenance→
  • ContributorsBus factor, per-file maintainers, and the human/agent split→
  • StatsSize class, origin, lifetime churn, rhythm and records→
  • CostsWhat indexing this snapshot cost, by model and by run→