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

tallarium / reverse_proxy_plug

🔛 an Elixir reverse proxy Plug with HTTP/2, chunked transfer and path proxying support

ElixirMIT★ 316 stars⑂ 71 forkssince Aug 2018View on GitHub ↗
KindLibraryNetwork servicehow this is determined

tallarium/reverse_proxy_plug holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (75/100) and lowest on AI Readiness (32/100). It was last updated 7 days ago. 2 contributors account for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

TallariumOrganization
5 followers59 public repossince Feb 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexreverse_proxy_plug3.0.448,90328144 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
36/36Push recencylast push 7 days ago
6.2/36Commit cadence9/52 weeks with commits
10.8/18Commit volume15 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year15
human_commit_share
days_since_last_push7
active_weeks_last_year9
How it's scored
27/27Ships releases27 releases published
27/36Release recencylatest release 144 days ago
19.8/27Release cadencea release every ~116.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count27
latest_release_tagv3.0.4
releases_from_tagsno
days_since_latest_release144
mean_days_between_releases116.9
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?

61Moderate · 17% of overall
How it's scored
40.5/60Stars316 stars
15.4/25Forks71 forks
4.7/15Watchers8 watchers
Inputs used
forks71
stars316
watchers8
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
62.5/80Monthly downloads48,903 downloads/month across hex
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesreverse_proxy_plug
dependents
ecosystemshex
total_downloads1,242,406
monthly_downloads48,903
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12/22.5Commit distributiontop contributor authored 47% of commits
13.5/13.5Contributor breadth25 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled25
top_contributor_share0.467
How it's scored
35.6/42Issue resolution85% of issues closed
22.5/30PR acceptance143/191 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/14 approved changesets -- score normalized to 1
Inputs used
merged_prs143
open_issues9
closed_issues50
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.847
closed_unmerged_prs48
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
5.6/25Owner reach5 followers of tallarium
24.9/25Track record59 public repos, account ~11 yr old
Inputs used
followers5
owner_typeOrganization
is_verified
owner_logintallarium
public_repos59
account_age_days4,180
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 144 days ago
20/20Version history28 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesreverse_proxy_plug
ecosystemshex
any_deprecatedno
min_days_since_publish144

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests7 out of 14 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicselixir, plug, http, proxy, reverse-proxy, reverse-proxy-server, http-server, chunked-transmission
has_wikino
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?

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.2/2.5CI-Tests7 out of 14 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 2/14 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 4 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
0/7.5Vulnerabilities32 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

32At 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
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
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, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeElixir without a type-check config
55/55Manageable file sizes0/21 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes26,153
source_files_sampled21
oversized_source_files0

Key facts

316GitHub stars
25contributors
15commits, last 12 months
7days since last push
27releases
2bus factor
9open issues
Hexpackage ecosystems

More detail

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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 08:13 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
5CI-Tests7 out of 14 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/14 approved changesets -- score normalized to 1
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities32 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Hexreq~> 0.3.0 or ~> 0.4.0 or ~> 0.5.0mix.exs
Hexfinch~> 0.18mix.exs
Hexplug~> 1.6mix.exs
Hexhttpoison~> 1.4 or ~> 2.0 or ~> 3.0mix.exs
Hextesla~> 1.4mix.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.