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

in-app-notifications-example-nextjs Codebase Valuation

In-app notifications example app, written using NextJS

View knocklabs/in-app-notifications-example-nextjs on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/knocklabs

in-app-notifications-example-nextjs

In-app notifications example app, written using NextJS

RepoWorth$131.38Current measured development value · Less than one active build day
Rebuild complexity62.403/100Profile: Complex
10.5K code tokens25 source filesJavaScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/in-app-notifications-example-nextjs
Authored code10.5K tokens · 1,576 source lines
Complexity62.403/100 · Complex
Primary stackJavaScript
Scan coverage99.89% · 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
$131.38

Modeled range $105.10 to $157.66

0.1 active build days0.7 engineering hours9K implementation tokens
Repository evidenceMeasured at the scanned commit
10.5K tokens

1,576 source lines across 25 authored files

0 test files25 dependencies99.89% 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$131.38
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity62/100Measured from code scale and structural signals
Maintainability66/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

84 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
#1cjbell@cjbell1839.1%Current GitHub contributor snapshot
#2JEverhart383@JEverhart3831430.4%Current GitHub contributor snapshot
#3Connor Lindsey@connorlindsey613.0%Current GitHub contributor snapshot
#4kylemcd@kylemcd48.7%Current GitHub contributor snapshot
#5thomaswhyyou@thomaswhyyou12.2%Current GitHub contributor snapshot
#6ghecho@ghecho12.2%Current GitHub contributor snapshot
#7rachael-t@rachael-t12.2%Current GitHub contributor snapshot
#8woodke@woodke12.2%Current GitHub contributor snapshot
About in-app-notifications-example-nextjs

What the public repository appears to contain.

In-app notifications example app, written using NextJS

License
MIT
Default branch
main
GitHub stars
29
Forks
8
Last public push
Jun 18, 2026
Repository state
Active public repository
Detected language profile44.3KB authored source
JavaScript97.33%
CSS2.67%
Source files25
Test files0
Manifests1
Dependencies25
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 signal66/100

Established based on deterministic repository structure and complexity signals.

Production source10.5K 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 infrastructure372 tokens

1 manifests and 0 workspace boundaries were detected.

Documentation2.1K tokens

1 documentation files remain visible as a distinct enablement signal.

Integration surface190 signals

25 dependency declarations and 12 public-interface signals were measured.

Repository structure2 levels deep

0 large files and 83 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 evidence9KProduction, tests, configuration, and documentation
Estimated implementation output9KImplementation, retries, integration, and verification
Engineering oversight0.7 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 653eb2f627dd753ad4e928ed4096abfd4266aca8, 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.