Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-21 11:49 UTC

ethlo / itu

An extremely fast parser and formatter of standardized date and date-times supporting RFC-3339 (ISO-8601 profile) and more.

JavaApache-2.0★ 39 stars⑂ 10 forkssince Feb 2017View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

ethlo/itu holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (64/100) and lowest on Vitality (46/100). It was last updated 28 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

48
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

Morten HaraldsenPersonal account
17 followers71 public repossince Jan 2012ethlo

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavencom.ethlo.time:itu1.14.0-28546 days ago

Metrics by category

Vitality

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

46Weak · 21% of overall
How it's scored
28.8/36Push recencylast push 28 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share0.99
days_since_last_push28
active_weeks_last_year1
How it's scored
27/27Ships releases28 releases published
7.2/36Release recencylatest release 546 days ago
27/27Release cadencea release every ~43.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count28
latest_release_tagv1.14.0
releases_from_tagsno
days_since_latest_release546
mean_days_between_releases43.9
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?

48Weak · 17% of overall
How it's scored
25.6/60Stars39 stars
8/25Forks10 forks
0/15Watchers2 watchers
Inputs used
forks10
stars39
watchers2
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)
0/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_servicesapp.codacy.com, codecov.io, shields.io
has_pull_request_templateno

Sustainability & Governance

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

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.5/22.5Commit distributiontop contributor authored 98% of commits
8.1/13.5Contributor breadth6 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.977
How it's scored
42/42Issue resolution100% of issues closed
26.4/30PR acceptance29/33 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/29 approved changesets -- score normalized to 1
Inputs used
merged_prs29
open_issues0
closed_issues13
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs4
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
9/25Owner reach17 followers of ethlo
25/25Track record71 public repos, account ~14 yr old
Inputs used
followers17
owner_typeUser
is_verified
owner_loginethlo
public_repos71
account_age_days5,319
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on maven
14/35Publish recencylatest publish 546 days ago
20/20Version history28 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescom.ethlo.time:itu
ecosystemsmaven
any_deprecatedno
min_days_since_publish546

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests1 out of 8 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics13 topics
0/10Wiki
Inputs used
topicsrfc3339, time, java, parser, formatter, dateparser, datetime, date, library, optimized, iso-8601, no-dependencies, performance
has_wikino
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?

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests1 out of 8 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/29 approved changesets -- score normalized to 1
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0.5/5SASTSAST tool is not run on all commits -- score normalized to 1
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Branch-Protection, 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
advisories7
affected_packages1
assessed_packages20
unassessed_packages0
affected_by_severityhigh 1
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 20 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8.1/40Legible commit history15 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.152
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrappom.xml (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
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
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_manifestspom.xml
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable codeJava (statically typed)
55/55Manageable file sizes0/60 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes19,382
source_files_sampled60
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplessamples
Inputs used
example_dirssamples
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

39GitHub stars
6contributors
1commits, last 12 months
28days since last push
28releases
1bus factor
0open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 10 ⇿
0Stars
10Forks
23Releases

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.

02468101012017-042021-032025-02
Major 0Minor 8Patch 13

Each point covers 8 days.

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-08-21 11:49 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
1CI-Tests1 out of 8 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/29 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
1SASTSAST tool is not run on all commits -- score normalized to 1
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities13 existing vulnerabilities detected
All dependencies 20

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

RegistryPackageVersionRelation
Mavench.qos.logback:logback-classic1.3.15indirect
Mavencom.code-intelligence:jazzer-junit0.24.0indirect
Mavencom.ethlo.documentation:source-extractor-maven-plugin0.3.0indirect
Mavencom.fasterxml.jackson.core:jackson-databind2.18.2indirect
Mavencom.github.wvengen:proguard-maven-plugin2.6.1indirect
Mavenorg.apache.felix:maven-bundle-plugin5.1.8indirect
Mavenorg.apache.maven.plugins:maven-gpg-plugin1.6indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin3.4.2indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin3.3.1indirect
Mavenorg.apache.maven.plugins:maven-source-plugin3.2.1indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin3.5.2indirect
Mavenorg.assertj:assertj-core3.27.7indirect
Mavenorg.codehaus.mojo:license-maven-plugin2.2.0indirect
Mavenorg.codehaus.mojo:versions-maven-plugin2.8.1indirect
Mavenorg.jacoco:jacoco-maven-plugin0.8.12indirect
Mavenorg.junit.jupiter:junit-jupiter-api5.9.3indirect
Mavenorg.junit.jupiter:junit-jupiter-params5.9.3indirect
Mavenorg.moditect:moditect-maven-plugin1.2.2indirect
Mavenorg.slf4j:slf4j-api2.0.11indirect
Mavenorg.sonatype.plugins:nexus-staging-maven-plugin1.6.13indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
com.fasterxml.jackson.core:jackson-databind2.18.2indirecthigh73.2.1

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