Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 14:34 UTC

DIG-Network / dig-merkle

Canonical DIG Network crate for the CHIP-0035 DataLayer coin/singleton that anchors a .dig file's merkle root on-chain: pure key-free SpendBundle builders (mint/update-root/update-ownership/oracle/melt/hydrate/walk-lineage) over chia-wallet-sdk. Never broadcasts, never holds keys; the consumer signs + pushes.

RustApache-2.0★ 0 stars⑂ 0 forkssince Jul 2026View on GitHub ↗
KindLibraryhow this is determined
#chia-network#dig-network

DIG-Network/dig-merkle holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (66/100) and lowest on Security (1/100). It was last updated 48 days ago. A single contributor accounts for most of its recent work.

45
overall / 100
Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

45
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 47 is calibrated to 45 on the published index scale (record calibration 2026-08-02).

Ownership

DIG NetworkOrganization
42 followers111 public repossince Sep 2024

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iodig-merkle0.9.13,1151548 days agochiachip-0035datalayerdigsingletonapi-bindings

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

64Moderate · 21% of overall

Development activity

40Weak
How it's scored
18/36Push recency — last push 48 days ago
4.2/36Commit cadence — 6/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year30
human_commit_share1
days_since_last_push48
active_weeks_last_year6

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 15 releases published
36/36Release recency — latest release 48 days ago
27/27Release cadence — a release every ~5.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count15
latest_release_tagv0.9.1
releases_from_tagsno
days_since_latest_release48
mean_days_between_releases5.1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

39Weak · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

70Good
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

58Moderate
How it's scored
46.6/80Monthly downloads — 3,115 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdig-merkle
dependents—
ecosystemscrates
total_downloads9,658
monthly_downloads3,115
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

66Good · 23% of overall

Maintainer resilience (bus factor)

25At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.9/22.5Commit distribution — top contributor authored 52% of commits
2.7/13.5Contributor breadth — 2 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.517

Issue & PR responsiveness

93Exceptional
How it's scored
0/42Issue resolution — no issues or no data
28/30PR acceptance — 14/15 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs14
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

59Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
11.7/25Owner reach — 42 followers of DIG-Network
17.3/25Track record — 111 public repos, account ~2 yr old
Inputs used
followers42
owner_typeOrganization
is_verifiedno
owner_loginDIG-Network
public_repos111
account_age_days778

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 48 days ago
20/20Version history — 15 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdig-merkle
ecosystemscrates
any_deprecatedno
min_days_since_publish48

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall

Engineering practices

30At Risk
How it's scored
24/24CI workflows — 6 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

75Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/dig-merkle
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicschia-network, dig-network
has_wikiyes
homepage—
docs_sitehttps://docs.rs/dig-merkle
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

1Critical · 16% of overall

Security posture

1Critical
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesCargo.lock
manifestsCargo.toml
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

54Moderate · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 30 of 30 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

48Weak
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 15 of the last 30 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.5
toolchain_manifestsCargo.toml
dependency_bot_commit_share0

Code legibility for models

97Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
51.6/55Manageable file sizes — 1/16 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes85,781
source_files_sampled16
oversized_source_files1

Key facts

0GitHub stars
2contributors
30commits, last 12 months
48days since last push
15releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/DIG-Network/dig-merkle: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-10-22T14:34:00Z. Please include `8672:3D40AE:3FE3D7:6CDCDD:6ADA1ED5` when reporting this issue.); skipping Scorecard checks

More detail

Direct dependencies 8
RegistryPackageVersion constraintManifest
crates.iochia-wallet-sdk0.36Cargo.toml
crates.iochia-protocol0.36.1Cargo.toml
crates.iochia-puzzle-types0.36.1Cargo.toml
crates.ioclvm-traits0.36.1Cargo.toml
crates.iochia-sha20.36Cargo.toml
crates.iohex-literal0.4Cargo.toml
crates.iothiserror2Cargo.toml
crates.iodig-chainsource-interface0.3Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Related records

Inspected repositories sharing catalogue tags or ecosystems with DIG-Network/dig-merkle. Read them side by side →

99open-telemetry/opentelemetry-rustThe Rust OpenTelemetry implementationExceptional98github/copilot-sdkMulti-platform SDK for integrating GitHub Copilot Agent into apps and servicesExceptional98ZcashFoundation/zebraZcash - Financial Privacy in Rust 🦓Exceptional98wasmerio/wasmer🚀 Fast, secure, lightweight containers based on WebAssemblyExceptional98PyO3/pyo3Rust bindings for the Python interpreterExceptional97awslabs/mountpoint-s3A simple, high-throughput file client for mounting an Amazon S3 bucket as a local file system.Exceptional

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io.