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

OpenHFT / Chronicle-Core

Low level access to native memory, JVM and OS.

JavaApache-2.0★ 644 stars⑂ 136 forkssince Feb 2015View on GitHub ↗

OpenHFT/Chronicle-Core holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (83/100) and lowest on Engineering Quality (44/100). It was last updated 26 days ago. 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

842 followers35 public repossince May 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavennet.openhft:chronicle-core2026.6-48387 days ago
Mavennet.openhft:assertions-enabled1.0.0-11661 days ago
Mavennet.openhft:assertions-disabled1.0.0-11661 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 26 days ago
15.2/36Commit cadence — 22/52 weeks with commits
18/18Commit volume — 105 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year105
human_commit_share1
days_since_last_push26
active_weeks_last_year22

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 87 days ago
27/27Release cadence — a release every ~29.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagchronicle-core-2026.6
releases_from_tagsno
days_since_latest_release87
mean_days_between_releases29.6
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?

62Moderate · 17% of overall
How it's scored
45.6/60Stars — 644 stars
17.8/25Forks — 136 forks
9.1/15Watchers — 45 watchers
Inputs used
forks136
stars644
watchers45
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_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

73Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.9/22.5Commit distribution — top contributor authored 56% of commits
13.5/13.5Contributor breadth — 47 contributors
10/10OpenSSF Scorecard: Contributors — project has 14 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled47
top_contributor_share0.561
How it's scored
41.4/42Issue resolution — 98% of issues closed
25.3/30PR acceptance — 459/545 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 17/27 approved changesets -- score normalized to 6
Inputs used
merged_prs459
open_issues5
closed_issues321
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.985
closed_unmerged_prs86
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
21/25Owner reach — 842 followers of OpenHFT
23.3/25Track record — 35 public repos, account ~13 yr old
Inputs used
followers842
owner_typeOrganization
is_verifiedno
owner_loginOpenHFT
public_repos35
account_age_days4,893

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on maven
35/35Publish recency — latest publish 87 days ago
20/20Version history — 483 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnet.openhft:chronicle-core, net.openhft:assertions-enabled, net.openhft:assertions-disabled
ecosystemsmaven
any_deprecatedno
min_days_since_publish87

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 17 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
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
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 17/27 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 14 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
1/5SAST — SAST tool is not run on all commits -- score normalized to 2
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages13
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:net.openhft:chronicle-core@2026.6 runtime dependency closure — what installing the published package pulls in — 13 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.

67Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
18.1/40Legible commit history — 34 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.34
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes8,617
How it's scored
12.6/18One-command bootstrap — assertions-disabled/pom.xml, assertions-enabled/pom.xml, benchmarks/pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
6/10Demonstrated agent practice — 3 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
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.03
toolchain_manifestsassertions-disabled/pom.xml, assertions-enabled/pom.xml, benchmarks/pom.xml, checked-exceptions/pom.xml, pom.xml
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Java (statically typed)
54.8/55Manageable file sizes — 2/462 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes121,968
source_files_sampled462
oversized_source_files2

Key facts

644GitHub stars
47contributors
105commits, last 12 months
26days since last push
100releases
1bus factor
5open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch maven package 'net.openhft:chronicle-core-checked' from its registry

More detail

Star and fork history 0 ★ / 136 ⇿
0Stars
136Forks
100Releases

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.

025507510012515013532015-022020-122026-09
Major 0Minor 0Patch 0

Each point covers 11 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-10-19 10:10 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
0CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 17/27 approved changesets -- score normalized to 6
10Contributorsproject has 14 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
2SASTSAST tool is not run on all commits -- score normalized to 2
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Mavennet.openhft:third-party-bom2026.0pom.xml
Mavennet.openhft:chronicle-bom2026.0-SNAPSHOTpom.xml
Mavennet.openhft:affinity—pom.xml
Mavennet.openhft:posix—pom.xml
Mavennet.openhft:chronicle-analytics—pom.xml
Mavenorg.slf4j:slf4j-api—pom.xml
Mavenorg.jetbrains:annotations—pom.xml
All dependencies 31

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

RegistryPackageVersionRelation
Mavennet.openhft:affinity—direct
Mavennet.openhft:chronicle-analytics—direct
Mavennet.openhft:chronicle-bom2026.0-SNAPSHOTdirect
Mavennet.openhft:posix—direct
Mavennet.openhft:third-party-bom2026.0direct
Mavenorg.jetbrains:annotations—direct
Mavenorg.slf4j:slf4j-api—direct
Mavencom.github.ekryd.sortpom:sortpom-maven-plugin3.0.1indirect
Mavencom.squareup.okhttp3:mockwebserver—indirect
Mavennet.openhft:assertions-disabled—indirect
Mavennet.openhft:binary-compatibility-enforcer-plugin—indirect
Mavennet.openhft:chronicle-core—indirect
Mavennet.openhft:chronicle-test-framework—indirect
Mavennet.openhft:jlbh—indirect
Mavenorg.apache.commons:commons-math2.2indirect
Mavenorg.apache.felix:maven-bundle-plugin—indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin—indirect
Mavenorg.apache.maven.plugins:maven-install-plugin—indirect
Mavenorg.apache.maven.plugins:maven-invoker-plugin—indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin—indirect
Mavenorg.apache.maven.plugins:maven-scm-publish-plugin—indirect
Mavenorg.apache.maven.plugins:maven-shade-plugin—indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin—indirect
Mavenorg.apache.servicemix.tooling:depends-maven-plugin—indirect
Mavenorg.codehaus.mojo:exec-maven-plugin—indirect
Mavenorg.codehaus.mojo:exec-maven-plugin3.1.0indirect
Mavenorg.junit.jupiter:junit-jupiter-api—indirect
Mavenorg.junit.jupiter:junit-jupiter-params—indirect
Mavenorg.openjdk.jmh:jmh-core—indirect
Mavenorg.openjdk.jmh:jmh-generator-annprocess—indirect
Mavenorg.slf4j:slf4j-simple—indirect
Dependency advisories 0

Installing maven:net.openhft:chronicle-core@2026.6 pulls in 13 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.