Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 04:38 UTC

python-injector / injector

Python dependency injection framework, inspired by Guice

PythonBSD-3-Clause★ 1,536 stars⑂ 95 forkssince Nov 2010View on GitHub ↗

python-injector/injector holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Engineering Quality (71/100) and lowest on AI Readiness (54/100). It was last updated 32 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

python-injectorOrganization
4 followers2 public repossince Dec 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIinjectorpoints to another repo — not scored0.24.0-57215 days agodependency-injectiondidependency-injection-frameworkinversion-of-controliocinversion-of-control-container

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
18/36Push recencylast push 32 days ago
9.7/36Commit cadence14/52 weeks with commits
17.3/18Commit volume83 commits in the last year
8/10OpenSSF Scorecard: Maintained9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year83
human_commit_share0.82
days_since_last_push32
active_weeks_last_year14
How it's scored
27/27Ships releases2 releases published
16.2/36Release recencylatest release 215 days ago
27/27Release cadencea release every ~41.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tag0.24.0
releases_from_tagsno
days_since_latest_release215
mean_days_between_releases41.7
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?

63Moderate · 17% of overall
How it's scored
51.7/60Stars1,536 stars
16.4/25Forks95 forks
6/15Watchers13 watchers
Inputs used
forks95
stars1,536
watchers13
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.2/22.5Commit distributiontop contributor authored 55% of commits
13.5/13.5Contributor breadth29 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled29
top_contributor_share0.547
How it's scored
29.7/42Issue resolution71% of issues closed
24.8/30PR acceptance132/160 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/6 approved changesets -- score normalized to 0
Inputs used
merged_prs132
open_issues45
closed_issues109
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.708
closed_unmerged_prs28
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 backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
5/25Owner reach4 followers of python-injector
10.9/25Track record2 public repos, account ~3 yr old
Inputs used
followers4
owner_typeOrganization
is_verified
owner_loginpython-injector
public_repos2
account_age_days1,349
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsdependency-injection, dependency-injection-framework, di, python, injector
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?

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/6 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 7 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
6/7.5Maintained9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
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
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages41
unassessed_packages0
affected_by_severityhigh 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 41 resolved dependencies against OSV. 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
38.4/40Legible commit history59 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.72
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkinginjector/py.typed, mypy.ini
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance18 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configno
typecheck_configsinjector/py.typed, mypy.ini
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.18
How it's scored
27/45Type-checkable codePython with type-check config (injector/py.typed, mypy.ini)
44/55Manageable file sizes1/5 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes62,652
source_files_sampled5
oversized_source_files1

Key facts

1,536GitHub stars
29contributors
83commits, last 12 months
32days since last push
2releases
1bus factor
45open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi package 'injector' points at a different repository (https://github.com/alecthomas/injector); excluded from ecosystem scoring

More detail

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

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.

0204060801009332012-072019-062026-05
Major 0Minor 2Patch 0

Each point covers 13 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-08-13 04:38 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
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/6 approved changesets -- score normalized to 0
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
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
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 41

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

RegistryPackageVersionRelation
PyPIalabaster0.7.13indirect
PyPIbabel2.14.0indirect
PyPIbeautifulsoup44.12.3indirect
PyPIblack26.3.1indirect
PyPIbuild1.0.3indirect
PyPIcertifi2024.7.4indirect
PyPIcharset-normalizer3.3.2indirect
PyPIcheck-manifest0.49indirect
PyPIclick8.1.7indirect
PyPIcoverage7.3.2indirect
PyPIdocutils0.20.1indirect
PyPIfuro2024.5.6indirect
PyPIidna3.15indirect
PyPIimagesize1.4.1indirect
PyPIiniconfig2.0.0indirect
PyPIjinja23.1.6indirect
PyPImarkupsafe2.1.3indirect
PyPImypy1.7.1indirect
PyPImypy-extensions1.0.0indirect
PyPIpackaging25.0indirect
PyPIpathspec1.0.4indirect
PyPIplatformdirs4.1.0indirect
PyPIpluggy1.6.0indirect
PyPIpygments2.20.0indirect
PyPIpyproject-hooks1.0.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov4.1.0indirect
PyPIpytokens0.4.1indirect
PyPIrequests2.33.0indirect
PyPIsnowballstemmer2.2.0indirect
PyPIsoupsieve2.8.4indirect
PyPIsphinx7.1.2indirect
PyPIsphinx-basic-ng1.0.0b2indirect
PyPIsphinxcontrib-applehelp1.0.4indirect
PyPIsphinxcontrib-devhelp1.0.2indirect
PyPIsphinxcontrib-htmlhelp2.0.1indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.3indirect
PyPIsphinxcontrib-serializinghtml1.1.5indirect
PyPItyping-extensions4.15.0indirect
PyPIurllib32.7.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 41 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
click8.1.7indirecthigh18.3.3

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.