You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gh-aw codebase shows a quality signal of 5228/10000 as of today's scan — sitting in the "moderate" range. The codebase scanned 4,463 files across 187 directories, with 4,413 import edges and 2,686 call edges. No god files or hotspots were detected, and cycles remain low at just 2. The primary concern is function complexity, with 834 functions flagged as complex.
No architectural rules file (.sentrux/rules.toml) is configured, so no rule violations were detected — though adding rules would enable stricter quality gates.
Quality Signal
Metric
Today
Yesterday
7d Trend
Overall
5228
—
➡️ (first run)
Coupling Score
0.038
—
➡️
Cycles
2
—
➡️
God Files
0
—
✅
Hotspots
0
—
✅
Dist. from Main Sequence
0.34
—
➡️
Bottleneck
Current primary bottleneck: Function Complexity — 834 functions exceed complexity thresholds. High function complexity makes code harder to reason about, test, and maintain. The recommended approach is to decompose large functions into smaller, focused units.
Rules
✅ No rules configured — no violations detected.
⚠️ Consider adding a .sentrux/rules.toml to enforce architectural constraints (e.g., max coupling, zero cycles, module boundaries).
Quality Trend (30 days)
This is the first recorded data point for this repository. Future runs will show trend data here.
Reduce function complexity: 834 complex functions is the primary drag on quality. Refactor large functions (particularly in pkg/workflow/ and pkg/cli/) into smaller, single-responsibility units.
Address the 2 import cycles: While low, cycles indicate tight coupling. Running sentrux check . with a rules file can pinpoint the exact files involved and help break the circular dependencies.
Add .sentrux/rules.toml: Define architectural rules (max coupling score, zero cycles, module layer boundaries) to enforce quality gates automatically in CI and future daily reports.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The gh-aw codebase shows a quality signal of 5228/10000 as of today's scan — sitting in the "moderate" range. The codebase scanned 4,463 files across 187 directories, with 4,413 import edges and 2,686 call edges. No god files or hotspots were detected, and cycles remain low at just 2. The primary concern is function complexity, with 834 functions flagged as complex.
No architectural rules file (
.sentrux/rules.toml) is configured, so no rule violations were detected — though adding rules would enable stricter quality gates.Quality Signal
Bottleneck
Current primary bottleneck: Function Complexity — 834 functions exceed complexity thresholds. High function complexity makes code harder to reason about, test, and maintain. The recommended approach is to decompose large functions into smaller, focused units.
Rules
✅ No rules configured — no violations detected.
Quality Trend (30 days)
This is the first recorded data point for this repository. Future runs will show trend data here.
Recommendations
pkg/workflow/andpkg/cli/) into smaller, single-responsibility units.sentrux check .with a rules file can pinpoint the exact files involved and help break the circular dependencies..sentrux/rules.toml: Define architectural rules (max coupling score, zero cycles, module layer boundaries) to enforce quality gates automatically in CI and future daily reports.References: §25529082544
Beta Was this translation helpful? Give feedback.
All reactions