Current repository readingScanned Jul 24, 2026, 5:23 AM UTC

google_ml_kit_flutter Codebase Valuation

A flutter plugin that implements Google's standalone ML Kit

View flutter-ml/google_ml_kit_flutter on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/flutter-ml

google_ml_kit_flutter

A flutter plugin that implements Google's standalone ML Kit

RepoWorth$1,748Current measured development value · 1.0 active build days
Rebuild complexity90.555/100Profile: Complex
120K code tokens186 source filesDart primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/google-ml-kit-flutter
Authored code120K tokens · 17,646 source lines
Complexity90.555/100 · Complex
Primary stackDart
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
$1,748

Modeled range $1,399 to $2,098

1.0 active build days8.2 engineering hours102.7K implementation tokens
Repository evidenceMeasured at the scanned commit
120K tokens

17,646 source lines across 186 authored files

0 test files918 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$1,748
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity91/100Measured from code scale and structural signals
Maintainability50/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

30 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
#1fbernaly@fbernaly11947.6%Current GitHub contributor snapshot
#2bharat-biradar@bharat-biradar9036.0%Current GitHub contributor snapshot
#3bensonarafat@bensonarafat249.6%Current GitHub contributor snapshot
#4panmari@panmari41.6%Current GitHub contributor snapshot
#5jaredsburrows@jaredsburrows31.2%Current GitHub contributor snapshot
#6Old Autumn@penkzhou20.8%Current GitHub contributor snapshot
#7X-SLAYER@X-SLAYER20.8%Current GitHub contributor snapshot
#8feinstein@feinstein20.8%Current GitHub contributor snapshot
#9ipcjs@ipcjs20.8%Current GitHub contributor snapshot
#10khjde1207@khjde120720.8%Current GitHub contributor snapshot
About google_ml_kit_flutter

What the public repository appears to contain.

A flutter plugin that implements Google's standalone ML Kit

hactoberfest
License
MIT
Default branch
develop
GitHub stars
1,270
Forks
886
Last public push
Jul 21, 2026
Repository state
Active public repository
Detected language profile556.5KB authored source
Dart49.45%
Kotlin26.85%
Swift16.62%
GRADLE4.19%
Python1.28%
Shell0.95%
Ruby0.6%
Objective-C0.05%
Source files186
Test files0
Manifests22
Dependencies918
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 signal50/100

Developing based on deterministic repository structure and complexity signals.

Production source120K 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

22 manifests and 0 workspace boundaries were detected.

Documentation71.8K tokens

69 documentation files remain visible as a distinct enablement signal.

Integration surface608 signals

918 dependency declarations and 69 public-interface signals were measured.

Repository structure13 levels deep

0 large files and 1,974 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.

breadth

Polyglot system

At least five languages each represent one percent or more of measured source tokens.

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 scaleModerate

Measured from the current source archive.

ComplexityHigh

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 evidence102.7KProduction, tests, configuration, and documentation
Estimated implementation output102.7KImplementation, retries, integration, and verification
Engineering oversight8.2 hoursOrientation, integration, tests, and review
Active build time1.0 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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