Bracket Tools
C+ 74 completed
Other
monorepo / graphql · small
91
Files
10,258
LOC
0
Frameworks
5
Languages
Pipeline State
completedRun ID
#726269Phase
doneProgress
0%Started
2026-04-15 00:58:27Finished
2026-04-15 00:58:27LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
70.40Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:31Deduplication group #55909
Member of a group with 1 similar repo(s) — this repo is canonical view group →
Repobility — the code-quality scanner for AI-generated software · https://repobility.com
AI Prompt
Create a Rust monorepo for esports tournament tooling, specifically designed to interact with start.gg. I need the structure to include crates for core data types, a generic sled-based caching layer, and an abstract query interface. Please also include a main SDK crate that handles caching and rate-limited client interactions with the start.gg GraphQL schema. Additionally, build out tools for reporting, such as a `ratatui` TUI for live set reporting and a background scraper daemon.
rust graphql monorepo esports cli graphql-client caching tui
Generated by gemma4:latest
Catalog Information
Create a Rust monorepo for esports tournament tooling, specifically designed to interact with start.gg. I need the structure to include crates for core data types, a generic sled-based caching layer, and an abstract query interface. Please also include a main SDK crate that handles caching and rate-limited client interactions with the start.gg GraphQL schema. Additionally, build out tools for reporting, such as a ratatui TUI for live set reporting and a background scraper daemon.
Tags
rust graphql monorepo esports cli graphql-client caching tui
Quality Score
C+
73.8/100
Structure
62
Code Quality
100
Documentation
67
Testing
60
Practices
70
Security
70
Dependencies
80
Strengths
- Good test coverage (33% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Low average code complexity — well-structured code
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No CI/CD configuration — manual testing and deployment
- Potential hardcoded secrets in 3 files
- 243 duplicate lines detected — consider DRY refactoring
- 1 'god files' with >500 LOC need decomposition
Recommendations
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
- Move hardcoded secrets to environment variables or a secrets manager
Languages
Frameworks
None detected
Symbols
function133
struct110
extension41
type_alias36
enum17
trait8
constant4
Embed Badge
Add to your README:
