Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 03:17 UTC

modem-dev / hunk

Review-first terminal diff viewer for agentic coders

TypeScriptMIT★ 8,842 stars⑂ 276 forkssince Mar 2026View on GitHub ↗
KindCommand-line toolLibraryNetwork servicehow this is determined

modem-dev/hunk holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (84/100) and lowest on Security (57/100). It was last updated today. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

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.

86
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 72 is calibrated to 86 on the published index scale (record calibration 2026-08-02).

Ownership

ModemOrganization · verified domain
163 followers15 public repossince Apr 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmhunkdiff0.20.020,906712 days agoaicode-reviewdiffgitterminaltui

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
15.9/36Commit cadence23/52 weeks with commits
18/18Commit volume718 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year718
human_commit_share1
days_since_last_push0
active_weeks_last_year23
How it's scored
27/27Ships releases62 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~3.6 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count62
latest_release_tagv0.20.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases3.6

Community & Adoption

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

77Good · 17% of overall
How it's scored
60/60Stars8,842 stars
20.3/25Forks276 forks
5.6/15Watchers11 watchers
Inputs used
forks276
stars8,842
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
57.6/80Monthly downloads20,906 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageshunkdiff
dependents
ecosystemsnpm
total_downloads
monthly_downloads20,906
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.5/22.5Commit distributiontop contributor authored 85% of commits
13.5/13.5Contributor breadth69 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled69
top_contributor_share0.846
How it's scored
23.4/42Issue resolution56% of issues closed
27.2/30PR acceptance572/632 decided PRs merged
6.5/13Newcomer PR acceptance4/8 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/30 approved changesets -- score normalized to 0
Inputs used
merged_prs572
open_issues83
closed_issues104
prs_merged_7d41
prs_decided_7d55
prs_merged_30d43
prs_decided_30d60
issue_closed_ratio0.556
closed_unmerged_prs60
first_time_authors_30d8
first_time_prs_merged_30d4
first_time_prs_decided_30d8
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
15.9/25Owner reach163 followers of modem-dev
11.5/25Track record15 public repos, account ~1 yr old
Inputs used
followers163
owner_typeOrganization
is_verifiedyes
owner_loginmodem-dev
public_repos15
account_age_days498

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 2 days ago
20/20Version history71 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageshunkdiff
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests26 out of 26 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://hunk.dev
10/10Repository description
10/10Topics10 topics
0/10Wiki
Inputs used
topicscli, code-review, diff, git, tui, agents, jj, jujutsu, sapling, terminal
has_wikino
homepagehttps://hunk.dev
docs_sitehttps://hunk.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests26 out of 26 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities38 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages28
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:hunkdiff@0.20.0 runtime dependency closure — what installing the published package pulls in — 28 packages. Reachability is not analyzed.

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.

77Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://hunk.dev/llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://hunk.dev/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes13,123
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json, website/tsconfig.json
10/10Reproducible environmentNix
10/10Demonstrated agent practice27 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixyes
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json, website/tsconfig.json
agent_commit_share0.27
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.5/55Manageable file sizes8/800 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes133,474
source_files_sampled800
oversized_source_files8
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

8,842GitHub stars
69contributors
718commits, last 12 months
0days since last push
62releases
1bus factor
83open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 18 authors (cap 12)

More detail

Star and fork history 0 ★ / 276 ⇿
0Stars
276Forks
61Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

050100150200250300276232026-032026-062026-08
Major 0Minor 16Patch 25
OpenSSF Scorecard 4.6 / 10
4.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-28 03:17 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests26 out of 26 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities38 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
npmbun^1.3.14package.json
npmchokidar^4.0.3package.json
npmcommander^14.0.3package.json
npmdiff^8.0.3package.json
npmget-east-asian-width^1.5.0package.json
npmshell-quote1.9.0package.json
npmstring-width^8.2.1package.json
npmzod^4.3.6package.json
npm@astrojs/markdown-remark^7.2.1website/package.json
npm@astrojs/sitemap^3.7.3website/package.json
npm@astrojs/starlight^0.41.5website/package.json
npm@fontsource-variable/jetbrains-mono^5.2.8website/package.json
npmastro^7.1.4website/package.json
npmstarlight-dot-md^0.2.1website/package.json
npmstarlight-llms-txt^0.11.0website/package.json
All dependencies 56

Full resolved dependency set from the GitHub dependency graph: 19 direct and 37 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@astrojs/markdown-remark^7.2.1direct
npm@astrojs/sitemap^3.7.3direct
npm@astrojs/starlight^0.41.5direct
npm@fontsource-variable/jetbrains-mono^5.2.8direct
npmastro^7.1.4direct
npmbun^1.3.14direct
npmchokidar^4.0.3direct
npmcommander12.1.0direct
npmcommander13.1.0direct
npmcommander^14.0.3direct
npmdiff^8.0.3direct
npmget-east-asian-width^1.5.0direct
npmshell-quote1.9.0direct
npmstarlight-dot-md^0.2.1direct
npmstarlight-llms-txt^0.11.0direct
npmstring-width^8.2.1direct
npmzod3.24.2direct
npmzod4.0.5direct
npmzod^4.3.6direct
npm@astrojs/check^0.9.10indirect
npm@axe-core/playwright^4.10.2indirect
npm@changesets/changelog-github^0.7.0indirect
npm@opentui/core0.4.1indirect
npm@opentui/core0.4.3indirect
npm@opentui/core^0.5.1indirect
npm@opentui/react0.4.1indirect
npm@opentui/react0.4.3indirect
npm@opentui/react^0.5.1indirect
npm@pierre/diffs1.3.5indirect
npm@playwright/test^1.56.1indirect
npm@types/bun1.2.4indirect
npm@types/bun1.3.1indirect
npm@types/bun1.3.14indirect
npm@types/react19.0.10indirect
npm@types/react19.2.2indirect
npm@types/react^19.2.14indirect
npm@types/ws^8.18.1indirect
npmdependency-cruiser18.2.0indirect
npmknip^6.32.0indirect
npmlint-staged^16.4.0indirect
npmmarked17.0.1indirect
npmoxfmt0.16.0indirect
npmoxfmt0.20.0indirect
npmoxfmt^0.41.0indirect
npmoxlint0.16.0indirect
npmoxlint1.15.0indirect
npmoxlint^1.56.0indirect
npmreact19.1.0indirect
npmreact19.2.0indirect
npmreact^19.2.4indirect
npmsimple-git-hooks^2.13.1indirect
npmtuistory^0.0.16indirect
npmtypescript5.7.3indirect
npmtypescript5.9.2indirect
npmtypescript^5.9.3indirect
npmws^8.18.3indirect
Dependency advisories 0

Installing npm:hunkdiff@0.20.0 pulls in 28 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.

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