Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 08:54 UTC

ash-project / ash_archival

An Ash extension to implement archival (soft deletion) for resources.

ElixirCustom license★ 27 stars⑂ 18 forkssince Jun 2022View on GitHub ↗

ash-project/ash_archival holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (80/100) and lowest on AI Readiness (29/100). It was last updated 15 days ago. 2 contributors account for most of its recent work.

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

80
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 68 is calibrated to 80 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_archival2.0.325,12221254 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
28.8/36Push recencylast push 15 days ago
12.5/36Commit cadence18/52 weeks with commits
14.2/18Commit volume37 commits in the last year
6/10OpenSSF Scorecard: Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year37
human_commit_share
days_since_last_push15
active_weeks_last_year18
How it's scored
27/27Ships releases4 releases published
16.2/36Release recencylatest release 254 days ago
19.8/27Release cadencea release every ~45.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count4
latest_release_tagv2.0.3
releases_from_tagsno
days_since_latest_release254
mean_days_between_releases45.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?

62Moderate · 17% of overall
How it's scored
23/60Stars27 stars
10.3/25Forks18 forks
1.7/15Watchers3 watchers
Inputs used
forks18
stars27
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
58.7/80Monthly downloads25,122 downloads/month across hex
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesash_archival
dependents
ecosystemshex
total_downloads328,785
monthly_downloads25,122
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?

80Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.2/22.5Commit distributiontop contributor authored 46% of commits
13.5/13.5Contributor breadth13 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled13
top_contributor_share0.456
How it's scored
42/42Issue resolution100% of issues closed
22.3/30PR acceptance135/182 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 4/10 approved changesets -- score normalized to 4
Inputs used
merged_prs135
open_issues0
closed_issues12
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs47
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.
How it's scored
25/25Published & resolvable1 package(s) on hex
26/35Publish recencylatest publish 254 days ago
20/20Version history21 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesash_archival
ecosystemshex
any_deprecatedno
min_days_since_publish254

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 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
12/20OpenSSF Scorecard: CI-Tests15 out of 25 merged PRs checked by a CI test -- score normalized to 6
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_archival
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsarchival, ash, soft-delete
has_wikiyes
homepagehttps://hexdocs.pm/ash_archival
docs_sitehttps://hexdocs.pm/ash_archival
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 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.5/2.5CI-Tests15 out of 25 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 4/10 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 6 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
4.5/7.5Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4/5SASTSAST tool is not run on all commits -- score normalized to 8
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.9
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/29 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes14,987
source_files_sampled29
oversized_source_files0

Key facts

27GitHub stars
13contributors
37commits, last 12 months
15days since last push
4releases
2bus factor
0open issues
Hexpackage ecosystems

More detail

OpenSSF Scorecard 5.9 / 10
5.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-07-17 08:54 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests15 out of 25 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 4/10 approved changesets -- score normalized to 4
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
8SASTSAST tool is not run on all commits -- score normalized to 8
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Hexash~> 3.0 and >= 3.0.5mix.exs
All dependencies 54

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

RegistryPackageVersionRelation
Hexash3.29.3direct
Hexash_postgres2.10.0indirect
Hexash_sql0.6.4indirect
Hexbunt1.0.0indirect
Hexcredo1.7.19indirect
Hexcrux0.1.3indirect
Hexdb_connection2.10.1indirect
Hexdecimal3.1.1indirect
Hexdialyxir1.4.7indirect
Hexearmark_parser1.4.45indirect
Hexecto3.14.0indirect
Hexecto_sql3.14.0indirect
Hexerlex0.2.9indirect
Hexets0.9.0indirect
Hexex_ast0.12.5indirect
Hexex_check0.16.0indirect
Hexex_doc0.40.3indirect
Hexfile_system1.1.1indirect
Hexfinch0.23.0indirect
Hexgit_cli0.3.0indirect
Hexgit_ops2.10.0indirect
Hexglob_ex0.1.11indirect
Hexhpax1.0.3indirect
Hexigniter0.8.2indirect
Hexiterex0.1.2indirect
Hexjason1.4.5indirect
Hexlibgraph0.16.0indirect
Hexmakeup1.2.1indirect
Hexmakeup_elixir1.0.1indirect
Hexmakeup_erlang1.1.0indirect
Hexmime2.0.7indirect
Hexmint1.9.0indirect
Hexmix_audit2.1.5indirect
Hexmultigraph0.16.1-mg.4indirect
Hexnimble_options1.1.1indirect
Hexnimble_parsec1.4.2indirect
Hexnimble_pool1.1.0indirect
Hexowl0.13.1indirect
Hexpostgrex0.22.2indirect
Hexreactor1.0.2indirect
Hexreq0.6.2indirect
Hexrewrite1.3.0indirect
Hexsimple_sat0.1.4indirect
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
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.