Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-26 14:09 UTC

bloxbean / julc

An Experimental Java-to-UPLC Compiler

Java · LeanMIT★ 6 stars⑂ 1 forksince Feb 2026View on GitHub ↗

bloxbean/julc holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (85/100) and lowest on Community & Adoption (39/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

BloxBeanOrganization · verified domain
38 followers62 public repossince Apr 2019

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?

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
17.3/36Commit cadence — 25/52 weeks with commits
18/18Commit volume — 385 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year385
human_commit_share1
days_since_last_push2
active_weeks_last_year25
How it's scored
27/27Ships releases — 13 releases published
36/36Release recency — latest release 22 days ago
27/27Release cadence — a release every ~14.9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count13
latest_release_tagv0.1.0-pre16
releases_from_tagsno
days_since_latest_release22
mean_days_between_releases14.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

39Weak · 17% of overall
How it's scored
11.3/60Stars — 6 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars6
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
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?

53Moderate · 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
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
26.2/42Issue resolution — 62% of issues closed
30/30PR acceptance — 64/64 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs64
open_issues9
closed_issues15
prs_merged_7d2
prs_decided_7d2
prs_merged_30d17
prs_decided_30d17
issue_closed_ratio0.625
closed_unmerged_prs0
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
20/20Verified domain
11.4/25Owner reach — 38 followers of bloxbean
25/25Track record — 62 public repos, account ~7 yr old
Inputs used
followers38
owner_typeOrganization
is_verifiedyes
owner_loginbloxbean
public_repos62
account_age_days2,699

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://julc.dev
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://julc.dev
docs_sitehttps://julc.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

41Weak · 16% of overall
How it's scored
5.2/7.5Binary-Artifacts — binaries present in source code
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/2 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 31 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.1

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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://julc.dev/llms.txt)
40/40Legible commit history — 91 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://julc.dev/llms.txt
legible_history_share0.91
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes7,093
How it's scored
12.6/18One-command bootstrap — build.gradle, julc-analysis/build.gradle, julc-analyzer-cli/build.gradle (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — docs/tsconfig.json, julc-playground/frontend/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
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
lockfilespackage-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsdocs/tsconfig.json, julc-playground/frontend/tsconfig.json
agent_commit_share0
toolchain_manifestsbuild.gradle, julc-analysis/build.gradle, julc-analyzer-cli/build.gradle, julc-annotation-processor/build.gradle, julc-benchmark/build.gradle, julc-bls/build.gradle, julc-blueprint/build.gradle, julc-bom/build.gradle, julc-cardano-client-lib/build.gradle, julc-cli/build.gradle, julc-compiler/build.gradle, julc-core/build.gradle, julc-decompiler/build.gradle, julc-e2e-tests/build.gradle, julc-examples/build.gradle, julc-gradle-plugin/build.gradle, julc-jrl/build.gradle, julc-jrl/julc-jrl-core/build.gradle, julc-ledger-api/build.gradle, julc-playground/build.gradle, julc-plugin-test/build.gradle, julc-stdlib/build.gradle, julc-testkit-jqwik/build.gradle, julc-testkit/build.gradle, julc-verification/build.gradle, julc-vm-java/build.gradle, julc-vm-scalus/build.gradle, julc-vm-truffle/build.gradle, julc-vm/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Java (statically typed)
54.5/55Manageable file sizes — 11/1,190 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes334,376
source_files_sampled1,190
oversized_source_files11
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — example, examples
Inputs used
example_dirsexample, examples
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

6GitHub stars
1contributors
385commits, last 12 months
2days since last push
13releases
1bus factor
9open issues
Maven, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

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-26 14:08 UTC

7Binary-Artifactsbinaries present in source code
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests2 out of 2 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/2 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities31 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmmonaco-editor^0.52.2julc-playground/frontend/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.