This report is available to share but is not indexed because the scan coverage or repository footprint is below the publication threshold.
CodeValuation.com
RepoWorth
github.com/MukundaKatta
agent-stack-reliability-primitives-paper
Preprint paper package — Six reliability primitives for LLM agents (AgentFit, AgentGuard, AgentSnap, AgentVet, AgentCast, AgentBudget). Artifact pattern for stackable, zero-dependency single-concern libraries.
RepoWorth$83.22Current measured development value · Less than one active build day
Rebuild complexity58.584/100Profile: Complex
7.4K code tokens4 source filesTeX primary language
Authored code7.4K tokens · 753 source lines
Complexity58.584/100 · Complex
Primary stackTeX
Scan coverage43.86% · 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$83.22
Modeled range $54.09 to $128.99
0.1 active build days0.5 engineering hours5.9K implementation tokens
Repository evidenceMeasured at the scanned commit7.4K tokens
753 source lines across 4 authored files
0 test files0 dependencies43.86% 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$83.22
Current measured reading
Measurement basisCurrent readingCurrent published repository scanEvidence coverage44%current scanComplexity59/100Measured from code scale and structural signalsMaintainability68/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.
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 signal68/100
Established based on deterministic repository structure and complexity signals.
Production source7.4K tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence0 tokens
0 detected test files contribute separately from production code.
Configuration and infrastructure0 tokens
0 manifests and 0 workspace boundaries were detected.
Documentation37.4K tokens
18 documentation files remain visible as a distinct enablement signal.
Integration surface15 signals
0 dependency declarations and 0 public-interface signals were measured.
Repository structure1 levels deep
0 large files and 71 branch signals add structural context.
Excluded from authored evidence0 files
0 generated files were identified. Ignored and generated material does not inflate RepoWorth.
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 scaleModerate
Measured from the current source archive.
ComplexityModerate
Derived from branch density, dependencies, languages, and code scale.
VerificationLow
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 evidence5.9KProduction, tests, configuration, and documentation
Estimated implementation output5.9KImplementation, retries, integration, and verification
Engineering oversight0.5 hoursOrientation, integration, tests, and review
Active build time0.1 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit d3b270dbe5a5f2dc229b0de628eedcfcec3e6a36, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
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.