palantir / tritium
Tritium is a library for instrumenting applications to provide better observability at runtime
palantir/tritium holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (99/100) and lowest on Engineering Quality (46/100). It was last updated today. A single contributor accounts for most of its recent work.
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.
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 68 is calibrated to 80 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 35.3/36 | Commit cadence — 51/52 weeks with commits |
| 18/18 | Commit volume — 316 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 316 |
| human_commit_share | 0.99 |
| days_since_last_push | 0 |
| active_weeks_last_year | 51 |
Release discipline
How it's scored
| 27/27 | Ships releases — 100 releases published |
| 36/36 | Release recency — latest release 3 days ago |
| 27/27 | Release cadence — a release every ~12.8 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 100 |
| latest_release_tag | 0.137.0 |
| releases_from_tags | no |
| days_since_latest_release | 3 |
| mean_days_between_releases | 12.8 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 29.5/60 | Stars — 67 stars |
| 10/25 | Forks — 17 forks |
| 13.5/15 | Watchers — 274 watchers |
Inputs used
| forks | 17 |
| stars | 67 |
| watchers | 274 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 7.2/7.2 | Issue template |
| 6.3/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 1 |
| has_contributing | no |
| has_issue_template | yes |
| has_code_of_conduct | no |
| readme_badge_services | shields.io |
| has_pull_request_template | yes |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 4.8/22.5 | Commit distribution — top contributor authored 78% of commits |
| 13.5/13.5 | Contributor breadth — 26 contributors |
| 3/10 | OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 26 |
| top_contributor_share | 0.785 |
How it's scored
| 23.4/42 | Issue resolution — 56% of issues closed |
| 27/30 | PR acceptance — 2,274/2,525 decided PRs merged |
| 13/13 | Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d |
| 13.5/15 | OpenSSF Scorecard: Code-Review — Found 28/30 approved changesets -- score normalized to 9 |
Inputs used
| merged_prs | 2,274 |
| open_issues | 16 |
| closed_issues | 20 |
| prs_merged_7d | 7 |
| prs_decided_7d | 7 |
| prs_merged_30d | 33 |
| prs_decided_30d | 33 |
| issue_closed_ratio | 0.556 |
| closed_unmerged_prs | 251 |
| first_time_authors_30d | 1 |
| first_time_prs_merged_30d | 1 |
| first_time_prs_decided_30d | 1 |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 20/20 | Verified domain |
| 25/25 | Owner reach — 4,721 followers of palantir |
| 25/25 | Track record — 267 public repos, account ~16 yr old |
Inputs used
| followers | 4,721 |
| owner_type | Organization |
| is_verified | yes |
| owner_login | palantir |
| public_repos | 267 |
| account_age_days | 5,921 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 28 out of 28 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 3 topics |
| 0/10 | Wiki |
Inputs used
| topics | java, instrumentation, octo-correct-managed |
| has_wiki | no |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 6/7.5 | Binary-Artifacts — binaries present in source code |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 28 out of 28 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 6.8/7.5 | Code-Review — Found 28/30 approved changesets -- score normalized to 9 |
| 0.8/2.5 | Contributors — project has 1 contributing companies or organizations -- score normalized to 3 |
| 0/10 | Dangerous-Workflow — no data |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — no data |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 12 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 6 |
| scorecard_aggregate | 6.6 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 37.7/40 | Legible commit history — 70 of 99 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.707 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
How it's scored
| 12.6/18 | One-command bootstrap — build.gradle, tritium-annotations/build.gradle, tritium-api/build.gradle (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — Java (statically typed) |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 8/8 | Automated maintenance — 1 of the last 100 commits are automated dependency updates |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | build.gradle, tritium-annotations/build.gradle, tritium-api/build.gradle, tritium-caffeine/build.gradle, tritium-core/build.gradle, tritium-ids/build.gradle, tritium-jmh/build.gradle, tritium-lib/build.gradle, tritium-metrics-jvm/build.gradle, tritium-metrics/build.gradle, tritium-processor/build.gradle, tritium-proxy/build.gradle, tritium-registry/build.gradle, tritium-slf4j/build.gradle, tritium-test/build.gradle, tritium-time/build.gradle, tritium-tracing/build.gradle |
| dependency_bot_commit_share | 0.01 |
Code legibility for models
How it's scored
| 45/45 | Type-checkable code — Java (statically typed) |
| 55/55 | Manageable file sizes — 0/197 source files over 60KB |
Inputs used
| primary_language | Java |
| largest_source_bytes | 38,022 |
| source_files_sampled | 197 |
| oversized_source_files | 0 |
Machine-readable interfaces
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software |
| 0/20 | MCP server — not applicable to this kind of software |
| 40/40 | Runnable examples — examples |
Inputs used
| example_dirs | examples |
| has_mcp_signal | no |
| api_schema_files | — |
| interfaces_expected_of | — |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
More detail
Star and fork history 0 ★ / 17 ⇿
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.
Each point covers 9 days.
OpenSSF Scorecard 6.6 / 10
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).
| 8 | Binary-Artifacts | binaries present in source code |
| n/a | Branch-Protection | internal 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 |
| 10 | CI-Tests | 28 out of 28 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 9 | Code-Review | Found 28/30 approved changesets -- score normalized to 9 |
| 3 | Contributors | project has 1 contributing companies or organizations -- score normalized to 3 |
| n/a | Dangerous-Workflow | no workflows found |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| n/a | Token-Permissions | No tokens found |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
All dependencies 0
Full resolved dependency set from the GitHub dependency graph: 0 direct and 0 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|
Dependency advisories not assessed
Advisory matching could not run for this report: No resolved dependencies to assess
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.
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.