Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 11:28 UTC

kafkaex / kafka_ex

Kafka client library for Elixir

ElixirMIT★ 612 stars⑂ 165 forkssince Jan 2015View on GitHub ↗

kafkaex/kafka_ex holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (85/100) and lowest on Security (35/100). It was last updated 2 days ago. 2 contributors account 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

kafkaexOrganization
1 follower2 public repossince Aug 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexkafka_ex1.0.324,812382 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
17.3/36Commit cadence25/52 weeks with commits
18/18Commit volume136 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year136
human_commit_share1
days_since_last_push2
active_weeks_last_year25
How it's scored
27/27Ships releases16 releases published
36/36Release recencylatest release 2 days ago
19.8/27Release cadencea release every ~67 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count16
latest_release_tagv1.0.3
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases67
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?

70Good · 17% of overall
How it's scored
45.2/60Stars612 stars
18.5/25Forks165 forks
5.3/15Watchers10 watchers
Inputs used
forks165
stars612
watchers10
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, shields.io
has_pull_request_templateno
How it's scored
58.6/80Monthly downloads24,812 downloads/month across hex
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageskafka_ex
dependents
ecosystemshex
total_downloads32,420,057
monthly_downloads24,812
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?

70Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.9/22.5Commit distributiontop contributor authored 34% of commits
13.5/13.5Contributor breadth66 contributors
10/10OpenSSF Scorecard: Contributorsproject has 15 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled66
top_contributor_share0.336
How it's scored
40.5/42Issue resolution96% of issues closed
26.4/30PR acceptance345/392 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs345
open_issues7
closed_issues191
prs_merged_7d6
prs_decided_7d7
prs_merged_30d6
prs_decided_30d7
issue_closed_ratio0.965
closed_unmerged_prs47
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
2.2/25Owner reach1 followers of kafkaex
15.5/25Track record2 public repos, account ~11 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginkafkaex
public_repos2
account_age_days4,057

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on hex
35/35Publish recencylatest publish 2 days ago
20/20Version history38 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageskafka_ex
ecosystemshex
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
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://hexdocs.pm/kafka_ex
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicskafka, elixir, erlang
has_wikiyes
homepage
docs_sitehttps://hexdocs.pm/kafka_ex
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

35Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.2/2.5CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 15 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.5
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.

65Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
37.9/40Legible commit history71 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.71
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes11,513
How it's scored
12.6/18One-command bootstrapmix.exs (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice9 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesmix.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.09
toolchain_manifestsmix.exs
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeElixir without a type-check config
54.9/55Manageable file sizes1/586 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes60,767
source_files_sampled586
oversized_source_files1

Key facts

612GitHub stars
66contributors
136commits, last 12 months
2days since last push
16releases
2bus factor
7open issues
Hexpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-15: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 612 stars today.

More detail

Star and fork history 612 ★ / 165 ⇿
612Stars
165Forks
11Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Star history is shown as collected on 2026-07-15. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

0125250375500625612160102015-022020-102026-07
Major 1Minor 6Patch 3

Each point covers 11 days.

OpenSSF Scorecard 3.5 / 10
3.5aggregate

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-09-12 11:28 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 15 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Hexno_warnpriv/plts/kafka_ex.pltmix.exs
Hexkayrock~> 1.0mix.exs
Hextelemetry~> 1.2mix.exs
Hexsnappyer~> 1.2mix.exs
Hexlz4b~> 0.0.13mix.exs
Hexezstd~> 1.0mix.exs
Hexaws_credentials~> 1.0mix.exs
Hexaws_signature~> 0.4.2mix.exs
Hexjason~> 1.0mix.exs
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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