emilianobonassi / jpbc
jPBC fork for get Maven works again
emilianobonassi/jpbc holds a health index of 23 out of 100, placing it in the At Risk band. It scores highest on AI Readiness (48/100) and lowest on Vitality (13/100). It was last updated 2796 days ago.
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.
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 33 is calibrated to 27 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
Work has arrived and nobody has attended to it
Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.
How abandonment is assessedHow it's scored
| 0/36 | Push recency — last push 2,796 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Inputs used
| commits_last_year | 0 |
| human_commit_share | — |
| days_since_last_push | 2,796 |
| active_weeks_last_year | 0 |
Release discipline
How it's scored
| 16.2/27 | Ships releases — 1 version tags (no GitHub releases) |
| 0/36 | Release recency — latest release 4,040 days ago |
| 12.6/27 | Release cadence — cadence unknown (single release) |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 1 |
| latest_release_tag | v2.0.0 |
| releases_from_tags | yes |
| days_since_latest_release | 4,040 |
| mean_days_between_releases | — |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 20/60 | Stars — 18 stars |
| 9.3/25 | Forks — 14 forks |
| 1.7/15 | Watchers — 3 watchers |
Inputs used
| forks | 14 |
| stars | 18 |
| watchers | 3 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 16.9/22.5 | License — license file present, not a recognized license |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | no |
| readme_badges | 0 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Issue & PR responsiveness
How it's scored
| 10.5/42 | Issue resolution — 25% of issues closed |
| 0/30 | PR acceptance — no decided pull requests or no data |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/6 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 0 |
| open_issues | 3 |
| closed_issues | 1 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 0.25 |
| closed_unmerged_prs | 0 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Ownership & stewardship
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 18.5/25 | Owner reach — 378 followers of emilianobonassi |
| 25/25 | Track record — 81 public repos, account ~12 yr old |
Inputs used
| followers | 378 |
| owner_type | User |
| is_verified | — |
| owner_login | emilianobonassi |
| public_repos | 81 |
| account_age_days | 4,495 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — http://gas.dia.unisa.it/projects/jpbc/index.html |
| 10/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | http://gas.dia.unisa.it/projects/jpbc/index.html |
| docs_site | http://gas.dia.unisa.it/projects/jpbc/index.html |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 0/7.5 | Binary-Artifacts — binaries present in source code |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/6 approved changesets -- score normalized to 0 |
| 0/2.5 | Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
| 0/10 | Dangerous-Workflow — no data |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — no SAST tool detected |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — no data |
| 4.5/7.5 | Vulnerabilities — 4 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 12 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 6 |
| scorecard_aggregate | 1 |
Dependency advisories
How it's scored
| 19.6/35 | Direct dependencies free of known advisories — 1 affected: org.bouncycastle:bcprov-jdk16 1.46 (moderate 5.5) |
| 0/25 | Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope |
| 35.2/40 | No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,009 days ago |
Inputs used
| source | osv |
| advisories | 4 |
| affected_packages | 2 |
| assessed_packages | 14 |
| unassessed_packages | 1 |
| affected_by_severity | moderate 2 |
| direct_affected_packages | 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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
How it's scored
| 12.6/18 | One-command bootstrap — jpbc-android/pom.xml, jpbc-api/pom.xml, jpbc-benchmark/pom.xml (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — Java (statically typed) |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | — |
| toolchain_manifests | jpbc-android/pom.xml, jpbc-api/pom.xml, jpbc-benchmark/pom.xml, jpbc-crypto/pom.xml, jpbc-mm/pom.xml, jpbc-pbc/pom.xml, jpbc-plaf/pom.xml, jpbc-site-skin/pom.xml, jpbc-test/pom.xml, pom.xml |
| dependency_bot_commit_share | — |
Code legibility for models
How it's scored
| 45/45 | Type-checkable code — Java (statically typed) |
| 54.8/55 | Manageable file sizes — 1/363 source files over 60KB |
Inputs used
| primary_language | Java |
| largest_source_bytes | 86,857 |
| source_files_sampled | 363 |
| oversized_source_files | 1 |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Contributor list unavailable
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-mm' from its registry
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-api' from its registry
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-pbc' from its registry
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-plaf' from its registry
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-test' from its registry
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-crypto' from its registry
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-android' from its registry
- Could not fetch maven package 'it.unisa.dia.gas:jpbc-benchmark' from its registry
More detail
Star and fork history 0 ★ / 14 ⇿
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.
Each point covers 6 days.
OpenSSF Scorecard 1.0 / 10
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).
| 0 | Binary-Artifacts | binaries present in source code |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/6 approved changesets -- score normalized to 0 |
| 0 | Contributors | project has 0 contributing companies or organizations -- score normalized to 0 |
| n/a | Dangerous-Workflow | no workflows found |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | no SAST tool detected |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| n/a | Token-Permissions | No tokens found |
| 6 | Vulnerabilities | 4 existing vulnerabilities detected |
Direct dependencies 19
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | jpbc-android/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-plaf | 2.0.0 | jpbc-android/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | jpbc-benchmark/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-plaf | 2.0.0 | jpbc-benchmark/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-pbc | 2.0.0 | jpbc-benchmark/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | jpbc-crypto/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-plaf | 2.0.0 | jpbc-crypto/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-pbc | 2.0.0 | jpbc-crypto/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-mm | 2.0.0 | jpbc-crypto/pom.xml |
| Maven | org.bouncycastle:bcprov-jdk16 | 1.46 | jpbc-crypto/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | jpbc-mm/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-plaf | 2.0.0 | jpbc-mm/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | jpbc-pbc/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-plaf | 2.0.0 | jpbc-pbc/pom.xml |
| Maven | net.java.dev.jna:jna | 3.2.5 | jpbc-pbc/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | jpbc-plaf/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | jpbc-test/pom.xml |
| Maven | it.unisa.dia.gas:jpbc-plaf | 2.0.0 | jpbc-test/pom.xml |
| Maven | org.apache.maven.doxia:doxia-core | 1.1.3 | pom.xml |
All dependencies 15
Full resolved dependency set from the GitHub dependency graph: 7 direct and 8 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| Maven | it.unisa.dia.gas:jpbc-api | 2.0.0 | direct |
| Maven | it.unisa.dia.gas:jpbc-mm | 2.0.0 | direct |
| Maven | it.unisa.dia.gas:jpbc-pbc | 2.0.0 | direct |
| Maven | it.unisa.dia.gas:jpbc-plaf | 2.0.0 | direct |
| Maven | net.java.dev.jna:jna | 3.2.5 | direct |
| Maven | org.apache.maven.doxia:doxia-core | 1.1.3 | direct |
| Maven | org.bouncycastle:bcprov-jdk16 | 1.46 | direct |
| Maven | com.google.android:android | 4.1.1.4 | indirect |
| Maven | com.jayway.maven.plugins.android.generation2:android-maven-plugin | — | indirect |
| Maven | junit:junit | 4.8.2 | indirect |
| Maven | org.apache.maven.plugins:maven-changes-plugin | 2.3 | indirect |
| Maven | org.apache.maven.plugins:maven-compiler-plugin | 2.3 | indirect |
| Maven | org.apache.maven.plugins:maven-jar-plugin | 2.2 | indirect |
| Maven | org.apache.maven.plugins:maven-project-info-reports-plugin | 2.1.2 | indirect |
| Maven | org.apache.maven.plugins:maven-site-plugin | 2.1.1 | indirect |
Dependency advisories 2
This repository publishes no package the index resolves, so its own dependency graph was assessed — 14 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 1 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.
| Package | Version | Relation | Severity | Advisories | Fixed in |
|---|---|---|---|---|---|
| org.bouncycastle:bcprov-jdk16 | 1.46 | direct | moderate | 3 | 1.73 |
| junit:junit | 4.8.2 | indirect | moderate | 1 | 4.13.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.
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.