Sprted

D 50 completed
Other
unknown / zig · small
51
Files
11,695
LOC
0
Frameworks
3
Languages

Pipeline State

completed
Run ID
#1475650
Phase
done
Progress
0%
Started
2026-04-16 11:02:07
Finished
2026-04-16 11:02:07
LLM tokens
0

Pipeline Metadata

Stage
Skipped
Decision
skip_scaffold_dup
Novelty
35.00
Framework unique
Isolation
Last stage change
2026-04-16 18:15:42
Deduplication group #49193
Member of a group with 43 similar repo(s) — canonical #1591863 view group →
Want this analysis on your repo? https://repobility.com/scan/

AI Prompt

Create a simple sprite editor using Zig and raylib. The editor should be functional enough to build sprites and include an MCP bridge component (`sprted-mcp`) that communicates with an in-process API server. The setup should guide the user on running the editor via `zig build run` and building binaries with `zig build`. It should also document the necessary environment variables like `SPRTED_API_INFO_PATH` for configuring the API connection details.
zig raylib sprite-editor game-dev graphics mcp api
Generated by gemma4:latest

Catalog Information

Create a simple sprite editor using Zig and raylib. The editor should be functional enough to build sprites and include an MCP bridge component (sprted-mcp) that communicates with an in-process API server. The setup should guide the user on running the editor via zig build run and building binaries with zig build. It should also document the necessary environment variables like SPRTED_API_INFO_PATH for configuring the API connection details.

Tags

zig raylib sprite-editor game-dev graphics mcp api

Quality Score

D
50.5/100
Structure
41
Code Quality
54
Documentation
48
Testing
0
Practices
78
Security
100
Dependencies
50

Strengths

  • Consistent naming conventions (snake_case)
  • Good security practices — no major issues detected

Weaknesses

  • No LICENSE file — legal ambiguity for contributors
  • No tests found — high risk of regressions
  • No CI/CD configuration — manual testing and deployment
  • 1240 duplicate lines detected — consider DRY refactoring
  • 6 'god files' with >500 LOC need decomposition

Recommendations

  • Add a test suite — start with critical path integration tests
  • 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)

Languages

zig
98.1%
text
1.1%
markdown
0.8%

Frameworks

None detected

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/1175091.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV