Current repository readingScanned Jul 24, 2026, 9:57 PM UTC

amber Codebase Valuation

๐Ÿ’Ž Amber the programming language compiled to Bash/Ksh/Zsh

View amber-lang/amber on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/amber-lang

amber

๐Ÿ’Ž Amber the programming language compiled to Bash/Ksh/Zsh

RepoWorth$2,145Current measured development value ยท 1.4 active build days
Rebuild complexity72.942/100Profile: Complex
166.1K code tokens189 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/amber
Authored code166.1K tokens ยท 21,968 source lines
Complexity72.942/100 ยท Complex
Primary stackRust
Scan coverage95.44% ยท 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,145

Modeled range $1,716 to $2,574

1.4 active build days11.1 engineering hours138.7K implementation tokens
Repository evidenceMeasured at the scanned commit
166.1K tokens

21,968 source lines across 189 authored files

32 test files68 dependencies95.44% 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,145
Current measured reading
Measured ยท Jul 24, 2026Data through ยท Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage95%current scan
Complexity73/100Measured from code scale and structural signals
Maintainability76/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.

52-week repository activity

218 commits across the public default-branch history.

Commit activity provides delivery context. It does not assign a historical RepoWorth to unscanned commits or treat commit count as value.

Jul 27, 2025Weekly commitsJul 19, 2026

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
#1Ph0enixKM@Ph0enixKM40762.3%Current GitHub contributor snapshot
#2Mte90@Mte906610.1%Current GitHub contributor snapshot
#3lens0021@lens0021639.6%Current GitHub contributor snapshot
#4b1ek@b1ek355.4%Current GitHub contributor snapshot
#5hdwalters@hdwalters253.8%Current GitHub contributor snapshot
#6Tirito6626@Tirito6626162.5%Current GitHub contributor snapshot
#7arapower@arapower111.7%Current GitHub contributor snapshot
#8KrosFire@KrosFire111.7%Current GitHub contributor snapshot
#9MuhamedMagdi@MuhamedMagdi101.5%Current GitHub contributor snapshot
#10kilianc@kilianc91.4%Current GitHub contributor snapshot
About amber

What the public repository appears to contain.

๐Ÿ’Ž Amber the programming language compiled to Bash/Ksh/Zsh

bashbash-scriptingcompilershacktoberfestkshzsh
License
LGPL-3.0
Default branch
staging
GitHub stars
5,153
Forks
133
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile705.8KB authored source
Rust99.73%
Shell0.27%
Source files189
Test files32
Manifests2
Dependencies68
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 signal76/100

Strong based on deterministic repository structure and complexity signals.

Production source137.9K tokens

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

Test evidence28.1K tokens

32 detected test files contribute separately from production code.

Configuration and infrastructure493 tokens

2 manifests and 0 workspace boundaries were detected.

Documentation2.5K tokens

14 documentation files remain visible as a distinct enablement signal.

Integration surface29 signals

68 dependency declarations and 4 public-interface signals were measured.

Repository structure4 levels deep

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

Excluded from authored evidence0 files

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

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 evidence138.7KProduction, tests, configuration, and documentation
Estimated implementation output138.7KImplementation, retries, integration, and verification
Engineering oversight11.1 hoursOrientation, integration, tests, and review
Active build time1.4 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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