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

ash-project / ash_oban

The extension for integrating Ash resources with Oban.

ElixirCustom license★ 40 stars⑂ 33 forkssince Apr 2023View on GitHub ↗
KindLibraryhow this is determined
#ash#background-jobs#jobs#oban

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

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

71
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 63 is calibrated to 71 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_oban0.8.1040,1525994 days ago

Metrics by category

Vitality

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

67Good · 21% of overall

Development activity

51Moderate
How it's scored
18/36Push recency — last push 62 days ago
15.9/36Commit cadence — 23/52 weeks with commits
17.5/18Commit volume — 88 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year88
human_commit_share—
days_since_last_push62
active_weeks_last_year23

Release discipline

90Excellent
How it's scored
27/27Ships releases — 11 releases published
27/36Release recency — latest release 113 days ago
27/27Release cadence — a release every ~25.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tagv0.8.7
releases_from_tagsno
days_since_latest_release113
mean_days_between_releases25.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?

66Good · 17% of overall

Popularity & adoption

41Weak
How it's scored
25.8/60Stars — 40 stars
12.5/25Forks — 33 forks
2.7/15Watchers — 4 watchers
Inputs used
forks33
stars40
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license 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

Ecosystem adoption (downloads)

77Good
How it's scored
61.4/80Monthly downloads — 40,152 downloads/month across hex
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesash_oban
dependents—
ecosystemshex
total_downloads379,208
monthly_downloads40,152
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?

74Good · 23% of overall

Maintainer resilience (bus factor)

38Weak
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.4/22.5Commit distribution — top contributor authored 58% of commits
13.5/13.5Contributor breadth — 32 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled32
top_contributor_share0.581

Issue & PR responsiveness

79Good
How it's scored
42/42Issue resolution — 100% of issues closed
27.1/30PR acceptance — 178/197 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/30 approved changesets -- score normalized to 0
Inputs used
merged_prs178
open_issues0
closed_issues19
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio1
closed_unmerged_prs19
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.

Ownership & stewardship

92Excellent
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
18.6/25Owner reach — 384 followers of ash-project
25/25Track record — 61 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 & resolvable — 1 package(s) on hex
35/35Publish recency — latest publish 94 days ago
20/20Version history — 59 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesash_oban
ecosystemshex
any_deprecatedno
min_days_since_publish94

Engineering Quality

Are baseline engineering and documentation practices in place?

69Good · 19% of overall

Engineering practices

48Weak
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
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 site — https://hexdocs.pm/ash_oban
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsash, background-jobs, jobs, oban
has_wikiyes
homepagehttps://hexdocs.pm/ash_oban
docs_sitehttps://hexdocs.pm/ash_oban
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

41Weak · 16% of overall

Security posture

41Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 2/30 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 15 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.1
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

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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.

Verify loop (build / test / typecheck)

41Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no data
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
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.

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — Elixir without a type-check config
55/55Manageable file sizes — 0/43 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes52,203
source_files_sampled43
oversized_source_files0

Key facts

40GitHub stars
32contributors
88commits, last 12 months
62days since last push
11releases
1bus factor
0open issues
Hexpackage ecosystems

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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 07:40 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities15 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Hexash~> 3.0 and >=3.8.0mix.exs
Hexoban~> 2.20mix.exs
Hexpostgrex~> 0.18mix.exs
All dependencies 53

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

RegistryPackageVersionRelation
Hexash3.24.1direct
Hexoban2.21.1direct
Hexpostgrex0.22.0direct
Hexbunt1.0.0indirect
Hexcredo1.7.18indirect
Hexcrux0.1.2indirect
Hexdb_connection2.9.0indirect
Hexdecimal2.3.0indirect
Hexdialyxir1.4.7indirect
Hexearmark_parser1.4.44indirect
Hexecto3.13.5indirect
Hexecto_sql3.13.5indirect
Hexerlex0.2.8indirect
Hexets0.9.0indirect
Hexex_check0.16.0indirect
Hexex_doc0.40.1indirect
Hexexcoveralls0.18.5indirect
Hexfile_system1.1.1indirect
Hexfinch0.21.0indirect
Hexgit_cli0.3.0indirect
Hexgit_ops2.9.3indirect
Hexglob_ex0.1.11indirect
Hexhpax1.0.3indirect
Hexigniter0.7.9indirect
Hexiterex0.1.2indirect
Hexjason1.4.4indirect
Hexlibgraph0.16.0indirect
Hexmakeup1.2.1indirect
Hexmakeup_elixir1.0.1indirect
Hexmakeup_erlang1.0.3indirect
Hexmime2.0.7indirect
Hexmint1.7.1indirect
Hexmix_audit2.1.5indirect
Hexnimble_options1.1.1indirect
Hexnimble_parsec1.4.2indirect
Hexnimble_pool1.1.0indirect
Hexoban/oban_pro1.6.14indirect
Hexowl0.13.0indirect
Hexreactor1.0.1indirect
Hexreq0.5.17indirect
Hexrewrite1.3.0indirect
Hexsimple_sat0.1.4indirect
Hexsobelow0.14.1indirect
Hexsourceror1.12.0indirect
Hexspark2.6.1indirect
Hexspitfire0.3.10indirect
Hexsplode0.3.0indirect
Hexstream_data1.3.0indirect
Hextelemetry1.4.1indirect
Hextext_diff0.1.0indirect
Hexyamerl0.10.0indirect
Hexyaml_elixir2.12.1indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with ash-project/ash_oban. Read them side by side →

99taskforcesh/bullmqBullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQLExceptional92sidekiq/sidekiqSimple, efficient background processing for RubyExcellent90dereuromark/cakephp-queueQueue plugin for CakePHP - simple, pure PHP and without dependencies.Excellent87durable-workflow/workflowCore package for defining and running durable workflows and activities. Supports long-running persistent workflows, retries, queues, parallel execution, workflow monitoring, dedicated storage connections, and orchestration for microservices, data pipelines, sagas, agentic workflows, and other complex business processes.Excellent84sidequestjs/sidequestRedis-free background jobs for Node.js. Persist jobs in your existing Postgres, MySQL, SQLite, or MongoDB. A distributed, durable BullMQ alternative with a built-in dashboard.Excellent81ultraviolettes/filament-jobs-monitorQueue Monitoring Package for Filament Excellent

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