Rust rules for Bazel
View bazelbuild/rules_rust on GitHubThis report is available to share but is not indexed because the scan coverage or repository footprint is below the publication threshold.
Rust rules for Bazel
RepoWorth models the current development value represented by the visible repository evidence. It does not include ideation, intellectual property, business value, product discovery, or sale price.
Modeled range $3,613 to $8,616
47,774 source lines across 557 authored files
The headline RepoWorth and measured source facts are ready. Comparable history, accepted changes, and badge evidence will appear here as enrichment finishes.
Ranked from the public GitHub contributor evidence available at the latest scan. This table describes measured repository activity, not ownership or original authorship.
| Rank | Contributor | Contributions | Share of top group | Latest measured activity |
|---|---|---|---|---|
| #1 |  zertosh@zertosh | 1 | 100.0% | Current GitHub contributor snapshot |
Rust rules for Bazel
These values come from the same immutable repository scan as the headline RepoWorth. They stay tied to the scanned commit so the reading can be inspected against one exact source state.
Established based on deterministic repository structure and complexity signals.
First-party implementation tokens eligible for the modeled code-scale input.
394 detected test files contribute separately from production code.
100 manifests and 0 workspace boundaries were detected.
78 documentation files remain visible as a distinct enablement signal.
1,025 dependency declarations and 3 public-interface signals were measured.
0 large files and 4,003 branch signals add structural context.
26 generated files were identified. Ignored and generated material does not inflate RepoWorth.
Each highlight records a measured characteristic of the same repository scan used for this RepoWorth report.
At least 500 dependency declarations were measured across supported manifests.
Code scale, branching, dependencies, languages, structure, and visible test evidence shape the implementation and verification effort represented by this repository.
Measured from the current source archive.
Derived from branch density, dependencies, languages, and code scale.
Measures visible test code relative to the source corpus.
This view separates authored evidence from the implementation, integration, verification, and engineering oversight represented by the current repository.
Reading boundary: These are modeled development inputs for the visible code. They do not include product discovery, company value, private systems, or commercial outcomes.
CodeValuation.com counted supported authored source on commit 5f04c8c14c2ffacfe10ad14e55298be21454be04, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
Supported first-party source, tests, configuration, manifests, repository structure, dependency signals, and framework boundaries.
Common generated and vendored files, build output, dependencies, lockfiles, minified assets, binaries, media, and private systems outside this repository.
Ideation, intellectual-property rights, security posture, production reliability, company value, sale price, revenue, user value, proprietary data, or the cost of discovering the original product.
This is a modeled current development valuation for the repository's visible code at a specific commit. It reflects code volume, implementation output, complexity, and engineering oversight. It is not a business valuation, investment appraisal, security review, or estimate of sale price, ideation, intellectual property, revenue, users, brand, proprietary data, undocumented domain knowledge, or private infrastructure.
Enter a public GitHub URL to create a current repository reading.