Valveprotos Rs
C 63 completed
Other
unknown / protobuf · tiny
32
Files
7,039
LOC
0
Frameworks
6
Languages
Pipeline State
completedRun ID
#1541796Phase
doneProgress
0%Started
2026-04-16 21:00:39Finished
2026-04-16 21:00:39LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
45.51Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:36Deduplication group #52634
Member of a group with 19 similar repo(s) — canonical #1520622 view group →
All rows scored by the Repobility analyzer (https://repobility.com)
🧪 Code Distillation
Browse all specs →AI Prompt
Create a Rust library that manages a subset of Valve/Steam related protobuf definitions. I need the project structure to handle multiple proto definitions, including a mechanism to fetch the latest protos from SteamDatabase's Protobufs repository. Additionally, include scripts to build a dependency graph of imports between the protos and a way to enable/disable specific feature sets like 'deadlock' or 'gcsdk' using feature flags. The project should use Rust for implementation.
rust protobuf proto steam library build-system command-line
Generated by gemma4:latest
Catalog Information
Create a Rust library that manages a subset of Valve/Steam related protobuf definitions. I need the project structure to handle multiple proto definitions, including a mechanism to fetch the latest protos from SteamDatabase's Protobufs repository. Additionally, include scripts to build a dependency graph of imports between the protos and a way to enable/disable specific feature sets like 'deadlock' or 'gcsdk' using feature flags. The project should use Rust for implementation.
Tags
rust protobuf proto steam library build-system command-line
Quality Score
C
63.1/100
Structure
48
Code Quality
85
Documentation
55
Testing
15
Practices
78
Security
100
Dependencies
80
Strengths
- CI/CD pipeline configured (github_actions)
- Good security practices — no major issues detected
- Properly licensed project
Weaknesses
- No tests found — high risk of regressions
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
Languages
Frameworks
None detected
Symbols
function9
constant2
type_alias1
Embed Badge
Add to your README:
