Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-03 22:34 UTC

nbbrd / java-io-util

Common I/O utilities for Java

JavaEUPL-1.2★ 1 star⑂ 1 forksince Dec 2017View on GitHub ↗

nbbrd/java-io-util holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (94/100) and lowest on Community & Adoption (24/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

8 followers50 public repossince Sep 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavencom.github.nbbrd.java-io-util:java-io-win0.0.39-2720 days ago
Mavencom.github.nbbrd.java-io-util:java-io-xml0.0.39-2720 days ago
Mavencom.github.nbbrd.java-io-util:java-io-base0.0.39-2720 days ago
Mavencom.github.nbbrd.java-io-util:java-io-curl0.0.39-1620 days ago
Mavencom.github.nbbrd.java-io-util:java-io-http0.0.39-1320 days ago
Mavencom.github.nbbrd.java-io-util:java-io-picocsv0.0.39-2120 days ago
Mavencom.github.nbbrd.java-io-util:java-io-xml-bind0.0.39-2420 days ago

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
32.5/36Commit cadence47/52 weeks with commits
18/18Commit volume183 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year183
human_commit_share0.67
days_since_last_push0
active_weeks_last_year47
How it's scored
27/27Ships releases38 releases published
36/36Release recencylatest release 20 days ago
19.8/27Release cadencea release every ~87.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count38
latest_release_tagv0.0.39
releases_from_tagsno
days_since_latest_release20
mean_days_between_releases87.1
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?

24At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks1 forks
0/15Watchers1 watchers
Inputs used
forks1
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (EUPL-1.2)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.3/22.5Commit distributiontop contributor authored 99% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.988
How it's scored
33.6/42Issue resolution80% of issues closed
28.6/30PR acceptance509/533 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/24 approved changesets -- score normalized to 0
Inputs used
merged_prs509
open_issues1
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.8
closed_unmerged_prs24
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 backingorganization-owned
0/20Verified domain
6.9/25Owner reach8 followers of nbbrd
24.4/25Track record50 public repos, account ~11 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedno
owner_loginnbbrd
public_repos50
account_age_days4,371

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable7 package(s) on maven
35/35Publish recencylatest publish 20 days ago
20/20Version history27 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescom.github.nbbrd.java-io-util:java-io-win, com.github.nbbrd.java-io-util:java-io-xml, com.github.nbbrd.java-io-util:java-io-base, com.github.nbbrd.java-io-util:java-io-curl, com.github.nbbrd.java-io-util:java-io-http, com.github.nbbrd.java-io-util:java-io-picocsv, com.github.nbbrd.java-io-util:java-io-xml-bind
ecosystemsmaven
any_deprecatedno
min_days_since_publish20

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicslibrary, zero-dependency, java8
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?

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/24 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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 1 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
5/5SASTSAST tool is run on all commits
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.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
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
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:com.github.nbbrd.java-io-util:java-io-win@0.0.39 runtime dependency closure — what installing the published package pulls in — 5 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.

65Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit history0 of 67 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes6,283
How it's scored
12.6/18One-command bootstrapjava-io-base/pom.xml, java-io-bom/pom.xml, java-io-curl/pom.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 maintenance33 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_manifestsjava-io-base/pom.xml, java-io-bom/pom.xml, java-io-curl/pom.xml, java-io-http/pom.xml, java-io-picocsv/pom.xml, java-io-win/pom.xml, java-io-xml-bind/pom.xml, java-io-xml/pom.xml, pom.xml
dependency_bot_commit_share0.33
How it's scored
45/45Type-checkable codeJava (statically typed)
55/55Manageable file sizes0/288 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes34,586
source_files_sampled288
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 examplessample
Inputs used
example_dirssample
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

1GitHub stars
2contributors
183commits, last 12 months
0days since last push
38releases
1bus factor
1open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 6.1 / 10
6.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-09-03 22:34 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
10CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/24 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 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
10SASTSAST tool is run on all commits
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 33
RegistryPackageVersion constraintManifest
Maven${project.groupId}:java-io-base${project.version}java-io-bom/pom.xml
Maven${project.groupId}:java-io-picocsv${project.version}java-io-bom/pom.xml
Maven${project.groupId}:java-io-win${project.version}java-io-bom/pom.xml
Maven${project.groupId}:java-io-xml${project.version}java-io-bom/pom.xml
Maven${project.groupId}:java-io-xml-bind${project.version}java-io-bom/pom.xml
Maven${project.groupId}:java-io-curl${project.version}java-io-bom/pom.xml
Maven${project.groupId}:java-io-http${project.version}java-io-bom/pom.xml
Maven${project.groupId}:java-io-base${project.version}java-io-curl/pom.xml
Maven${project.groupId}:java-io-base${project.version}java-io-http/pom.xml
Mavencom.github.nbbrd.java-io-util:java-io-curl${project.version}java-io-http/pom.xml
Mavencom.squareup.okhttp3:okhttp-jvm5.5.0java-io-http/pom.xml
Maven${project.groupId}:java-io-base${project.version}java-io-picocsv/pom.xml
Mavencom.github.nbbrd.picocsv:picocsv2.6.0java-io-picocsv/pom.xml
Maven${project.groupId}:java-io-base${project.version}java-io-win/pom.xml
Maven${project.groupId}:java-io-xml${project.version}java-io-xml-bind/pom.xml
Mavenjavax.xml.bind:jaxb-apijava-io-xml-bind/pom.xml
Mavenorg.glassfish.jaxb:jaxb-runtimejava-io-xml-bind/pom.xml
Maven${project.groupId}:java-io-base${project.version}java-io-xml/pom.xml
Mavenorg.jspecify:jspecify1.0.1pom.xml
Mavenorg.junit:junit-bom6.1.3pom.xml
Mavenorg.assertj:assertj-core3.27.7pom.xml
Mavenorg.wiremock:wiremock-standalone3.13.2pom.xml
Mavenorg.slf4j:slf4j-nop2.0.18pom.xml
Mavenjavax.xml.bind:jaxb-api2.4.0-b180830.0359pom.xml
Mavenorg.glassfish.jaxb:jaxb-runtime2.4.0-b180830.0438pom.xml
Mavenorg.kordamp.maven:pomchecker-enforcer-rules1.15.0pom.xml
Mavenorg.codehaus.mojo:extra-enforcer-rules1.12.0pom.xml
Mavencom.github.nbbrd.heylogs:heylogs-enforcer-rules${heylogs.version}pom.xml
Mavencom.github.nbbrd.nbbrd-maven-tools:nbbrd-enforcer-rules1.3.0pom.xml
Mavenorg.projectlombok:lombok${lombok.version}pom.xml
Mavencom.github.nbbrd.java-service-util:java-service-bom${java-service.version}pom.xml
Mavencom.github.nbbrd.java-design-util:java-design-annotation${java-design.version}pom.xml
Mavencom.github.nbbrd.java-design-util:java-design-processor${java-design.version}pom.xml
All dependencies 37

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

RegistryPackageVersionRelation
Mavencom.github.nbbrd.java-design-util:java-design-annotation1.10.2direct
Mavencom.github.nbbrd.java-design-util:java-design-processor1.10.2direct
Mavencom.github.nbbrd.java-io-util:java-io-curl0.0.40-SNAPSHOTdirect
Mavencom.github.nbbrd.picocsv:picocsv2.6.0direct
Mavencom.squareup.okhttp3:okhttp-jvm5.5.0direct
Mavenjavax.xml.bind:jaxb-api2.4.0-b180830.0359direct
Mavenorg.assertj:assertj-core3.27.7direct
Mavenorg.glassfish.jaxb:jaxb-runtime2.4.0-b180830.0438direct
Mavenorg.jspecify:jspecify1.0.1direct
Mavenorg.projectlombok:lombok1.18.46direct
Mavenorg.slf4j:slf4j-nop2.0.18direct
Mavenorg.wiremock:wiremock-standalone3.13.2direct
Mavencom.github.nbbrd.java-io-util:java-io-base0.0.40-SNAPSHOTindirect
Mavencom.github.nbbrd.java-io-util:java-io-xml0.0.40-SNAPSHOTindirect
Mavencom.github.nbbrd.java-service-util:java-service-annotation2.1.0indirect
Mavencom.github.nbbrd.java-service-util:java-service-processor2.1.0indirect
Mavencom.squareup.okio:okio-jvm3.18.1indirect
Mavencom.sun.istack:istack-commons-runtime3.0.7indirect
Mavencom.sun.xml.fastinfoset:FastInfoset1.2.15indirect
Mavenio.github.hakky54:ayza10.0.6indirect
Mavenio.github.hakky54:desidero1.0.0indirect
Mavenio.github.hakky54:laleler1.0.0indirect
Mavenio.github.hakky54:sude2.0.2indirect
Mavenjavax.activation:javax.activation-api1.2.0indirect
Mavennet.bytebuddy:byte-buddy1.18.3indirect
Mavenorg.apiguardian:apiguardian-api1.1.2indirect
Mavenorg.glassfish.jaxb:txw22.4.0-b180830.0438indirect
Mavenorg.jetbrains.kotlin:kotlin-stdlib2.1.21indirect
Mavenorg.jetbrains:annotations13.0indirect
Mavenorg.junit.jupiter:junit-jupiter6.1.3indirect
Mavenorg.junit.jupiter:junit-jupiter-api6.1.3indirect
Mavenorg.junit.jupiter:junit-jupiter-engine6.1.3indirect
Mavenorg.junit.jupiter:junit-jupiter-params6.1.3indirect
Mavenorg.junit.platform:junit-platform-commons6.1.3indirect
Mavenorg.junit.platform:junit-platform-engine6.1.3indirect
Mavenorg.jvnet.staxex:stax-ex1.8indirect
Mavenorg.opentest4j:opentest4j1.3.0indirect
Dependency advisories 0

Installing maven:com.github.nbbrd.java-io-util:java-io-win@0.0.39 pulls in 5 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 statisticsMaven.