Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-30 13:50 UTC

dahlia / hongdown

A Markdown formatter that enforces Hong Minhee's Markdown style conventions

RustGPL-3.0★ 197 stars⑂ 9 forkssince Jan 2026View on GitHub ↗
KindLibraryCommand-line toolWeb interfacehow this is determined

dahlia/hongdown holds a health index of 65 out of 100, placing it in the Good band. It scores highest on AI Readiness (75/100) and lowest on Security (39/100). It was last updated 33 days ago. A single contributor accounts for most of its recent work.

65
overall / 100
Good

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.

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

Ownership

Hong Minhee (洪 民憙)Personal account
1,365 followers275 public repossince Jun 2008@fedify-dev

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iohongdown0.5.377812233 days ago

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
18/36Push recencylast push 33 days ago
11.1/36Commit cadence16/52 weeks with commits
18/18Commit volume431 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year431
human_commit_share1
days_since_last_push33
active_weeks_last_year16
How it's scored
27/27Ships releases30 releases published
36/36Release recencylatest release 33 days ago
27/27Release cadencea release every ~9.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count30
latest_release_tag0.5.3
releases_from_tagsno
days_since_latest_release33
mean_days_between_releases9.9

Community & Adoption

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

48Weak · 17% of overall
How it's scored
37.2/60Stars197 stars
7.5/25Forks9 forks
0/15Watchers2 watchers
Inputs used
forks9
stars197
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
38.6/80Monthly downloads778 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageshongdown
dependents
ecosystemscrates
total_downloads4,605
monthly_downloads778
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?

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.7/22.5Commit distributiontop contributor authored 97% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.97
How it's scored
40.1/42Issue resolution96% of issues closed
28.2/30PR acceptance16/17 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 7/12 approved changesets -- score normalized to 5
Inputs used
merged_prs16
open_issues1
closed_issues21
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.955
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): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
22.5/25Owner reach1,365 followers of dahlia
25/25Track record275 public repos, account ~18 yr old
Inputs used
followers1,365
owner_typeUser
is_verified
owner_logindahlia
public_repos275
account_age_days6,661
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 33 days ago
20/20Version history122 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageshongdown
ecosystemscrates
any_deprecatedno
min_days_since_publish33

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://dahlia.github.io/hongdown/
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicscommonmark, formatter, gfm, markdown
has_wikino
homepagehttps://dahlia.github.io/hongdown/
docs_sitehttps://dahlia.github.io/hongdown/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

39Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2/2.5CI-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 7/12 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 7 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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.5Vulnerabilities28 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.9

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.

75Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
38.9/40Legible commit history73 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.73
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes18,254
How it's scored
18/18One-command bootstrapmise.toml
22/22Automated tests
0/11Lint / format config
11/11Static type checkingpackages/vscode/tsconfig.json, packages/wasm/tsconfig.json, website/tsconfig.json
10/10Reproducible environmentNix, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixyes
has_testsyes
lockfilesCargo.lock, pnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configno
typecheck_configspackages/vscode/tsconfig.json, packages/wasm/tsconfig.json, website/tsconfig.json
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
51.7/55Manageable file sizes4/67 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes294,228
source_files_sampled67
oversized_source_files4

Key facts

197GitHub stars
5contributors
431commits, last 12 months
33days since last push
30releases
1bus factor
1open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
28Releases

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.

035810922026-012026-042026-07
Major 0Minor 5Patch 23
OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-30 13:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 7/12 approved changesets -- score normalized to 5
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
0Vulnerabilities28 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
crates.ioclap4.5.54Cargo.toml
crates.iocomrak0.49.0Cargo.toml
crates.ioglob0.3.3Cargo.toml
crates.iohtml-escape0.2.13Cargo.toml
crates.ioindexmap2.12.1Cargo.toml
crates.iorayon1.11.0Cargo.toml
crates.ioregex1.12.2Cargo.toml
crates.ioserde1.0.228Cargo.toml
crates.iosimilar2.7.0Cargo.toml
crates.iotoml0.9.10Cargo.toml
crates.iounicode-width0.2.2Cargo.toml
crates.iowalkdir2.5.0Cargo.toml
crates.iowasm-bindgen0.2Cargo.toml
crates.ioserde-wasm-bindgen0.6Cargo.toml
crates.iojs-sys0.3Cargo.toml
crates.iogetrandom0.3Cargo.toml
crates.ioignore0.4.25Cargo.toml
crates.iodirs6.0.0Cargo.toml
crates.iocaseless0.2.2Cargo.toml
npm@fontsource-variable/source-serif-4^5.2.9website/package.json
npm@fontsource/ibm-plex-mono^5.2.7website/package.json
npm@hongdown/wasmworkspace:*website/package.json
npmsolid-js^1.9.10website/package.json
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.

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 statisticscrates.io.