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

daisy / braille-css-java

Implementation of Braille CSS in Java/ANTLR.

Java · GAPNo license detected★ 2 stars⑂ 1 forksince Jun 2015View on GitHub ↗

daisy/braille-css-java holds a health index of 25 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (45/100) and lowest on Community & Adoption (14/100). It was last updated 53 days ago. A single contributor accounts for most of its recent work.

25
overall / 100
At Risk

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.

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

Ownership

DAISY ConsortiumOrganization
64 followers99 public repossince Apr 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenorg.daisy.braille:braille-csspoints to another repo — not scored1.29.0-3453 days ago

Metrics by category

Vitality

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

32At Risk · 21% of overall
How it's scored
18/36Push recency — last push 53 days ago
4.8/36Commit cadence — 7/52 weeks with commits
9.7/18Commit volume — 11 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year11
human_commit_share1
days_since_last_push53
active_weeks_last_year7
How it's scored
16.2/27Ships releases — 19 version tags (no GitHub releases)
0/36Release recency — latest release 2,188 days ago
12.6/27Release cadence — a release every ~182.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count19
latest_release_tag1.17.0
releases_from_tagsyes
days_since_latest_release2,188
mean_days_between_releases182.8
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?

14Critical · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 1 forks
3.9/15Watchers — 6 watchers
Inputs used
forks1
stars2
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
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?

45Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
25.2/42Issue resolution — 60% of issues closed
19.8/30PR acceptance — 29/44 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/19 approved changesets -- score normalized to 0
Inputs used
merged_prs29
open_issues4
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.6
closed_unmerged_prs15
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
13/25Owner reach — 64 followers of daisy
25/25Track record — 99 public repos, account ~15 yr old
Inputs used
followers64
owner_typeOrganization
is_verifiedno
owner_logindaisy
public_repos99
account_age_days5,652

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 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 5 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

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?

23At Risk · 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 — 0 out of 5 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
0/7.5Code-Review — Found 0/19 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
18.5/35Direct dependencies free of known advisories — 1 affected: com.google.guava:guava 24.0-android (moderate 5.9)
10/25Indirect dependencies free of known advisories — 1 affected: commons-io:commons-io 2.6 (high 7.5)
30/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,316 days ago
Inputs used
sourceosv
advisories5
affected_packages2
assessed_packages11
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages1
Matched the maven:org.daisy.braille:braille-css@1.29.0 runtime dependency closure — what installing the published package pulls in — 11 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
2.1/40Legible commit history — 4 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.04
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — 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 — 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
toolchain_manifestspom.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)
53/55Manageable file sizes — 1/27 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes75,475
source_files_sampled27
oversized_source_files1

Key facts

2GitHub stars
1contributors
11commits, last 12 months
53days since last push
19releases
1bus factor
4open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • maven package 'org.daisy.braille:braille-css' points at a different repository (https://github.com/snaekobbi/braille-css.git); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 1.4 / 10
1.4aggregate

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 07:52 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/19 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Mavenorg.daisy.libs:jstyleparser1.20-p27-SNAPSHOTpom.xml
Mavencom.google.guava:guava24.0-androidpom.xml
Mavenorg.daisy.libs:jstyleparser—pom.xml
Mavencom.google.guava:guava—pom.xml
All dependencies 12

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

RegistryPackageVersionRelation
Mavencom.google.guava:guava—direct
Mavencom.google.guava:guava24.0-androiddirect
Mavenorg.daisy.libs:jstyleparser—direct
Mavenorg.daisy.libs:jstyleparser1.20-p27-SNAPSHOTdirect
Mavench.qos.logback:logback-classic1.0.11indirect
Mavenjunit:junit4.12indirect
Mavenorg.antlr:antlr3-maven-plugin3.5.2indirect
Mavenorg.apache.felix:maven-bundle-plugin—indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin—indirect
Mavenorg.apache.maven.plugins:maven-release-plugin—indirect
Mavenorg.daisy.libs:maven-dependency-plugin—indirect
Mavenxerces:xercesImpl2.11.0indirect
Dependency advisories 2

Installing maven:org.daisy.braille:braille-css@1.29.0 pulls in 11 packages, direct and transitive: 2 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
commons-io:commons-io2.6indirecthigh22.14.0
com.google.guava:guava24.0-androiddirectmoderate332.0.0-android

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.