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

infrahouse / infrahouse-toolkit

InfraHouse Toolkit.

PythonCustom license★ 75 stars⑂ 2 forkssince Feb 2023View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

infrahouse/infrahouse-toolkit holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Security (40/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

InfraHouseOrganization · verified domain
13 followers71 public repossince Jan 2023InfraHouse Inc.

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIinfrahouse-toolkit2.66.09,5951410 days agoinfrahouse-toolkit

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
15.9/36Commit cadence — 23/52 weeks with commits
16.6/18Commit volume — 70 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year70
human_commit_share0.66
days_since_last_push0
active_weeks_last_year23

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 22 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~22 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count22
latest_release_tagv2.66.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases22

Community & Adoption

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

54Moderate · 17% of overall
How it's scored
30.3/60Stars — 75 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars75
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesapp.codacy.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
53.1/80Monthly downloads — 9,595 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesinfrahouse-toolkit
dependents—
ecosystemspypi
total_downloads—
monthly_downloads9,595
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.6/22.5Commit distribution — top contributor authored 97% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.973
How it's scored
10.2/42Issue resolution — 24% of issues closed
26.8/30PR acceptance — 192/215 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_prs192
open_issues31
closed_issues10
prs_merged_7d1
prs_decided_7d1
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0.244
closed_unmerged_prs23
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
20/20Verified domain
8.2/25Owner reach — 13 followers of infrahouse
20.4/25Track record — 71 public repos, account ~3 yr old
Inputs used
followers13
owner_typeOrganization
is_verifiedyes
owner_logininfrahouse
public_repos71
account_age_days1,360

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 — 141 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesinfrahouse-toolkit
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, pyproject.toml ([tool.black], [tool.isort]), tox.ini
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicsinfrahouse, python
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfiles — Gemfile.lock
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesGemfile.lock
manifestsomnibus-infrahouse-toolkit/Gemfile, pyproject.toml, requirements.txt, requirements_dev.txt, setup.cfg, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories3
affected_packages3
assessed_packages144
unassessed_packages39
affected_by_severityhigh 1, moderate 1, low 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 144 resolved dependencies against OSV. 39 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.aws.amazon.com/llms.txt)
33.1/40Legible commit history — 41 of 66 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.aws.amazon.com/llms.txt
legible_history_share0.621
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,349
How it's scored
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — .pylintrc, pyproject.toml ([tool.black], [tool.isort]), tox.ini
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 17 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 12 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.17
toolchain_manifests—
dependency_bot_commit_share0.12
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/257 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes48,037
source_files_sampled257
oversized_source_files0

Key facts

75GitHub stars
3contributors
70commits, last 12 months
0days since last push
22releases
1bus factor
31open issues
PyPI, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:infrahouse-toolkit@2.66.0; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
6Releases

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.

111222212024-062024-072024-08
Major 0Minor 4Patch 2
Direct dependencies 1
RegistryPackageVersion constraintManifest
RubyGemsomnibus~> 9.0omnibus-infrahouse-toolkit/Gemfile
All dependencies 183

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

RegistryPackageVersionRelation
RubyGemsomnibus9.0.24direct
PyPIblack—indirect
PyPIboto3—indirect
PyPIbotocore—indirect
PyPIbuild—indirect
PyPIbump2version—indirect
PyPIcached-property—indirect
PyPIcertbot—indirect
PyPIcertbot-dns-route53—indirect
PyPIclick—indirect
PyPIcryptography—indirect
PyPIdiskcache—indirect
PyPIec2-metadata—indirect
PyPIelastic-transport—indirect
PyPIelasticsearch—indirect
PyPIgitpython—indirect
PyPIgoogle-api-python-client—indirect
PyPIgoogle-auth—indirect
PyPIidna—indirect
PyPIinfrahouse-core—indirect
PyPIisort—indirect
PyPImdformat—indirect
PyPImdformat-gfm—indirect
PyPIpipdeptree—indirect
PyPIpygithub—indirect
PyPIpyhcl—indirect
PyPIpyjwt—indirect
PyPIpylint—indirect
PyPIpymysql—indirect
PyPIpytest—indirect
PyPIpytest-cov—indirect
PyPIpytest-timeout—indirect
PyPIrequests—indirect
PyPIsemgrep—indirect
PyPIsphinx—indirect
PyPItabulate—indirect
PyPItox—indirect
PyPItwine—indirect
PyPIwcwidth—indirect
PyPIyamllint—indirect
RubyGemsaddressable2.9.0indirect
RubyGemsast2.4.3indirect
RubyGemsaws-eventstream1.4.0indirect
RubyGemsaws-partitions1.1265.0indirect
RubyGemsaws-sdk-core3.252.0indirect
RubyGemsaws-sdk-kms1.129.0indirect
RubyGemsaws-sdk-s31.116.0indirect
RubyGemsaws-sdk-secretsmanager1.133.0indirect
RubyGemsaws-sigv41.12.1indirect
RubyGemsbase640.3.0indirect
RubyGemsbcrypt_pbkdf1.1.2indirect
RubyGemsberkshelf8.0.9indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbuilder3.3.0indirect
RubyGemschef17.10.163indirect
RubyGemschef-cleanroom1.0.5indirect
RubyGemschef-config17.10.163indirect
RubyGemschef-telemetry1.1.1indirect
RubyGemschef-utils17.10.163indirect
RubyGemschef-vault4.1.11indirect
RubyGemschef-zero15.1.11indirect
RubyGemscitrus3.0.2indirect
RubyGemscleanroom1.0.0indirect
RubyGemscoderay1.1.3indirect
RubyGemsconcurrent-ruby1.3.7indirect
RubyGemscontracts0.16.1indirect
RubyGemscookstyle8.7.6indirect
RubyGemscorefoundation0.3.13indirect
RubyGemsdiff-lcs1.5.1indirect
RubyGemsed255191.4.0indirect
RubyGemserubi1.13.1indirect
RubyGemserubis2.7.0indirect
RubyGemsfaraday2.14.3indirect
RubyGemsfaraday-follow_redirects0.5.0indirect
RubyGemsfaraday-net_http3.4.4indirect
RubyGemsffi1.15.5indirect
RubyGemsffi-libarchive1.1.14indirect
RubyGemsffi-yajl2.6.0indirect
RubyGemsfuzzyurl0.9.0indirect
RubyGemsgssapi1.3.1indirect
RubyGemsgyoku1.4.0indirect
RubyGemshashie5.1.0indirect
RubyGemshttpclient2.9.0indirect
RubyGemsiniparse1.5.0indirect
RubyGemsinspec-core5.22.55indirect
RubyGemsio-console0.8.2indirect
RubyGemsiostruct0.7.0indirect
RubyGemsipaddress0.8.3indirect
RubyGemsjmespath1.6.2indirect
RubyGemsjson2.20.0indirect
RubyGemskitchen-vagrant2.2.1indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslibyajl22.1.0indirect
RubyGemslicense-acceptance2.1.13indirect
RubyGemslicense_scout1.4.2indirect
RubyGemslint_roller1.1.0indirect
RubyGemslittle-plugger1.1.4indirect
RubyGemslogger1.7.0indirect
RubyGemslogging2.4.0indirect
RubyGemsmethod_source1.1.0indirect
RubyGemsminitar0.12.1indirect
RubyGemsmixlib-archive1.1.7indirect
RubyGemsmixlib-authentication3.0.10indirect
RubyGemsmixlib-cli2.1.8indirect
RubyGemsmixlib-config3.0.27indirect
RubyGemsmixlib-install3.17.0indirect
RubyGemsmixlib-log3.1.2.1indirect
RubyGemsmixlib-shellout3.3.9indirect
RubyGemsmixlib-versioning1.2.12indirect
RubyGemsmolinillo0.8.0indirect
RubyGemsmulti_json1.19.1indirect
RubyGemsmultipart-post2.4.1indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsnet-http0.9.1indirect
RubyGemsnet-scp4.1.0indirect
RubyGemsnet-sftp4.0.0indirect
RubyGemsnet-ssh7.3.3indirect
RubyGemsnet-ssh-gateway2.0.0indirect
RubyGemsnori2.7.1indirect
RubyGemsoctokit4.25.1indirect
RubyGemsohai17.9.4indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.28.0indirect
RubyGemsparser3.3.11.1indirect
RubyGemsparslet2.0.0indirect
RubyGemspastel0.8.0indirect
RubyGemspedump0.7.6indirect
RubyGemsplist3.7.2indirect
RubyGemsprism1.9.0indirect
RubyGemsproxifier21.1.0indirect
RubyGemspry0.16.0indirect
RubyGemspublic_suffix6.0.2indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.6indirect
RubyGemsrackup2.3.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsreline0.6.3indirect
RubyGemsretryable3.0.5indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspec3.12.0indirect
RubyGemsrspec-core3.12.3indirect
RubyGemsrspec-expectations3.12.4indirect
RubyGemsrspec-its1.3.1indirect
RubyGemsrspec-mocks3.12.7indirect
RubyGemsrspec-support3.12.2indirect
RubyGemsrubocop1.86.1indirect
RubyGemsrubocop-ast1.49.1indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsrubyntlm0.6.5indirect
RubyGemsrubyzip2.4.1indirect
RubyGemssawyer0.9.3indirect
RubyGemssemverse3.0.2indirect
RubyGemssolve4.0.4indirect
RubyGemssslshake1.3.1indirect
RubyGemsstrings0.2.1indirect
RubyGemsstrings-ansi0.2.0indirect
RubyGemssyslog-logger1.6.8indirect
RubyGemstest-kitchen3.5.1indirect
RubyGemsthor1.2.2indirect
RubyGemstoml-rb2.2.0indirect
RubyGemstomlrb1.3.0indirect
RubyGemstrain-core3.12.3indirect
RubyGemstrain-winrm0.2.13indirect
RubyGemstty-box0.7.0indirect
RubyGemstty-color0.6.0indirect
RubyGemstty-cursor0.7.1indirect
RubyGemstty-prompt0.23.1indirect
RubyGemstty-reader0.9.0indirect
RubyGemstty-screen0.8.2indirect
RubyGemstty-table0.12.0indirect
RubyGemsunicode-display_width2.6.0indirect
RubyGemsunicode_utils1.4.0indirect
RubyGemsuri1.1.1indirect
RubyGemsuuidtools2.2.0indirect
RubyGemsvault0.18.2indirect
RubyGemswebrick1.9.2indirect
RubyGemswinrm2.3.9indirect
RubyGemswinrm-elevated1.2.3indirect
RubyGemswinrm-fs1.3.5indirect
RubyGemswisper2.0.1indirect
RubyGemswmi-lite1.0.7indirect
RubyGemszhexdump0.3.0indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 144 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 0 are direct. 39 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
rubyzip2.4.1indirecthigh13.4.0
aws-sdk-s31.116.0indirectmoderate11.208.0
json2.20.0indirectlow12.21.2

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.