Current repository readingScanned Jul 24, 2026, 2:08 PM UTC

augurs Codebase Valuation

Time series analysis for Rust, with bindings to Python and Javascript

View grafana/augurs on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/grafana

augurs

Time series analysis for Rust, with bindings to Python and Javascript

RepoWorth$5,831Current measured development value · 3.4 active build days
Rebuild complexity94.267/100Profile: Complex
406.9K code tokens137 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/augurs
Authored code406.9K tokens · 51,098 source lines
Complexity94.267/100 · Complex
Primary stackRust
Scan coverage96.64% · Content scan
RepoWorth development valuation

One valuation, with the evidence behind it.

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.

RepoWorthCurrent measured development value
$5,831

Modeled range $4,665 to $6,997

3.4 active build days26.9 engineering hours336K implementation tokens
Repository evidenceMeasured at the scanned commit
406.9K tokens

51,098 source lines across 137 authored files

19 test files901 dependencies96.64% scan coverage
Measured RepoWorth history

The current RepoWorth starts the measured history.

This current scan is the first measured point. Later scans add comparable history when the repository changes. RepoWorth is not back-cast onto commits that were never scanned.

Recorded RepoWorth$5,831
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage97%current scan
Complexity94/100Measured from code scale and structural signals
Maintainability61/100Current structure, tests, and generated-code balance

This current scan establishes the RepoWorth baseline. Comparable value changes appear only after another completed scan under the same measurement basis.

RepoWorth history compares completed repository scans only when their measurement basis is compatible. Commit activity is shown separately so delivery volume is not presented as code value.

Repository contributors

Top contributors.

Ranked from the public GitHub contributor evidence available at the latest scan. This table describes measured repository activity, not ownership or original authorship.

RankContributorContributionsShare of top groupLatest measured activity
#1Ben Sully@sd2k5079.4%Current GitHub contributor snapshot
#2yoziru@yoziru57.9%Current GitHub contributor snapshot
#33shv@3shv34.8%Current GitHub contributor snapshot
#4kolesnikovae@kolesnikovae11.6%Current GitHub contributor snapshot
#5csmarchbanks@csmarchbanks11.6%Current GitHub contributor snapshot
#6shenxiangzhuang@shenxiangzhuang11.6%Current GitHub contributor snapshot
#7edwardcqian@edwardcqian11.6%Current GitHub contributor snapshot
#8glitched-w0rld@glitched-w0rld11.6%Current GitHub contributor snapshot
About augurs

What the public repository appears to contain.

Time series analysis for Rust, with bindings to Python and Javascript

hacktoberfestrusttime-seriestime-series-analysis
License
Apache-2.0
Default branch
main
GitHub stars
575
Forks
26
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile1.9MB authored source
Rust70.81%
JavaScript17.7%
TypeScript7.44%
Python2.97%
HTML0.87%
C/C++0.11%
C++0.1%
Source files137
Test files19
Manifests30
Dependencies901
Measured technical evidence

A fuller view of what the scanner found.

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.

Maintainability signal61/100

Established based on deterministic repository structure and complexity signals.

Production source322.4K tokens

First-party implementation tokens eligible for the modeled code-scale input.

Test evidence84.6K tokens

19 detected test files contribute separately from production code.

Configuration and infrastructure6.8K tokens

30 manifests and 0 workspace boundaries were detected.

Documentation28K tokens

54 documentation files remain visible as a distinct enablement signal.

Integration surface166 signals

901 dependency declarations and 3 public-interface signals were measured.

Repository structure6 levels deep

0 large files and 2,249 branch signals add structural context.

Excluded from authored evidence0 files

124 generated files were identified. Ignored and generated material does not inflate RepoWorth.

Measured repository distinctions

Repository evidence highlights.

Each highlight records a measured characteristic of the same repository scan used for this RepoWorth report.

quality

Verification depth

At least 20 percent of measured source tokens are in test paths.

architecture

Dependency ecosystem

At least 500 dependency declarations were measured across supported manifests.

Technical effort profile

What makes this repository harder to rebuild.

Code scale, branching, dependencies, languages, structure, and visible test evidence shape the implementation and verification effort represented by this repository.

Code scaleHigh

Measured from the current source archive.

ComplexityHigh

Derived from branch density, dependencies, languages, and code scale.

VerificationHigh

Measures visible test code relative to the source corpus.

Development effort composition

Source volume alone does not explain the work.

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.

Weighted authored evidence336KProduction, tests, configuration, and documentation
Estimated implementation output336KImplementation, retries, integration, and verification
Engineering oversight26.9 hoursOrientation, integration, tests, and review
Active build time3.4 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

CodeValuation.com counted supported authored source on commit 6049507a27d8b7119d75ab3a82233e40bdc5713a, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.

Included

Supported first-party source, tests, configuration, manifests, repository structure, dependency signals, and framework boundaries.

Excluded

Common generated and vendored files, build output, dependencies, lockfiles, minified assets, binaries, media, and private systems outside this repository.

Not claimed

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.

Check another repository

Run RepoWorth on your own codebase.

Enter a public GitHub URL to create a current repository reading.

No sign-up for public repositories. Private repositories require a free trial. Evaluated in real time directly from GitHub. Code is never stored. Derived measurements and valuation history are saved.