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

DominoKit / domino-rest

domino-rest

JavaApache-2.0★ 35 stars⑂ 7 forkssince Jul 2018View on GitHub ↗

DominoKit/domino-rest holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (64/100) and lowest on AI Readiness (41/100). It was last updated 24 days ago. A single contributor accounts for most of its recent work.

56
overall / 100
Moderate

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.

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

Ownership

DominoKitOrganization
28 followers50 public repossince May 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenorg.dominokit:domino-rest-jvm2.0.2-1724 days ago
Mavenorg.dominokit:domino-rest-test2.0.0-RC2-13711 days ago
Mavenorg.dominokit:domino-rest-jaxrs2.0.2-1724 days ago
Mavenorg.dominokit:domino-rest-client2.0.2-1724 days ago
Mavenorg.dominokit:domino-rest-shared2.0.2-1824 days ago
Mavenorg.dominokit:domino-rest-processor2.0.2-1724 days ago

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 24 days ago
4.8/36Commit cadence — 7/52 weeks with commits
14.3/18Commit volume — 38 commits in the last year
6/10OpenSSF Scorecard: Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year38
human_commit_share1
days_since_last_push24
active_weeks_last_year7
How it's scored
27/27Ships releases — 7 releases published
16.2/36Release recency — latest release 292 days ago
12.6/27Release cadence — a release every ~218.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tag2.0.0
releases_from_tagsno
days_since_latest_release292
mean_days_between_releases218.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?

43Weak · 17% of overall
How it's scored
24.8/60Stars — 35 stars
6.5/25Forks — 7 forks
4.7/15Watchers — 8 watchers
Inputs used
forks7
stars35
watchers8
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_badges4
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.5/22.5Commit distribution — top contributor authored 80% of commits
5.4/13.5Contributor breadth — 4 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.801
How it's scored
41.4/42Issue resolution — 99% of issues closed
24/30PR acceptance — 12/15 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs12
open_issues1
closed_issues69
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.986
closed_unmerged_prs3
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
10.5/25Owner reach — 28 followers of DominoKit
24.4/25Track record — 50 public repos, account ~9 yr old
Inputs used
followers28
owner_typeOrganization
is_verifiedno
owner_loginDominoKit
public_repos50
account_age_days3,442

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 6 package(s) on maven
35/35Publish recency — latest publish 24 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesorg.dominokit:domino-rest-jvm, org.dominokit:domino-rest-test, org.dominokit:domino-rest-jaxrs, org.dominokit:domino-rest-client, org.dominokit:domino-rest-shared, org.dominokit:domino-rest-processor
ecosystemsmaven
any_deprecatedno
min_days_since_publish24

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/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_dirno
has_descriptionyes

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no 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
4.5/7.5Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
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
0/7.5Vulnerabilities — 27 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
7.4/25Indirect dependencies free of known advisories — 2 affected: com.fasterxml.jackson.core:jackson-core 2.18.6 (high 7.5), com.fasterxml.jackson.core:jackson-databind 2.18.6 (high 8.1)
33.3/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 117 days ago
Inputs used
sourceosv
advisories16
affected_packages2
assessed_packages17
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Matched the maven:org.dominokit:domino-rest-jvm@2.0.2 runtime dependency closure — what installing the published package pulls in — 17 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6.4/40Legible commit history — 12 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.12
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — domino-rest-client-test/pom.xml, domino-rest-client/pom.xml, domino-rest-jaxrs/pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
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
toolchain_manifestsdomino-rest-client-test/pom.xml, domino-rest-client/pom.xml, domino-rest-jaxrs/pom.xml, domino-rest-jvm/pom.xml, domino-rest-processor/pom.xml, domino-rest-shared/pom.xml, domino-rest-test-java17/pom.xml, domino-rest-test/pom.xml, pom.xml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Java (statically typed)
55/55Manageable file sizes — 0/286 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes57,356
source_files_sampled286
oversized_source_files0

Key facts

35GitHub stars
4contributors
38commits, last 12 months
24days since last push
7releases
1bus factor
1open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch maven package 'org.dominokit:domino-rest-client-test' from its registry
  • Could not fetch maven package 'org.dominokit:domino-rest-test-java17' from its registry

More detail

Star and fork history 0 ★ / 7 ⇿
0Stars
7Forks
7Releases

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.

1234567712019-062022-122026-07
Major 2Minor 0Patch 2

Each point covers 7 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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 09:47 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
10Packagingpackaging workflow 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
0Vulnerabilities27 existing vulnerabilities detected
Direct dependencies 45
RegistryPackageVersion constraintManifest
Mavenorg.gwtproject.timer:gwt-timer1.0.0-RC1domino-rest-client/pom.xml
Mavenorg.dominokit:domino-slf4j-logger${domino.logger.version}domino-rest-client/pom.xml
Mavenorg.dominokit:domino-rest-shared${project.version}domino-rest-client/pom.xml
Mavenorg.gwtproject.core:gwt-core1.0.0-RC1domino-rest-client/pom.xml
Mavenorg.gwtproject.event:gwt-event1.0.0-RC1domino-rest-client/pom.xml
Mavenorg.gwtproject.xhr:gwt-xhr1.0.0-RC1domino-rest-client/pom.xml
Mavenorg.gwtproject.regexp:gwt-regexp1.0.0-RC1domino-rest-client/pom.xml
Mavencom.google.elemental2:elemental2-promise—domino-rest-client/pom.xml
Mavenjakarta.ws.rs:jakarta.ws.rs-api${jax.rs.version}domino-rest-client/pom.xml
Mavenorg.dominokit:domino-rest-jaxrs${project.version}domino-rest-client/pom.xml
Mavenorg.dominokit:domino-rest-shared${project.version}domino-rest-jvm/pom.xml
Mavenjakarta.ws.rs:jakarta.ws.rs-api${jax.rs.version}domino-rest-jvm/pom.xml
Mavenorg.dominokit:domino-rest-shared${project.version}domino-rest-processor/pom.xml
Mavenorg.dominokit:domino-jackson-processor${domino.jackson.version}domino-rest-processor/pom.xml
Mavenjakarta.ws.rs:jakarta.ws.rs-api${jax.rs.version}domino-rest-processor/pom.xml
Mavencom.google.auto.service:auto-service1.1.1domino-rest-processor/pom.xml
Mavenorg.dominokit:domino-apt-commons1.0.5domino-rest-processor/pom.xml
Mavenjakarta.ws.rs:jakarta.ws.rs-api${jax.rs.version}domino-rest-shared/pom.xml
Mavenorg.dominokit:domino-jackson${domino.jackson.version}domino-rest-shared/pom.xml
Mavenorg.dominokit:domino-aggregator-shared${domino.aggregator.version}domino-rest-shared/pom.xml
Mavenjavax.annotation:javax.annotation-api—domino-rest-shared/pom.xml
Mavenorg.dominokit:domino-rest-jvm${project.version}domino-rest-test-java17/pom.xml
Mavenorg.dominokit:domino-rest-jvm${project.version}domino-rest-test/pom.xml
Mavenorg.gwtproject:gwt${gwt.version}pom.xml
Mavencommons-codec:commons-codec1.11pom.xml
Mavenorg.ow2.asm:asm9.7.1pom.xml
Mavenorg.ow2.asm:asm-commons9.7.1pom.xml
Mavenorg.ow2.asm:asm-tree9.7.1pom.xml
Mavenorg.ow2.asm:asm-util9.7.1pom.xml
Mavenxml-apis:xml-apis1.4.01pom.xml
Mavenjavax.servlet:javax.servlet-api3.1.0pom.xml
Mavenjavax.annotation:javax.annotation-api1.3.2pom.xml
Mavencom.google.elemental2:elemental2-core${elemental2.version}pom.xml
Mavencom.google.elemental2:elemental2-dom${elemental2.version}pom.xml
Mavencom.google.elemental2:elemental2-promise${elemental2.version}pom.xml
Mavencom.google.jsinterop:jsinterop-annotations2.0.2pom.xml
Mavencom.google.code.findbugs:jsr3053.0.2pom.xml
Mavencommons-io:commons-io2.15.0pom.xml
Mavencom.fasterxml.jackson.core:jackson-databind${jackson.databind.version}pom.xml
Mavencom.fasterxml.jackson.core:jackson-annotations${jackson.databind.version}pom.xml
Mavencom.fasterxml.jackson.core:jackson-core${jackson.databind.version}pom.xml
Mavencom.google.auto:auto-common1.2.2pom.xml
Mavencom.google.guava:guava32.1.3-jrepom.xml
Mavenjakarta.ws.rs:jakarta.ws.rs-api${jax.rs.version}pom.xml
Mavenorg.apache.commons:commons-lang33.18.0pom.xml
All dependencies 63

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

RegistryPackageVersionRelation
Mavencom.fasterxml.jackson.core:jackson-annotations2.16.0direct
Mavencom.fasterxml.jackson.core:jackson-core2.16.0direct
Mavencom.fasterxml.jackson.core:jackson-databind2.16.0direct
Mavencom.google.auto.service:auto-service1.1.1direct
Mavencom.google.auto:auto-common1.2.2direct
Mavencom.google.elemental2:elemental2-core1.2.3direct
Mavencom.google.elemental2:elemental2-dom1.2.3direct
Mavencom.google.elemental2:elemental2-promise—direct
Mavencom.google.elemental2:elemental2-promise1.2.3direct
Mavencom.google.guava:guava32.1.3-jredirect
Mavencommons-codec:commons-codec1.10direct
Mavenjakarta.ws.rs:jakarta.ws.rs-api—direct
Mavenjavax.annotation:javax.annotation-api—direct
Mavenjavax.annotation:javax.annotation-api1.3.2direct
Mavenjavax.servlet:javax.servlet-api3.1.0direct
Mavenorg.apache.commons:commons-lang33.14.0direct
Mavenorg.dominokit:domino-aggregator-shared—direct
Mavenorg.dominokit:domino-apt-commons1.0.5direct
Mavenorg.dominokit:domino-jackson—direct
Mavenorg.dominokit:domino-jackson-processor—direct
Mavenorg.dominokit:domino-rest-jaxrs2.0.0direct
Mavenorg.dominokit:domino-rest-jvm2.0.0direct
Mavenorg.dominokit:domino-rest-shared2.0.0direct
Mavenorg.dominokit:domino-slf4j-logger—direct
Mavenorg.gwtproject.core:gwt-core1.0.0-RC1direct
Mavenorg.gwtproject.event:gwt-event1.0.0-RC1direct
Mavenorg.gwtproject.regexp:gwt-regexp1.0.0-RC1direct
Mavenorg.gwtproject.timer:gwt-timer1.0.0-RC1direct
Mavenorg.gwtproject.xhr:gwt-xhr1.0.0-RC1direct
Mavenorg.gwtproject:gwt2.12.0direct
Mavenxml-apis:xml-apis1.4.01direct
Maven jakarta.ws.rs:jakarta.ws.rs-api3.1.0indirect
Mavencom.diffplug.spotless:spotless-maven-plugin2.43.0indirect
Mavencom.mycila:license-maven-plugin3.0indirect
Mavenjunit:junit4.13.1indirect
Mavenjunit:junit4.13.2indirect
Mavennet.ltgt.gwt.maven:gwt-maven-plugin—indirect
Mavennet.ltgt.gwt.maven:gwt-maven-plugin1.1.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin—indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.11.0indirect
Mavenorg.apache.maven.plugins:maven-deploy-plugin3.0.0-M1indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin3.0.0-M3indirect
Mavenorg.apache.maven.plugins:maven-gpg-plugin—indirect
Mavenorg.apache.maven.plugins:maven-gpg-plugin1.6indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin3.6.2indirect
Mavenorg.apache.maven.plugins:maven-shade-plugin3.2.4indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin3.0.0-M5indirect
Mavenorg.assertj:assertj-core3.19.0indirect
Mavenorg.assertj:assertj-core3.8.0indirect
Mavenorg.dominokit:domino-rest-client2.0.0indirect
Mavenorg.dominokit:domino-rest-processor2.0.0indirect
Mavenorg.dominokit:gitflow-maven-plugin1.0.0indirect
Mavenorg.glassfish.jersey.containers:jersey-container-jdk-http3.0.4indirect
Mavenorg.glassfish.jersey.core:jersey-server3.0.4indirect
Mavenorg.glassfish.jersey.inject:jersey-hk23.0.4indirect
Mavenorg.glassfish.jersey.media:jersey-media-json-jackson3.0.4indirect
Mavenorg.gwtproject:gwt-dev—indirect
Mavenorg.gwtproject:gwt-user—indirect
Mavenorg.junit.jupiter:junit-jupiter-engine5.7.0indirect
Mavenorg.junit.jupiter:junit-jupiter-params5.7.0indirect
Mavenorg.junit.platform:junit-platform-launcher1.7.0indirect
Mavenorg.sonatype.central:central-publishing-maven-plugin—indirect
Mavenorg.sonatype.central:central-publishing-maven-plugin0.8.0indirect
Dependency advisories 2

Installing maven:org.dominokit:domino-rest-jvm@2.0.2 pulls in 17 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
com.fasterxml.jackson.core:jackson-core2.18.6indirecthigh33.2.3
com.fasterxml.jackson.core:jackson-databind2.18.6indirecthigh133.2.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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Maven.