Current repository readingScanned Jul 24, 2026, 3:05 PM UTC
faro-web-sdk Codebase Valuation
The Grafana Faro Web SDK, part of the Grafana Faro project, is a highly configurable web SDK for real user monitoring (RUM) that instruments browser frontend applications to capture observability signals. Frontend telemetry can then be correlated with backend and infrastructure data for full-stack observability.
The Grafana Faro Web SDK, part of the Grafana Faro project, is a highly configurable web SDK for real user monitoring (RUM) that instruments browser frontend applications to capture observability signals. Frontend telemetry can then be correlated with backend and infrastructure data for full-stack observability.
RepoWorth$2,602Current measured development value · 1.7 active build days
Rebuild complexity76.081/100Profile: Complex
195K code tokens350 source filesTypeScript primary language
Authored code195K tokens · 27,487 source lines
Complexity76.081/100 · Complex
Primary stackTypeScript
Scan coverage98.3% · 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$2,602
Modeled range $2,081 to $3,122
1.7 active build days13.2 engineering hours165.3K implementation tokens
Repository evidenceMeasured at the scanned commit195K tokens
27,487 source lines across 350 authored files
91 test files91 dependencies98.3% 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$2,602
Current measured reading
Measurement basisCurrent readingCurrent published repository scanEvidence coverage98%current scanComplexity76/100Measured from code scale and structural signalsMaintainability78/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.
The Grafana Faro Web SDK, part of the Grafana Faro project, is a highly configurable web SDK for real user monitoring (RUM) that instruments browser frontend applications to capture observability signals. Frontend telemetry can then be correlated with backend and infrastructure data for full-stack observability.
License
Apache-2.0
Default branch
main
GitHub stars
1,107
Forks
123
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile843.9KB authored source
TypeScript99.27%
JavaScript0.68%
HTML0.05%
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 signal78/100
Strong based on deterministic repository structure and complexity signals.
Production source79K tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence116K tokens
91 detected test files contribute separately from production code.
Configuration and infrastructure9K tokens
8 manifests and 0 workspace boundaries were detected.
Documentation56K tokens
35 documentation files remain visible as a distinct enablement signal.
Integration surface2,195 signals
91 dependency declarations and 601 public-interface signals were measured.
Repository structure6 levels deep
0 large files and 2,454 branch signals add structural context.
Excluded from authored evidence0 files
1 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.
architecture
Interface builder
At least 500 deterministic public interface signals were measured in source.
architecture
Integration surface
At least 1,000 deterministic integration signals were measured in source.
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 evidence165.3KProduction, tests, configuration, and documentation
Estimated implementation output165.3KImplementation, retries, integration, and verification
Engineering oversight13.2 hoursOrientation, integration, tests, and review
Active build time1.7 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit 623efe261a48adffff57a1e68616096366a2ad14, 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.
