Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-02 21:17 UTC

TAKETODAY / today-infrastructure

:sparkles: A Java library for applications software infrastructure

JavaApache-2.0★ 133 stars⑂ 14 forkssince Aug 2018View on GitHub ↗

TAKETODAY/today-infrastructure holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Engineering Quality (71/100) and lowest on Sustainability & Governance (53/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

海健 YangPersonal account
145 followers42 public repossince Jun 2017@today-tech

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

Metrics by category

Vitality

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

60Moderate · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 0 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume2,529 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,529
human_commit_share1
days_since_last_push0
active_weeks_last_year52
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

57Moderate · 17% of overall
How it's scored
34.4/60Stars133 stars
9.3/25Forks14 forks
1.7/15Watchers3 watchers
Inputs used
forks14
stars133
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges9
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapp.codacy.com, codecov.io, coveralls.io, github.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 99% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.994
How it's scored
38.7/42Issue resolution92% of issues closed
28.2/30PR acceptance95/101 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs95
open_issues19
closed_issues222
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.921
closed_unmerged_prs6
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.6/25Owner reach145 followers of TAKETODAY
23.9/25Track record42 public repos, account ~9 yr old
Inputs used
followers145
owner_typeUser
is_verified
owner_loginTAKETODAY
public_repos42
account_age_days3,367
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 workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.today-tech.cn/today-infrastructure/
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsjava, ioc, framework, dependency-injection, bean, lightweight, high-performance, netty, aop
has_wikiyes
homepagehttps://docs.today-tech.cn/today-infrastructure/
docs_sitehttps://docs.today-tech.cn/today-infrastructure/
has_readmeyes
has_docs_dirno
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
6/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
0/2.5CI-Testsno data
0.5/2.5CII-Best-Practicesbadge detected: InProgress
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 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
7.5/7.5Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, 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
advisories0
affected_packages0
assessed_packages9
unassessed_packages0
affected_by_severitynone
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 9 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.

65Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
10.7/40Legible commit history20 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.2
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,937
How it's scored
12.6/18One-command bootstrap.github/actions/publish-gradle-plugin/build.gradle, build.gradle, buildSrc/build.gradle (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingJava (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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
toolchain_manifests.github/actions/publish-gradle-plugin/build.gradle, build.gradle, buildSrc/build.gradle, infra-aop/build.gradle, infra-app/build.gradle, infra-aspects/build.gradle, infra-beans/build.gradle, infra-bom/build.gradle, infra-build/infra-annotation-config-processor/build.gradle, infra-build/infra-app-loader-tools/build.gradle, infra-build/infra-app-loader/build.gradle, infra-build/infra-code-coverage/build.gradle, infra-build/infra-configuration-processor/build.gradle, infra-build/infra-gradle-plugin/build.gradle, infra-build/infra-jarmode-layertools/build.gradle, infra-build/infra-maven-plugin/build.gradle, infra-build/infra-maven-plugin/src/maven/resources/pom.xml, infra-context-indexer/build.gradle, infra-context-support/build.gradle, infra-context/build.gradle, infra-core-test/build.gradle, infra-core/build.gradle, infra-dependencies/build.gradle, infra-docs/build.gradle, infra-expression/build.gradle, infra-http-client/build.gradle, infra-http-codec/build.gradle, infra-http-converter/build.gradle, infra-http-reactive/build.gradle, infra-http-service/build.gradle, infra-http/build.gradle, infra-instrument/build.gradle, infra-jcache/build.gradle, infra-jdbc/build.gradle, infra-messaging/build.gradle, infra-oxm/build.gradle, infra-persistence/build.gradle, infra-samples/build.gradle, infra-samples/buildSrc/build.gradle, infra-samples/netty-app/build.gradle, infra-samples/web-api/build.gradle, infra-starter/build.gradle, infra-starter/infra-starter-application/build.gradle, infra-starter/infra-starter-aspectj/build.gradle, infra-starter/infra-starter-flyway/build.gradle, infra-starter/infra-starter-freemarker/build.gradle, infra-starter/infra-starter-groovy-templates/build.gradle, infra-starter/infra-starter-gson/build.gradle, infra-starter/infra-starter-http-service/build.gradle, infra-starter/infra-starter-jackson/build.gradle, infra-starter/infra-starter-jdbc-test/build.gradle, infra-starter/infra-starter-jdbc/build.gradle, infra-starter/infra-starter-json/build.gradle, infra-starter/infra-starter-jsonb/build.gradle, infra-starter/infra-starter-logback/build.gradle, infra-starter/infra-starter-logging/build.gradle, infra-starter/infra-starter-mail/build.gradle, infra-starter/infra-starter-netty-server/build.gradle, infra-starter/infra-starter-persistence/build.gradle, infra-starter/infra-starter-reactor-server/build.gradle, infra-starter/infra-starter-restclient-test/build.gradle, infra-starter/infra-starter-restclient/build.gradle, infra-starter/infra-starter-sql/build.gradle, infra-starter/infra-starter-test/build.gradle, infra-starter/infra-starter-transaction/build.gradle, infra-starter/infra-starter-validation/build.gradle, infra-starter/infra-starter-web/build.gradle, infra-starter/infra-starter-webclient/build.gradle, infra-starter/infra-starter-webmvc-test/build.gradle, infra-starter/infra-starter-webmvc/build.gradle, infra-starter/infra-starter-websocket/build.gradle, infra-test-support/build.gradle, infra-test/build.gradle, infra-testcontainers/build.gradle, infra-tx/build.gradle, infra-web-client/build.gradle, infra-web-core/build.gradle, infra-web-netty-server/build.gradle, infra-web-reactive/build.gradle, infra-web-reactor-server/build.gradle, infra-web-server/build.gradle, infra-web/build.gradle, infra-webmvc-mock/build.gradle, infra-webmvc/build.gradle, infra-websocket/build.gradle, integration-tests/build.gradle, module/build.gradle, module/infra-app-health/build.gradle, module/infra-app-jdbc-test/build.gradle, module/infra-app-restclient-test/build.gradle, module/infra-app-resttestclient/build.gradle, module/infra-app-webmvc-test/build.gradle, module/infra-docker-compose/build.gradle, module/infra-flyway/build.gradle, module/infra-freemarker/build.gradle, module/infra-groovy-templates/build.gradle, module/infra-gson/build.gradle, module/infra-jackson/build.gradle, module/infra-jsonb/build.gradle, module/infra-mail/build.gradle, module/infra-mariadb4j/build.gradle, module/infra-sql/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeJava (statically typed)
54.8/55Manageable file sizes46/10,980 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes312,492
source_files_sampled10,980
oversized_source_files46
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)infra-app/src/test/resources/proto/sample.proto, infra-messaging/src/test/proto/sample.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample, sample, samples
Inputs used
example_dirsexample, sample, samples
has_mcp_signalno
api_schema_filesinfra-app/src/test/resources/proto/sample.proto, infra-messaging/src/test/proto/sample.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

133GitHub stars
5contributors
2,529commits, last 12 months
0days since last push
0releases
1bus factor
19open issues
Maven, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 14 ⇿
0Stars
14Forks

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.

03581013151412019-112023-012026-03

Each point covers 6 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-09-02 21:17 UTC

8Binary-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
n/aCI-Testsno pull request found
2CII-Best-Practicesbadge detected: InProgress
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous 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
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
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 8
RegistryPackageVersion constraintManifest
npmantora3.2.0-alpha.12infra-docs/package.json
npm@antora/atlas-extension1.0.0-alpha.5infra-docs/package.json
npm@antora/collector-extension1.0.2infra-docs/package.json
npm@asciidoctor/tabs1.0.0-beta.6infra-docs/package.json
npm@springio/antora-extensions1.14.7infra-docs/package.json
npm@opendevise/antora-release-line-extension1.0.0infra-docs/package.json
npmfast-xml-parser5.7.0infra-docs/package.json
npm@today-tech/antora-extensions1.0.1infra-docs/package.json
All dependencies 9

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

RegistryPackageVersionRelation
npm@antora/atlas-extension1.0.0-alpha.5direct
npm@antora/collector-extension1.0.2direct
npm@asciidoctor/tabs1.0.0-beta.6direct
npm@opendevise/antora-release-line-extension1.0.0direct
npm@springio/antora-extensions1.14.7direct
npm@today-tech/antora-extensions1.0.1direct
npmantora3.2.0-alpha.12direct
npmfast-xml-parser5.7.0direct
Mavenorg.apache.maven.plugins:maven-plugin-plugin3.6.4indirect
Dependency advisories 0

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

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.