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

erlef / mix_sbom

Mix task to generate a Software Bill-of-Materials (SBoM) in CycloneDX format

ElixirCustom license★ 47 stars⑂ 21 forkssince Oct 2019View on GitHub ↗

erlef/mix_sbom holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (82/100) and lowest on AI Readiness (35/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

193 followers51 public repossince Feb 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexsbom0.10.029,5551498 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
22.2/36Commit cadence32/52 weeks with commits
18/18Commit volume135 commits in the last year
10/10OpenSSF Scorecard: Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year135
human_commit_share
days_since_last_push3
active_weeks_last_year32
How it's scored
27/27Ships releases14 releases published
27/36Release recencylatest release 98 days ago
12.6/27Release cadencea release every ~150.5 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count14
latest_release_tagv0.10.0
releases_from_tagsno
days_since_latest_release98
mean_days_between_releases150.5

Community & Adoption

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

62Moderate · 17% of overall
How it's scored
27/60Stars47 stars
10.8/25Forks21 forks
1.7/15Watchers3 watchers
Inputs used
forks21
stars47
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
59.6/80Monthly downloads29,555 downloads/month across hex
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessbom
dependents
ecosystemshex
total_downloads394,997
monthly_downloads29,555
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?

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.4/22.5Commit distributiontop contributor authored 54% of commits
13.5/13.5Contributor breadth11 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.539
How it's scored
25.8/42Issue resolution62% of issues closed
27.3/30PR acceptance100/110 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 2/7 approved changesets -- score normalized to 2
Inputs used
merged_prs100
open_issues5
closed_issues8
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.615
closed_unmerged_prs10
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
16.4/25Owner reach193 followers of erlef
24.5/25Track record51 public repos, account ~7 yr old
Inputs used
followers193
owner_typeOrganization
is_verified
owner_loginerlef
public_repos51
account_age_days2,710
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 98 days ago
20/20Version history14 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessbom
ecosystemshex
any_deprecatedno
min_days_since_publish98

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows14 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests22 out of 25 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://hex.pm/packages/sbom
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicselixir, mix, sbom, security-wg, cyclonedx
has_wikino
homepagehttps://hex.pm/packages/sbom
docs_sitehttps://hex.pm/packages/sbom
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

79Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2/2.5CI-Tests22 out of 25 merged PRs checked by a CI test -- score normalized to 8
1.2/2.5CII-Best-Practicesbadge detected: Passing
1.5/7.5Code-ReviewFound 2/7 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 11 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
6/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.9
Excluded from scoring (no data or not applicable): Packaging. 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.

35Weak · 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
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
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/587 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes19,001
source_files_sampled587
oversized_source_files0

Key facts

47GitHub stars
11contributors
135commits, last 12 months
3days since last push
14releases
1bus factor
5open issues
Hexpackage ecosystems

More detail

OpenSSF Scorecard 7.9 / 10
7.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 07:47 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
8CI-Tests22 out of 25 merged PRs checked by a CI test -- score normalized to 8
5CII-Best-Practicesbadge detected: Passing
2Code-ReviewFound 2/7 approved changesets -- score normalized to 2
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
9Licenselicense file detected
10Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Hexburrito~> 1.0mix.exs
Hexhex_core~> 0.18.0mix.exs
Hexjason~> 1.4mix.exs
Hexoptimus~> 0.6.1mix.exs
Hexprotobuf~> 0.17.0mix.exs
Hexpurl~> 0.3.0mix.exs
Hexhex~> 2.3mix.exs
All dependencies 68

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

RegistryPackageVersionRelation
Hexhex_core0.18.0direct
Hexjason1.1.2direct
Hexjason1.4.0direct
Hexjason1.4.4direct
Hexjason1.4.5direct
Hexoptimus0.6.1direct
Hexprotobuf0.17.0direct
Hexpurl0.3.0direct
Hex0ban/oban_pro1.5.4indirect
Hexbunt0.2.1indirect
Hexbunt1.0.0indirect
Hexcertifi2.5.1indirect
Hexcircuits_gpio~> 0.4indirect
Hexcomplex_dep~> 1.0indirect
Hexcredo1.7.0indirect
Hexcredo1.7.12indirect
Hexcredo1.7.19indirect
Hexcredo~> 1.7indirect
Hexdb_connection2.7.0indirect
Hexdecimal2.3.0indirect
Hexdialyxir1.4.7indirect
Hexdialyxir~> 1.0indirect
Hexdoctest_formatter0.4.1indirect
Hexearmark1.4.2indirect
Hexearmark_parser1.4.45indirect
Hexecto3.12.5indirect
Hexecto_sql3.12.1indirect
Hexerlex0.2.9indirect
Hexex_doc0.21.2indirect
Hexex_doc0.40.3indirect
Hexex_doc~> 0.21.2indirect
Hexexcoveralls0.18.5indirect
Hexexcoveralls~> 0.10indirect
Hexfile_system0.2.10indirect
Hexfile_system1.1.0indirect
Hexfile_system1.1.1indirect
Hexhackney1.15.2indirect
Hexhackney~> 1.15indirect
Hexidna6.0.0indirect
Hexmakeup1.0.0indirect
Hexmakeup1.2.1indirect
Hexmakeup_elixir0.14.0indirect
Hexmakeup_elixir1.0.1indirect
Hexmakeup_erlang1.1.0indirect
Hexmeck0.8.13indirect
Hexmeck~> 0.8.13indirect
Hexmetrics1.0.1indirect
Hexmime2.0.6indirect
Hexmimerl1.2.0indirect
Hexmix_test_watch~> 1.0indirect
Hexnerves~> 1.6indirect
Hexnimble_parsec0.5.1indirect
Hexnimble_parsec1.4.2indirect
Hexnumber1.0.5indirect
Hexoban2.19.4indirect
Hexoptional_dep~> 1.0indirect
Hexoptional_dev_dep~> 2.0indirect
Hexparse_trans3.3.0indirect
Hexphoenix~> 1.5indirect
Hexphoenix_live_dashboard~> 0.4indirect
Hexssl_verify_fun1.1.5indirect
Hexstream_data1.3.0indirect
Hexstyler1.11.0indirect
Hexsweet_xml0.6.6indirect
Hexsweet_xml~> 0.6.6indirect
Hextelemetry1.3.0indirect
Hextelemetry1.4.1indirect
Hexunicode_util_compat0.4.1indirect
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.