Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 23:20 UTC

ljhwang / aspect

A parallel, extensible finite element code to simulate convection in both 2D and 3D models.

C++Custom license★ 0 stars⑂ 0 forkssince Jun 2018forkView on GitHub ↗

ljhwang/aspect holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on AI Readiness (78/100) and lowest on Community & Adoption (9/100). It was last updated 39 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

Lorraine HwangPersonal account
14 followers36 public repossince May 2013Computational Infrastructure for Geodynamics

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

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
18/36Push recency — last push 39 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 1,120 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,120
human_commit_share1
days_since_last_push39
active_weeks_last_year47
How it's scored
16.2/27Ships releases — 5 version tags (no GitHub releases)
0/36Release recency — latest release 3,069 days ago
12.6/27Release cadence — a release every ~192.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count5
latest_release_tagv2.0.1
releases_from_tagsyes
days_since_latest_release3,069
mean_days_between_releases192.5
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?

9Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateno

Sustainability & Governance

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

45Weak · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.8/22.5Commit distribution — top contributor authored 25% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 24 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.253
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
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): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.5/25Owner reach — 14 followers of ljhwang
23.4/25Track record — 36 public repos, account ~13 yr old
Inputs used
followers14
owner_typeUser
is_verified—
owner_loginljhwang
public_repos36
account_age_days4,927
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows — 10 workflow(s)
24/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_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://aspect.geodynamics.org/
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://aspect.geodynamics.org/
docs_sitehttps://aspect.geodynamics.org/
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 24 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 45 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories65
affected_packages3
assessed_packages41
unassessed_packages6
affected_by_severitycritical 1, high 2
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 41 resolved dependencies against OSV. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

78Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
27.7/40Legible commit history — 52 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.52
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes1,368
How it's scored
18/18One-command bootstrap — benchmarks/tangurnis/Makefile, contrib/docker/docker/jupyter/Makefile, doc/Makefile, doc/sphinx/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C++ (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesbenchmarks/tangurnis/Makefile, contrib/docker/docker/jupyter/Makefile, doc/Makefile, doc/sphinx/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C++ (statically typed)
53.7/55Manageable file sizes — 40/1,697 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes2,361,398
source_files_sampled1,697
oversized_source_files40
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples, notebooks
Inputs used
example_dirsexamples, notebooks
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
99contributors
1,120commits, last 12 months
39days since last push
5releases
3bus factor
0open issues
—package ecosystems

Data collection warnings

  • Community profile unavailable
  • Could not fetch pypi package 'aspect-with-python' from its registry

More detail

OpenSSF Scorecard 2.7 / 10
2.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-11-16 23:19 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 24 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities45 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIlandlab—contrib/landlab/pyproject.toml
All dependencies 47

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

RegistryPackageVersionRelation
PyPIlandlab2.11.0direct
PyPIaspect-with-python0.0.0indirect
PyPIblack26.5.1indirect
PyPIbmipy2.0.1indirect
PyPIcertifi2026.7.22indirect
PyPIcftime1.6.5indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcontourpy1.3.3indirect
PyPIcycler0.12.1indirect
PyPIfonttools4.63.0indirect
PyPIjinja23.1.6indirect
PyPIkiwisolver1.5.0indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImatplotlib3.11.1indirect
PyPImdurl0.1.2indirect
PyPImypy-extensions1.1.0indirect
PyPImyst-parser—indirect
PyPInetcdf41.7.4indirect
PyPInumpy2.5.1indirect
PyPIpackaging26.2indirect
PyPIpandas3.0.5indirect
PyPIpathspec1.1.1indirect
PyPIpatsy1.0.2indirect
PyPIpillow12.3.0indirect
PyPIplatformdirs4.11.0indirect
PyPIpy-richdem2.2.0rc2indirect
PyPIpygments2.20.0indirect
PyPIpyparsing3.3.2indirect
PyPIpyshp3.1.5indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytokens0.4.1indirect
PyPIpyyaml6.0.3indirect
PyPIrequireit0.9.0indirect
PyPIrich15.0.0indirect
PyPIrich-click1.9.8indirect
PyPIscipy1.18.0indirect
PyPIsix1.17.0indirect
PyPIsphinx-book-theme—indirect
PyPIsphinx-copybutton—indirect
PyPIsphinx-design—indirect
PyPIsphinx-inline-tabs—indirect
PyPIsphinxcontrib-bibtex—indirect
PyPIstatsmodels0.14.6indirect
PyPItzdata2026.3indirect
PyPIxarray2026.7.0indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 41 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 0 are direct. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
pillow12.3.0indirectcritical6213.0.0
black26.5.1indirecthigh126.10.1
certifi2026.7.22indirecthigh22026.10.18

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.