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

levitate Codebase Valuation

A tool for helping to understand APIs exported and consumed by NPM packages (or any TypeScript code).

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

levitate

A tool for helping to understand APIs exported and consumed by NPM packages (or any TypeScript code).

RepoWorth$3,217Current measured development value · 2.1 active build days
Rebuild complexity72.499/100Profile: Complex
277.1K code tokens75 source filesTypeScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/levitate
Authored code277.1K tokens · 20,299 source lines
Complexity72.499/100 · Complex
Primary stackTypeScript
Scan coverage100% · 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
$3,217

Modeled range $2,574 to $3,861

2.1 active build days16.7 engineering hours208.6K implementation tokens
Repository evidenceMeasured at the scanned commit
277.1K tokens

20,299 source lines across 75 authored files

42 test files28 dependencies100% 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$3,217
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity72/100Measured from code scale and structural signals
Maintainability80/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
#1Esteban Beltran@academo5533.3%Current GitHub contributor snapshot
#2Levente Balogh@leventebalogh5231.5%Current GitHub contributor snapshot
#3Marcus Andersson@mckn169.7%Current GitHub contributor snapshot
#4Hugo Häggmark@hugohaggmark137.9%Current GitHub contributor snapshot
#5Timur Olzhabayev@tolzhabayev116.7%Current GitHub contributor snapshot
#6Jack Westbrook@jackw63.6%Current GitHub contributor snapshot
#7Grot (@grafanabot)@grafanabot63.6%Current GitHub contributor snapshot
#8Hugo Kiyodi Oshiro@oshirohugo42.4%Current GitHub contributor snapshot
#9Kristian Bremberg@KristianGrafana10.6%Current GitHub contributor snapshot
#10Tobias Skarhed@tskarhed10.6%Current GitHub contributor snapshot
About levitate

What the public repository appears to contain.

A tool for helping to understand APIs exported and consumed by NPM packages (or any TypeScript code).

keepteam-frontend-platform
License
Apache-2.0
Default branch
main
GitHub stars
31
Forks
2
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile1.2MB authored source
TypeScript99.99%
JavaScript0.01%
Source files75
Test files42
Manifests1
Dependencies28
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 signal80/100

Strong based on deterministic repository structure and complexity signals.

Production source20.4K tokens

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

Test evidence256.7K tokens

42 detected test files contribute separately from production code.

Configuration and infrastructure1.2K tokens

1 manifests and 0 workspace boundaries were detected.

Documentation4.9K tokens

5 documentation files remain visible as a distinct enablement signal.

Integration surface625 signals

28 dependency declarations and 280 public-interface signals were measured.

Repository structure4 levels deep

0 large files and 7,217 branch signals add structural context.

Excluded from authored evidence0 files

0 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.

quality

Test fortress

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

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.

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 evidence208.6KProduction, tests, configuration, and documentation
Estimated implementation output208.6KImplementation, retries, integration, and verification
Engineering oversight16.7 hoursOrientation, integration, tests, and review
Active build time2.1 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

CodeValuation.com counted supported authored source on commit 8ef9cfb7bfcf34cddc6817f21e66879a5297e505, 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.