Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-05 16:52 UTC

domondi1 / inferrail

Self-hosted OpenAI/Anthropic-compatible gateway: give each AI agent run a dollar budget, enforced before the provider, with a payload-free per-run cost record.

PythonApache-2.0★ 0 stars⑂ 0 forkssince Aug 2026View on GitHub ↗
KindNetwork serviceCommand-line toolLibraryWeb interfacehow this is determined

domondi1/inferrail holds a health index of 75 out of 100, placing it in the Good band. It scores highest on AI Readiness (86/100) and lowest on Community & Adoption (40/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

domondi1Personal account
1 follower32 public repossince Sep 2021

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

Package ecosystems

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
6.2/36Commit cadence — 9/52 weeks with commits
18/18Commit volume — 160 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year160
human_commit_share1
days_since_last_push0
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 2 releases published
36/36Release recency — latest release 9 days ago
27/27Release cadence — a release every ~33 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv0.4.4
releases_from_tagsno
days_since_latest_release9
mean_days_between_releases33

Community & Adoption

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

40Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
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_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
49.1/80Monthly downloads — 4,824 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesinferrail
dependents—
ecosystemspypi
total_downloads—
monthly_downloads4,824
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
29.7/30PR acceptance — 108/109 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_prs108
open_issues0
closed_issues2
prs_merged_7d38
prs_decided_7d39
prs_merged_30d59
prs_decided_30d60
issue_closed_ratio1
closed_unmerged_prs1
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
2.2/25Owner reach — 1 followers of domondi1
21.1/25Track record — 32 public repos, account ~5 yr old
Inputs used
followers1
owner_typeUser
is_verified—
owner_logindomondi1
public_repos32
account_age_days1,832
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
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_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://tryinferrail.com/
10/10Repository description
10/10Topics — 12 topics
0/10Wiki
Inputs used
topicsai-gateway, llm-gateway, llm-proxy, llmops, mcp, openai-compatible, ai-cost, agent-budget, ai-agents, cost-control, llm-budget, llm-cost
has_wikino
homepagehttps://tryinferrail.com/
docs_sitehttps://tryinferrail.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfiles — package-lock.json
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json
manifestsapp/package.json, pyproject.toml
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno

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.

86Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,344
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — app/tsconfig.json, src/inferrail/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 27 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
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsapp/tsconfig.json, src/inferrail/py.typed
agent_commit_share0.27
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (app/tsconfig.json, src/inferrail/py.typed)
54.4/55Manageable file sizes — 3/266 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes103,724
source_files_sampled266
oversized_source_files3
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — openapi.json
20/20MCP server
40/40Runnable examples — examples, recipes
Inputs used
example_dirsexamples, recipes
has_mcp_signalyes
api_schema_filesopenapi.json
interfaces_expected_ofnetwork-service

Key facts

0GitHub stars
1contributors
160commits, last 12 months
0days since last push
2releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:inferrail@0.4.14; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Direct dependencies 8
RegistryPackageVersion constraintManifest
npmreact^18.3.1app/package.json
npmreact-dom^18.3.1app/package.json
PyPIfastapi>=0.110pyproject.toml
PyPIuvicorn>=0.27pyproject.toml
PyPIhttpx>=0.27pyproject.toml
PyPIpydantic>=2.5pyproject.toml
PyPIpyyaml>=6.0pyproject.toml
PyPIpython-dotenv>=1.0pyproject.toml
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 — PyPI.