Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 14:29 UTC

BeamLabEU / phoenix_kit

PhoenixKit - The Elixir Phoenix Boilerplate Starter Kit for writing your SaaS, social networks, ERP systems, marketplaces, internal tools, AI-powered apps, community platforms, and more.

ElixirMIT★ 36 stars⑂ 9 forkssince Aug 2025View on GitHub ↗
KindLibraryNetwork servicehow this is determined

BeamLabEU/phoenix_kit holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (100/100) and lowest on Security (1/100). It was last updated today. 2 contributors account 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

BEAM LabOrganization
1 follower49 public repossince Jul 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexphoenix_kit2.22.98,3003120 days ago

Metrics by category

Vitality

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

100Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 5,449 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year5,449
human_commit_share1
days_since_last_push0
active_weeks_last_year52

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 68 releases published
36/36Release recency — latest release 18 days ago
27/27Release cadence — a release every ~13.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count68
latest_release_tagv2.13.5
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases13.5

Community & Adoption

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

54Moderate · 17% of overall
How it's scored
25/60Stars — 36 stars
7.5/25Forks — 9 forks
0/15Watchers — 0 watchers
Inputs used
forks9
stars36
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
52.3/80Monthly downloads — 8,300 downloads/month across hex
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesphoenix_kit
dependents—
ecosystemshex
total_downloads36,456
monthly_downloads8,300
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 factor — 2 contributor(s) cover half of all commits
15/22.5Commit distribution — top contributor authored 33% of commits
8.1/13.5Contributor breadth — 6 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor2
contributors_sampled6
top_contributor_share0.334
How it's scored
36.3/42Issue resolution — 86% of issues closed
28.1/30PR acceptance — 725/775 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs725
open_issues3
closed_issues19
prs_merged_7d18
prs_decided_7d18
prs_merged_30d59
prs_decided_30d60
issue_closed_ratio0.864
closed_unmerged_prs50
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 backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of BeamLabEU
14.7/25Track record — 49 public repos, account ~1 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginBeamLabEU
public_repos49
account_age_days426

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on hex
35/35Publish recency — latest publish 0 days ago
20/20Version history — 312 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesphoenix_kit
ecosystemshex
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
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 — no data
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://phoenixkit.eu
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicselixir, phoenix-framework, phoenix-elixir, saas-boilerplate, phoenix-kit
has_wikiyes
homepagehttps://phoenixkit.eu
docs_sitehttps://phoenixkit.eu
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesmix.lock
manifestsmix.exs
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

64Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 96 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.96
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes38,009
How it's scored
12.6/18One-command bootstrap — mix.exs (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 55 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesmix.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.55
toolchain_manifestsmix.exs
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Elixir without a type-check config
53.9/55Manageable file sizes — 20/985 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes2,795,285
source_files_sampled985
oversized_source_files20
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

36GitHub stars
6contributors
5,449commits, last 12 months
0days since last push
68releases
2bus factor
3open issues
Hexpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/BeamLabEU/phoenix_kit: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-09T14:29:08Z. Please include `D3C8:1E2E9E:186AA5F:17A3438:6AA16D31` when reporting this issue.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
61Releases

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.

0246810922025-082026-022026-08
Major 0Minor 6Patch 55
Direct dependencies 49
RegistryPackageVersion constraintManifest
Hexno_warnpriv/plts/dialyzer.pltmix.exs
Hexecto_sql~> 3.10mix.exs
Hexpostgrex~> 0.22mix.exs
Hexphoenix~> 1.8.1mix.exs
Hexphoenix_ecto~> 4.6mix.exs
Hexphoenix_html~> 4.0mix.exs
Hexphoenix_live_view~> 1.1mix.exs
Hexgettext~> 1.0mix.exs
Hexbandit~> 1.0mix.exs
Hexbcrypt_elixir~> 3.0mix.exs
Hexswoosh~> 1.20mix.exs
Hexgen_smtp~> 1.2mix.exs
Hexoauth2~> 2.0mix.exs
Hexueberauth~> 0.10mix.exs
Hexueberauth_google~> 0.12mix.exs
Hexueberauth_github~> 0.8mix.exs
Hexueberauth_facebook~> 0.10mix.exs
Hexhackney~> 4.0mix.exs
Hexleaf~> 0.4.1 or ~> 0.5 or ~> 0.6mix.exs
Hexmdex~> 0.13mix.exs
Hexrustler>= 0.0.0mix.exs
Hexfresco~> 0.10mix.exs
Hextessera~> 0.3mix.exs
Hexetcher~> 0.9mix.exs
Hexkeyfob~> 0.1.1mix.exs
Hexaws_regions~> 0.1.0mix.exs
Hexbackblaze_regions~> 0.1.0mix.exs
Hextigris_regions~> 0.1.0mix.exs
Hextz~> 0.28mix.exs
Hexjason~> 1.4mix.exs
Hexyaml_elixir~> 2.9mix.exs
Hexnimble_csv~> 1.2mix.exs
Hexuuidv7~> 1.0mix.exs
Hexoban~> 2.20mix.exs
Hexhammer~> 7.1mix.exs
Hexwebsockex~> 0.5.1mix.exs
Hexsweet_xml~> 0.7mix.exs
Hexex_aws~> 2.4mix.exs
Hexbeamlab_ex_aws_sqs~> 5.0mix.exs
Hexex_aws_sqs~> 5.0mix.exs
Hexex_aws_sns~> 2.3mix.exs
Hexex_aws_sts~> 2.3mix.exs
Hexex_aws_s3~> 2.4mix.exs
Hexex_aws_ec2~> 2.0mix.exs
Hexsaxy~> 1.5mix.exs
Hexfinch~> 0.18mix.exs
Hexreq~> 0.5mix.exs
Hexigniter~> 0.7mix.exs
Hexbeamlab_countries~> 1.0mix.exs
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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