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

hauleth / phoenix_bakery

Better compression for your Phoenix assets

ElixirMIT★ 67 stars⑂ 6 forkssince Oct 2021View on GitHub ↗
KindLibraryNetwork servicehow this is determined

hauleth/phoenix_bakery holds a health index of 39 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (56/100) and lowest on Security (17/100). It was last updated 51 days ago. A single contributor accounts for most of its recent work.

39
overall / 100
Weak

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.

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

Ownership

Łukasz Jan NiemierPersonal account
346 followers186 public repossince May 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexphoenix_bakery1.0.04,0624319 days ago

Metrics by category

Vitality

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

37Weak · 21% of overall
How it's scored
18/36Push recencylast push 51 days ago
1.4/36Commit cadence2/52 weeks with commits
7/18Commit volume5 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year5
human_commit_share
days_since_last_push51
active_weeks_last_year2
How it's scored
27/27Ships releases4 releases published
16.2/36Release recencylatest release 319 days ago
5.4/27Release cadencea release every ~475 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count4
latest_release_tagv1.0.0
releases_from_tagsno
days_since_latest_release319
mean_days_between_releases475
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?

46Weak · 17% of overall
How it's scored
29.5/60Stars67 stars
5.8/25Forks6 forks
0/15Watchers1 watchers
Inputs used
forks6
stars67
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
48.1/80Monthly downloads4,062 downloads/month across hex
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesphoenix_bakery
dependents
ecosystemshex
total_downloads111,455
monthly_downloads4,062
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5/22.5Commit distributiontop contributor authored 78% of commits
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.778
How it's scored
0/42Issue resolutionno issues or no data
21.8/30PR acceptance8/11 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 5/27 approved changesets -- score normalized to 1
Inputs used
merged_prs8
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs3
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
18.3/25Owner reach346 followers of hauleth
25/25Track record186 public repos, account ~16 yr old
Inputs used
followers346
owner_typeUser
is_verified
owner_loginhauleth
public_repos186
account_age_days5,891
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 319 days ago
12/20Version history4 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesphoenix_bakery
ecosystemshex
any_deprecatedno
min_days_since_publish319

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 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
4/20OpenSSF Scorecard: CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsphoenix, phoenix-framework, assets, compression, hacktoberfest
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

17Critical · 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
0.5/2.5CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 5/27 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflowdangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate1.7
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.

27At 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
0/8Automated maintenanceno data
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_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeElixir without a type-check config
46.5/55Manageable file sizes2/13 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes155,311
source_files_sampled13
oversized_source_files2

Key facts

67GitHub stars
6contributors
5commits, last 12 months
51days since last push
4releases
1bus factor
0open issues
Hexpackage ecosystems

More detail

OpenSSF Scorecard 1.7 / 10
1.7aggregate

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 09:14 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
2CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/27 approved changesets -- score normalized to 1
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Hexphoenix~> 1.6mix.exs
Hexbrotli~> 0.3.0mix.exs
Hexezstd~> 1.0mix.exs
Hexokmix.exs
Hexokmix.exs
Hexokmix.exs
Hexokmix.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
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.