Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 06:41 UTC

ash-project / ash_money

The extension for working with money types in Ash.

ElixirCustom license★ 16 stars⑂ 20 forkssince Nov 2023View on GitHub ↗

ash-project/ash_money holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (75/100) and lowest on AI Readiness (29/100). It was last updated 15 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Ash FrameworkOrganization
384 followers61 public repossince Dec 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexash_money0.2.614,1862738 days ago

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
28.8/36Push recencylast push 15 days ago
12.5/36Commit cadence18/52 weeks with commits
13.9/18Commit volume34 commits in the last year
5/10OpenSSF Scorecard: Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year34
human_commit_share
days_since_last_push15
active_weeks_last_year18
How it's scored
27/27Ships releases4 releases published
36/36Release recencylatest release 38 days ago
19.8/27Release cadencea release every ~116.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count4
latest_release_tagv0.2.6
releases_from_tagsno
days_since_latest_release38
mean_days_between_releases116.1
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?

60Moderate · 17% of overall
How it's scored
19.1/60Stars16 stars
10.7/25Forks20 forks
1.7/15Watchers3 watchers
Inputs used
forks20
stars16
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
55.4/80Monthly downloads14,186 downloads/month across hex
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesash_money
dependents
ecosystemshex
total_downloads125,119
monthly_downloads14,186
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?

75Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
11.2/22.5Commit distributiontop contributor authored 50% of commits
13.5/13.5Contributor breadth14 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.5
How it's scored
42/42Issue resolution100% of issues closed
26.9/30PR acceptance146/163 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/11 approved changesets -- score normalized to 1
Inputs used
merged_prs146
open_issues0
closed_issues9
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs17
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18.6/25Owner reach384 followers of ash-project
25/25Track record61 public repos, account ~6 yr old
Inputs used
followers384
owner_typeOrganization
is_verified
owner_loginash-project
public_repos61
account_age_days2,416
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 hex
35/35Publish recencylatest publish 38 days ago
20/20Version history27 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesash_money
ecosystemshex
any_deprecatedno
min_days_since_publish38

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 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
10/20OpenSSF Scorecard: CI-Tests11 out of 22 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://hexdocs.pm/ash
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsash, elixir, money
has_wikiyes
homepagehttps://hexdocs.pm/ash
docs_sitehttps://hexdocs.pm/ash
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
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.2/2.5CI-Tests11 out of 22 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 2/11 approved changesets -- score normalized to 1
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4.5/5SASTSAST tool is not run on all commits -- score normalized to 9
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesmix.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeElixir without a type-check config
55/55Manageable file sizes0/13 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes16,024
source_files_sampled13
oversized_source_files0

Key facts

16GitHub stars
14contributors
34commits, last 12 months
15days since last push
4releases
1bus factor
0open issues
Hexpackage ecosystems

More detail

OpenSSF Scorecard 5.7 / 10
5.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-07-17 06:41 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests11 out of 22 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/11 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
9SASTSAST tool is not run on all commits -- score normalized to 9
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Hexash~> 3.0 and >= 3.0.15mix.exs
Hexex_money~> 6.0mix.exs
Hexigniter~> 0.5 and >= 0.5.30mix.exs
Hexex_money_sql~> 2.0mix.exs
Hexash_postgres~> 2.0mix.exs
Hexash_graphql~> 1.0mix.exs
Hexash_json_api~> 1.4 and >= 1.4.3mix.exs
All dependencies 75

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

RegistryPackageVersionRelation
Hexash3.29.3direct
Hexash_graphql1.9.4direct
Hexash_json_api1.7.0direct
Hexash_postgres2.10.0direct
Hexex_money6.0.0direct
Hexex_money_sql2.0.0direct
Hexigniter0.8.2direct
Hexabsinthe1.11.0indirect
Hexabsinthe_plug1.5.9indirect
Hexash_sql0.6.5indirect
Hexbunt1.0.0indirect
Hexconv_case0.2.3indirect
Hexcredo1.7.18indirect
Hexcrux0.1.3indirect
Hexdb_connection2.10.1indirect
Hexdecimal3.1.1indirect
Hexdialyxir1.4.7indirect
Hexdigital_token1.0.0indirect
Hexearmark_parser1.4.44indirect
Hexecto3.14.0indirect
Hexecto_sql3.14.0indirect
Hexerlex0.2.8indirect
Hexets0.9.0indirect
Hexex_ast0.12.5indirect
Hexex_check0.16.0indirect
Hexex_cldr_currencies2.17.0indirect
Hexex_doc0.40.1indirect
Hexexpo1.1.1indirect
Hexfile_system1.1.1indirect
Hexfinch0.23.0indirect
Hexgettext1.0.2indirect
Hexgit_cli0.3.0indirect
Hexgit_ops2.10.0indirect
Hexglob_ex0.1.11indirect
Hexhpax1.0.3indirect
Hexiterex0.1.2indirect
Hexjason1.4.5indirect
Hexjson_xema0.6.5indirect
Hexlibgraph0.16.0indirect
Hexlocalize0.41.0indirect
Hexmakeup1.2.1indirect
Hexmakeup_elixir1.0.1indirect
Hexmakeup_erlang1.0.3indirect
Hexmime2.0.7indirect
Hexmint1.9.0indirect
Hexmix_audit2.1.5indirect
Hexmix_test_watch1.4.0indirect
Hexmultigraph0.16.1-mg.4indirect
Hexnimble_options1.1.1indirect
Hexnimble_parsec1.4.2indirect
Hexnimble_pool1.1.0indirect
Hexowl0.13.1indirect
Hexphoenix1.8.8indirect
Hexphoenix_pubsub2.2.0indirect
Hexphoenix_template1.0.4indirect
Hexplug1.20.2indirect
Hexplug_crypto2.1.1indirect
Hexpostgrex0.22.2indirect
Hexreactor1.0.2indirect
Hexreq0.6.2indirect
Hexrewrite1.3.0indirect
Hexsobelow0.14.1indirect
Hexsourceror1.12.2indirect
Hexspark2.7.2indirect
Hexspitfire0.3.13indirect
Hexsplode0.3.1indirect
Hexstream_data1.3.0indirect
Hextelemetry1.4.2indirect
Hextext_diff0.1.0indirect
Hexwebsock0.5.3indirect
Hexwebsock_adapter0.5.9indirect
Hexxema0.17.9indirect
Hexyamerl0.10.0indirect
Hexyaml_elixir2.12.2indirect
Hexymlr5.1.5indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsHex.