Security-first purple-team agent runtime in Rust with WASM sandboxing, approvals, scheduling, pgvector memory, and tamper-evident evidence logging.
View jason-allen-oneal/DemonClaw on GitHubSecurity-first purple-team agent runtime in Rust with WASM sandboxing, approvals, scheduling, pgvector memory, and tamper-evident evidence logging.
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.
Modeled range $552.01 to $828.01
6,957 source lines across 42 authored files
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.
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.
Ranked from the public GitHub contributor evidence available at the latest scan. This table describes measured repository activity, not ownership or original authorship.
| Rank | Contributor | Contributions | Share of top group | Latest measured activity |
|---|---|---|---|---|
| #1 |  Jason O'Neal@jason-allen-oneal | 74 | 100.0% | Current GitHub contributor snapshot |
Security-first purple-team agent runtime in Rust with WASM sandboxing, approvals, scheduling, pgvector memory, and tamper-evident evidence logging.
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.
Established based on deterministic repository structure and complexity signals.
First-party implementation tokens eligible for the modeled code-scale input.
5 detected test files contribute separately from production code.
5 manifests and 0 workspace boundaries were detected.
21 documentation files remain visible as a distinct enablement signal.
55 dependency declarations and 0 public-interface signals were measured.
0 large files and 794 branch signals add structural context.
0 generated files were identified. Ignored and generated material does not inflate RepoWorth.
Code scale, branching, dependencies, languages, structure, and visible test evidence shape the implementation and verification effort represented by this repository.
Measured from the current source archive.
Derived from branch density, dependencies, languages, and code scale.
Measures visible test code relative to the source corpus.
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.
CodeValuation.com counted supported authored source on commit 2d5d15a7b6fcb9a32ad335bc7b03d92738d080ab, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
Supported first-party source, tests, configuration, manifests, repository structure, dependency signals, and framework boundaries.
Common generated and vendored files, build output, dependencies, lockfiles, minified assets, binaries, media, and private systems outside this repository.
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.
Enter a public GitHub URL to create a current repository reading.