Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 17:39 UTC

com-lihaoyi / mill-moduledefs

Scalac compiler plugin to support Mill modules

Scala · ShellMIT★ 7 stars⑂ 4 forkssince Oct 2022View on GitHub ↗

com-lihaoyi/mill-moduledefs holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Vitality (73/100) and lowest on AI Readiness (32/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

54
overall / 100
Moderate

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.

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

Ownership

com-lihaoyiOrganization
436 followers24 public repossince Feb 2021

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

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
36/36Push recencylast push 6 days ago
6.9/36Commit cadence10/52 weeks with commits
12.1/18Commit volume21 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year21
human_commit_share0.978
days_since_last_push6
active_weeks_last_year10

Release discipline

100Exceptional
How it's scored
27/27Ships releases23 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~29.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count23
latest_release_tag0.13.4
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases29.7
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

32At Risk · 17% of overall
How it's scored
12.6/60Stars7 stars
4/25Forks4 forks
0/15Watchers0 watchers
Inputs used
forks4
stars7
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.5/22.5Commit distributiontop contributor authored 58% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 12 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.578
How it's scored
21/42Issue resolution50% of issues closed
30/30PR acceptance26/26 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs26
open_issues1
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.5
closed_unmerged_prs0
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
30/30Ownership backingorganization-owned
0/20Verified domain
19/25Owner reach436 followers of com-lihaoyi
21.3/25Track record24 public repos, account ~5 yr old
Inputs used
followers436
owner_typeOrganization
is_verifiedno
owner_logincom-lihaoyi
public_repos24
account_age_days2,022

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsmill, scala, scalac-plugin
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests4 out of 4 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 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 12 contributing companies or organizations
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
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
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-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories9
affected_packages9
assessed_packages92
unassessed_packages0
affected_by_severitycritical 9
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 92 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14.2/40Legible commit history24 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.267
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingScala (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 92
8/8Automated maintenance2 of the last 92 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.022
How it's scored
45/45Type-checkable codeScala (statically typed)
55/55Manageable file sizes0/5 source files over 60KB
Inputs used
primary_languageScala
largest_source_bytes5,972
source_files_sampled5
oversized_source_files0

Key facts

7GitHub stars
4contributors
21commits, last 12 months
6days since last push
23releases
1bus factor
1open issues
package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
1Releases

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.

1223344412022-102023-092024-08
Major 0Minor 0Patch 1

Each point covers 2 days.

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-09-04 17:39 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests4 out of 4 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 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 92

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

RegistryPackageVersionRelation
Mavencom.lihaoyi:sourcecode_2.130.3.0indirect
Mavencom.lihaoyi:sourcecode_30.3.0indirect
Mavenio.github.java-diff-utils:java-diff-utils4.12indirect
Mavenjline:jline2.14.6indirect
Mavennet.java.dev.jna:jna5.13.0indirect
Mavennet.java.dev.jna:jna5.14.0indirect
Mavennet.java.dev.jna:jna5.15.0indirect
Mavennet.java.dev.jna:jna5.3.1indirect
Mavennet.java.dev.jna:jna5.8.0indirect
Mavennet.java.dev.jna:jna5.9.0indirect
Mavenorg.fusesource.jansi:jansi1.12indirect
Mavenorg.jline:jline3.14.1indirect
Mavenorg.jline:jline3.15.0indirect
Mavenorg.jline:jline3.16.0indirect
Mavenorg.jline:jline3.19.0indirect
Mavenorg.jline:jline3.20.0indirect
Mavenorg.jline:jline3.21.0indirect
Mavenorg.jline:jline3.22.0indirect
Mavenorg.jline:jline3.24.1indirect
Mavenorg.jline:jline3.25.1indirect
Mavenorg.jline:jline3.26.3indirect
Mavenorg.jline:jline-native3.25.1indirect
Mavenorg.jline:jline-native3.27.0indirect
Mavenorg.jline:jline-reader3.25.1indirect
Mavenorg.jline:jline-reader3.27.0indirect
Mavenorg.jline:jline-terminal3.25.1indirect
Mavenorg.jline:jline-terminal3.27.0indirect
Mavenorg.jline:jline-terminal-jna3.25.1indirect
Mavenorg.jline:jline-terminal-jna3.27.0indirect
Mavenorg.scala-lang.modules:scala-asm9.6.0-scala-1indirect
Mavenorg.scala-lang.modules:scala-asm9.7.0-scala-2indirect
Mavenorg.scala-lang:scala-compiler2.13.0indirect
Mavenorg.scala-lang:scala-compiler2.13.1indirect
Mavenorg.scala-lang:scala-compiler2.13.10indirect
Mavenorg.scala-lang:scala-compiler2.13.11indirect
Mavenorg.scala-lang:scala-compiler2.13.12indirect
Mavenorg.scala-lang:scala-compiler2.13.13indirect
Mavenorg.scala-lang:scala-compiler2.13.14indirect
Mavenorg.scala-lang:scala-compiler2.13.15indirect
Mavenorg.scala-lang:scala-compiler2.13.2indirect
Mavenorg.scala-lang:scala-compiler2.13.3indirect
Mavenorg.scala-lang:scala-compiler2.13.4indirect
Mavenorg.scala-lang:scala-compiler2.13.5indirect
Mavenorg.scala-lang:scala-compiler2.13.6indirect
Mavenorg.scala-lang:scala-compiler2.13.7indirect
Mavenorg.scala-lang:scala-compiler2.13.8indirect
Mavenorg.scala-lang:scala-compiler2.13.9indirect
Mavenorg.scala-lang:scala-library2.13.0indirect
Mavenorg.scala-lang:scala-library2.13.1indirect
Mavenorg.scala-lang:scala-library2.13.10indirect
Mavenorg.scala-lang:scala-library2.13.11indirect
Mavenorg.scala-lang:scala-library2.13.12indirect
Mavenorg.scala-lang:scala-library2.13.13indirect
Mavenorg.scala-lang:scala-library2.13.14indirect
Mavenorg.scala-lang:scala-library2.13.15indirect
Mavenorg.scala-lang:scala-library2.13.2indirect
Mavenorg.scala-lang:scala-library2.13.3indirect
Mavenorg.scala-lang:scala-library2.13.4indirect
Mavenorg.scala-lang:scala-library2.13.5indirect
Mavenorg.scala-lang:scala-library2.13.6indirect
Mavenorg.scala-lang:scala-library2.13.7indirect
Mavenorg.scala-lang:scala-library2.13.8indirect
Mavenorg.scala-lang:scala-library2.13.9indirect
Mavenorg.scala-lang:scala-reflect2.13.0indirect
Mavenorg.scala-lang:scala-reflect2.13.1indirect
Mavenorg.scala-lang:scala-reflect2.13.10indirect
Mavenorg.scala-lang:scala-reflect2.13.11indirect
Mavenorg.scala-lang:scala-reflect2.13.12indirect
Mavenorg.scala-lang:scala-reflect2.13.13indirect
Mavenorg.scala-lang:scala-reflect2.13.14indirect
Mavenorg.scala-lang:scala-reflect2.13.15indirect
Mavenorg.scala-lang:scala-reflect2.13.2indirect
Mavenorg.scala-lang:scala-reflect2.13.3indirect
Mavenorg.scala-lang:scala-reflect2.13.4indirect
Mavenorg.scala-lang:scala-reflect2.13.5indirect
Mavenorg.scala-lang:scala-reflect2.13.6indirect
Mavenorg.scala-lang:scala-reflect2.13.7indirect
Mavenorg.scala-lang:scala-reflect2.13.8indirect
Mavenorg.scala-lang:scala-reflect2.13.9indirect
Mavenorg.scala-lang:scala3-compiler_33.5.0indirect
Mavenorg.scala-lang:scala3-compiler_33.5.2indirect
Mavenorg.scala-lang:scala3-compiler_33.6.2indirect
Mavenorg.scala-lang:scala3-interfaces3.5.0indirect
Mavenorg.scala-lang:scala3-interfaces3.5.2indirect
Mavenorg.scala-lang:scala3-interfaces3.6.2indirect
Mavenorg.scala-lang:scala3-library_33.5.2indirect
Mavenorg.scala-lang:scala3-library_33.6.2indirect
Mavenorg.scala-lang:tasty-core_33.5.0indirect
Mavenorg.scala-lang:tasty-core_33.5.2indirect
Mavenorg.scala-lang:tasty-core_33.6.2indirect
Mavenorg.scala-sbt:compiler-interface1.9.6indirect
Mavenorg.scala-sbt:util-interface1.9.8indirect
Dependency advisories 9

This repository publishes no package the index resolves, so its own dependency graph was assessed — 92 packages, which also include development and test pins that never ship: 9 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
org.scala-lang:scala-library2.13.0indirectcritical12.13.9
org.scala-lang:scala-library2.13.1indirectcritical12.13.9
org.scala-lang:scala-library2.13.2indirectcritical12.13.9
org.scala-lang:scala-library2.13.3indirectcritical12.13.9
org.scala-lang:scala-library2.13.4indirectcritical12.13.9
org.scala-lang:scala-library2.13.5indirectcritical12.13.9
org.scala-lang:scala-library2.13.6indirectcritical12.13.9
org.scala-lang:scala-library2.13.7indirectcritical12.13.9
org.scala-lang:scala-library2.13.8indirectcritical12.13.9

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