[daily-sentrux] Daily Sentrux Report - 2026-05-17

[github-actions[bot]]

The daily Sentrux structural quality scan of github/gh-aw completed successfully on 2026-05-17. The overall quality signal is 5226/10000, placing the codebase in a moderate health range. This is the first recorded baseline entry, so no trend comparison is available yet. The primary concern is the high number of complex functions (877), which represents the main bottleneck. Two dependency cycles and one god-file were also detected.

No architectural rules file (.sentrux/rules.toml) is configured, so rule-based enforcement is not yet active.

Quality Signal

Metric	Today	Yesterday	7d Trend
Overall	5226	—	➡️ (first run)
Coupling Score	0.197	—	➡️
Cycle Count	2	—	➡️
God Files	1	—	➡️
Complex Functions	877	—	➡️
Max Depth	8	—	➡️

⚠️ Overall signal (5226) is in the moderate range (5000–8000). No metrics have crossed the critical threshold below 5000.

Bottleneck

Current primary bottleneck: Complexity (877 complex functions) — A high count of complex functions increases cognitive load, makes testing harder, and raises the risk of defects. Breaking large functions into smaller, well-named units will improve this metric and overall maintainability.

Rules

i️ No .sentrux/rules.toml found — architectural rule enforcement is not yet configured. Consider adding rules to enforce package layering, forbidden dependencies, or module boundaries.

Quality Trend (30 days)

This is the first recorded entry in the quality history. Future runs will populate trend data here.

Current baseline (2026-05-17):

• Quality Signal: 5226/10000
• Files analyzed: 4,649 (of 4,700 total; 51 dropped)
• Dependency cycles: 2
• God files: 1
• Complex functions: 877
• Coupling score: 0.197
• Max dependency depth: 8

Recommendations

1. Reduce complex functions: 877 complex functions is the primary bottleneck. Target the highest-complexity files in pkg/workflow/ and pkg/cli/ for refactoring into smaller, focused functions.
2. Resolve dependency cycles: 2 cycles exist in the import graph. Run sentrux scan . in the GUI to identify which packages are involved and break the cycles by extracting shared interfaces or types.
3. Add architectural rules: Create .sentrux/rules.toml to enforce module boundaries (e.g., pkg/cli should not import pkg/workflow internals directly) and prevent future regressions.

References:

• §25976570246

Generated by 📊 Daily Sentrux Report · ● 5.2M · ◷

• expires on May 20, 2026, 12:15 AM UTC