Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 10:26 UTC

avaje / avaje-inject

Dependency injection via source code generation

JavaApache-2.0★ 321 stars⑂ 29 forkssince Nov 2018View on GitHub ↗
KindPluginLibraryhow this is determined

avaje/avaje-inject holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (53/100). It was last updated today. A single contributor accounts for most of its recent work.

87
overall / 100
Excellent

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.

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

Ownership

avajeOrganization
124 followers51 public repossince Jun 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenio.avaje:avaje-inject12.7-javax-27431 days ago
Mavenio.avaje:avaje-inject-aop12.7-javax-10631 days ago
Mavenio.avaje:avaje-inject-test12.7-javax-25831 days ago
Mavenio.avaje:avaje-inject-events12.7-javax-10631 days ago
Mavenio.avaje:avaje-inject-generator12.7-javax-27331 days ago
Mavenio.avaje:avaje-inject-maven-plugin12.7-javax-10831 days ago

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 232 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year232
human_commit_share0.45
days_since_last_push0
active_weeks_last_year51
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 31 days ago
19.8/27Release cadence — a release every ~56.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag12.7
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases56.2
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?

53Moderate · 17% of overall
How it's scored
40.6/60Stars — 321 stars
12.1/25Forks — 29 forks
3.3/15Watchers — 5 watchers
Inputs used
forks29
stars321
watchers5
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)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.6/22.5Commit distribution — top contributor authored 66% of commits
13.5/13.5Contributor breadth — 14 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.661
How it's scored
41.5/42Issue resolution — 99% of issues closed
27.1/30PR acceptance — 681/755 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 5/10 approved changesets -- score normalized to 5
Inputs used
merged_prs681
open_issues4
closed_issues320
prs_merged_7d2
prs_decided_7d3
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.988
closed_unmerged_prs74
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
0/20Verified domain
15.1/25Owner reach — 124 followers of avaje
24.5/25Track record — 51 public repos, account ~10 yr old
Inputs used
followers124
owner_typeOrganization
is_verifiedno
owner_loginavaje
public_repos51
account_age_days3,780

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 6 package(s) on maven
35/35Publish recency — latest publish 31 days ago
20/20Version history — 274 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesio.avaje:avaje-inject, io.avaje:avaje-inject-aop, io.avaje:avaje-inject-test, io.avaje:avaje-inject-events, io.avaje:avaje-inject-generator, io.avaje:avaje-inject-maven-plugin
ecosystemsmaven
any_deprecatedno
min_days_since_publish31

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://avaje.io/inject
10/10Repository description
10/10Topics — 13 topics
0/10Wiki
Inputs used
topicsjava, dependency-injection, apt, annotation-processing, dagger, inversion-of-control, kotlin, di-library, dinject, kapt, javax-inject, jakarta-inject, avaje
has_wikino
homepagehttps://avaje.io/inject
docs_sitehttps://avaje.io/inject
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 5/10 approved changesets -- score normalized to 5
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the maven:io.avaje:avaje-inject@12.7-javax runtime dependency closure — what installing the published package pulls in — 5 packages. 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.

69Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://avaje.io/llms.txt)
30.8/40Legible commit history — 26 of 45 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://avaje.io/llms.txt
legible_history_share0.578
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — blackbox-aspect/pom.xml, blackbox-collection-module-order/api/pom.xml, blackbox-collection-module-order/m1/pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 27 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.04
toolchain_manifestsblackbox-aspect/pom.xml, blackbox-collection-module-order/api/pom.xml, blackbox-collection-module-order/m1/pom.xml, blackbox-collection-module-order/m2/pom.xml, blackbox-collection-module-order/pom.xml, blackbox-collection-module-order/tests/pom.xml, blackbox-conditional-provider-order/api/pom.xml, blackbox-conditional-provider-order/m1/pom.xml, blackbox-conditional-provider-order/m2/pom.xml, blackbox-conditional-provider-order/pom.xml, blackbox-conditional-provider-order/tests/pom.xml, blackbox-multi-scope/pom.xml, blackbox-other/pom.xml, blackbox-test-inject/pom.xml, inject-aop/pom.xml, inject-bom/pom.xml, inject-events/pom.xml, inject-generator/pom.xml, inject-gradle-plugin/build.gradle, inject-maven-plugin/pom.xml, inject-test/pom.xml, inject/pom.xml, pom.xml
dependency_bot_commit_share0.27
How it's scored
45/45Type-checkable code — Java (statically typed)
55/55Manageable file sizes — 0/972 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes28,997
source_files_sampled972
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

321GitHub stars
14contributors
232commits, last 12 months
0days since last push
100releases
1bus factor
4open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch maven package 'io.avaje:blackbox-other' from its registry
  • Could not fetch maven package 'io.avaje:blackbox-aspect' from its registry

More detail

Star and fork history 0 ★ / 29 ⇿
0Stars
29Forks
87Releases

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.

0510152025302922020-102023-092026-08
Major 0Minor 0Patch 0

Each point covers 6 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-10-19 10:25 UTC

9Binary-Artifactsbinaries present in source code
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-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 5/10 approved changesets -- score normalized to 5
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 38
RegistryPackageVersion constraintManifest
Mavenio.avaje:avaje-inject${project.version}blackbox-multi-scope/pom.xml
Mavenio.avaje:blackbox-other${project.version}blackbox-multi-scope/pom.xml
Mavenio.avaje:blackbox-aspect${project.version}blackbox-test-inject/pom.xml
Mavenio.avaje:blackbox-other${project.version}blackbox-test-inject/pom.xml
Mavenio.avaje:avaje-jsonb3.16blackbox-test-inject/pom.xml
Mavenio.avaje:avaje-config5.2blackbox-test-inject/pom.xml
Mavenio.avaje:avaje-inject${project.version}blackbox-test-inject/pom.xml
Mavenio.avaje:avaje-spi-service2.17blackbox-test-inject/pom.xml
Mavenio.github.resilience4j:resilience4j-retry1.7.1blackbox-test-inject/pom.xml
Mavenio.github.resilience4j:resilience4j-annotations2.4.0blackbox-test-inject/pom.xml
Mavenio.avaje:avaje-inject12.7inject-bom/pom.xml
Mavenio.avaje:avaje-inject-aop12.7inject-bom/pom.xml
Mavenio.avaje:avaje-inject-events12.7inject-bom/pom.xml
Mavenio.avaje:avaje-inject-maven-plugin12.7inject-bom/pom.xml
Mavenio.avaje:avaje-inject-test12.7inject-bom/pom.xml
Mavenio.avaje:avaje-inject${project.version}inject-generator/pom.xml
Mavenio.avaje:avaje-inject-events${project.version}inject-generator/pom.xml
Mavenio.avaje:avaje-inject-aop${project.version}inject-generator/pom.xml
Mavenio.avaje:avaje-prisms${avaje.prisms.version}inject-generator/pom.xml
Mavenio.avaje:avaje-spi-service2.17inject-generator/pom.xml
Mavenio.avaje:avaje-http-api3.12.1inject-generator/pom.xml
Mavenio.avaje:avaje-inject${project.version}inject-maven-plugin/pom.xml
Mavenorg.ow2.asm:asm9.11inject-maven-plugin/pom.xml
Mavenio.avaje:avaje-inject${project.version}inject-test/pom.xml
Mavenorg.junit.jupiter:junit-jupiter-api${jupiter.version}inject-test/pom.xml
Mavenorg.junit.jupiter:junit-jupiter-engine${jupiter.version}inject-test/pom.xml
Mavennet.bytebuddy:byte-buddy1.18.15inject-test/pom.xml
Mavennet.bytebuddy:byte-buddy-agent1.18.15inject-test/pom.xml
Mavenorg.mockito:mockito-core${mockito.version}inject-test/pom.xml
Mavenorg.mockito:mockito-junit-jupiter${mockito.version}inject-test/pom.xml
Mavenorg.jspecify:jspecify1.0.1inject/pom.xml
Mavenjakarta.inject:jakarta.inject-api2.0.1inject/pom.xml
Mavenio.avaje:avaje-inject-aop${project.version}inject/pom.xml
Mavenio.avaje:avaje-applog1.2inject/pom.xml
Mavenio.avaje:avaje-config5.2inject/pom.xml
Mavenio.avaje:avaje-spi-service2.17inject/pom.xml
Mavenorg.mockito:mockito-core5.24.0inject/pom.xml
Mavenio.avaje:avaje-inject-events${project.version}inject/pom.xml
All dependencies 47

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

RegistryPackageVersionRelation
Mavenio.avaje:avaje-applog1.2direct
Mavenio.avaje:avaje-config5.2direct
Mavenio.avaje:avaje-http-api3.12.1direct
Mavenio.avaje:avaje-inject12.0direct
Mavenio.avaje:avaje-inject12.7direct
Mavenio.avaje:avaje-inject-aop12.7direct
Mavenio.avaje:avaje-inject-events12.7direct
Mavenio.avaje:avaje-inject-maven-plugin12.7direct
Mavenio.avaje:avaje-inject-test12.7direct
Mavenio.avaje:avaje-jsonb3.16direct
Mavenio.avaje:avaje-prisms2.1-RC2direct
Mavenio.avaje:avaje-spi-service2.17direct
Mavenio.avaje:blackbox-aspect12.7direct
Mavenio.avaje:blackbox-other12.7direct
Mavenio.github.resilience4j:resilience4j-annotations2.4.0direct
Mavenio.github.resilience4j:resilience4j-retry1.7.1direct
Mavenjakarta.inject:jakarta.inject-api2.0.1direct
Mavennet.bytebuddy:byte-buddy1.18.15direct
Mavennet.bytebuddy:byte-buddy-agent1.18.15direct
Mavenorg.jspecify:jspecify1.0.1direct
Mavenorg.junit.jupiter:junit-jupiter-api5.13.4direct
Mavenorg.junit.jupiter:junit-jupiter-engine5.13.4direct
Mavenorg.mockito:mockito-core5.24.0direct
Mavenorg.mockito:mockito-junit-jupiter5.24.0direct
Mavenorg.ow2.asm:asm9.11direct
Mavench.qos.logback:logback-classic1.6.5indirect
Mavenio.avaje:avaje-http-client3.12.1indirect
Mavenio.avaje:avaje-inject-generator12.7indirect
Mavenio.avaje:avaje-jex3.6indirect
Mavenio.avaje:avaje-jsr3051.2indirect
Mavenio.avaje:blackbox-collection-module-order-api12.7indirect
Mavenio.avaje:blackbox-collection-module-order-m112.7indirect
Mavenio.avaje:blackbox-collection-module-order-m212.7indirect
Mavenio.avaje:blackbox-conditional-provider-order-api12.7indirect
Mavenio.avaje:blackbox-conditional-provider-order-m112.7indirect
Mavenio.avaje:blackbox-conditional-provider-order-m212.7indirect
Mavenio.avaje:junit1.8indirect
Mavenjavax.annotation:javax.annotation-api1.3.2indirect
Mavenorg.apache.maven.plugin-tools:maven-plugin-annotations3.16.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin12.7indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin2.1-RC2indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin—indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin—indirect
Mavenorg.apache.maven.plugins:maven-plugin-plugin3.16.0indirect
Mavenorg.apache.maven:maven-core3.10.0indirect
Mavenorg.jetbrains:annotations26.1.0indirect
Mavenorg.projectlombok:lombok1.18.48indirect
Dependency advisories 0

Installing maven:io.avaje:avaje-inject@12.7-javax pulls in 5 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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 — Maven.