Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 13:38 UTC

jboss / jboss-parent-pom

JBoss Parent POM

No license detected★ 29 stars⑂ 64 forkssince Sep 2010View on GitHub ↗

jboss/jboss-parent-pom holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (93/100) and lowest on AI Readiness (29/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

jbossOrganization
35 followers96 public repossince Jan 2010

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?

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 196 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year196
human_commit_share0.55
days_since_last_push2
active_weeks_last_year42
How it's scored
27/27Ships releases — 21 releases published
36/36Release recency — latest release 26 days ago
19.8/27Release cadence — a release every ~70.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count21
latest_release_tagjboss-parent-55
releases_from_tagsno
days_since_latest_release26
mean_days_between_releases70.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?

35Weak · 17% of overall
How it's scored
23.5/60Stars — 29 stars
15/25Forks — 64 forks
5.3/15Watchers — 10 watchers
Inputs used
forks64
stars29
watchers10
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_badges—
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.4/22.5Commit distribution — top contributor authored 58% of commits
13.5/13.5Contributor breadth — 34 contributors
10/10OpenSSF Scorecard: Contributors — project has 63 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled34
top_contributor_share0.583
How it's scored
33.9/42Issue resolution — 81% of issues closed
25.5/30PR acceptance — 459/540 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 1/2 approved changesets -- score normalized to 5
Inputs used
merged_prs459
open_issues11
closed_issues46
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.807
closed_unmerged_prs81
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
11.2/25Owner reach — 35 followers of jboss
25/25Track record — 96 public repos, account ~16 yr old
Inputs used
followers35
owner_typeOrganization
is_verifiedno
owner_loginjboss
public_repos96
account_age_days6,141

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
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?

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 15 out of 15 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
3.8/7.5Code-Review — Found 1/2 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 63 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.7
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 advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages48
unassessed_packages11
affected_by_severitynone
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 48 resolved dependencies against OSV. 11 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 51 of 55 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.927
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — pom.xml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 45 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestspom.xml
dependency_bot_commit_share0.45

Key facts

29GitHub stars
34contributors
196commits, last 12 months
2days since last push
21releases
1bus factor
11open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 64 ⇿
0Stars
64Forks
16Releases

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.

01325385063756422011-102018-112025-11
Major 0Minor 0Patch 0

Each point covers 13 days.

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-11-16 13:38 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-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 1/2 approved changesets -- score normalized to 5
10Contributorsproject has 63 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 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
0SASTSAST tool is not run on all commits -- score normalized to 0
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 3
RegistryPackageVersion constraintManifest
Mavencom.puppycrawl.tools:checkstyle${version.checkstyle}pom.xml
Mavenorg.codehaus.plexus:plexus-archiver${version.plexus.archiver}pom.xml
Mavenorg.apache.apache.resources:apache-source-release-assembly-descriptor1.8pom.xml
All dependencies 59

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

RegistryPackageVersionRelation
Mavencom.puppycrawl.tools:checkstyle14.4.0direct
Mavenorg.apache.apache.resources:apache-source-release-assembly-descriptor1.8direct
Mavenorg.codehaus.plexus:plexus-archiver4.15.0direct
Mavencom.atlassian.maven.plugins:clover-maven-plugin4.1.10.1indirect
Mavencom.googlecode.maven-download-plugin:download-maven-plugin1.13.0indirect
Mavenio.github.download-maven-plugin:download-maven-plugin2.1.0indirect
Mavenorg.apache.felix:maven-bundle-plugin6.2.0indirect
Mavenorg.apache.maven.plugins:maven-antrun-plugin3.2.0indirect
Mavenorg.apache.maven.plugins:maven-archetype-plugin3.4.1indirect
Mavenorg.apache.maven.plugins:maven-assembly-plugin3.8.0indirect
Mavenorg.apache.maven.plugins:maven-checkstyle-plugin3.6.0indirect
Mavenorg.apache.maven.plugins:maven-clean-plugin3.5.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin—indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.16.0indirect
Mavenorg.apache.maven.plugins:maven-dependency-plugin3.11.0indirect
Mavenorg.apache.maven.plugins:maven-deploy-plugin—indirect
Mavenorg.apache.maven.plugins:maven-deploy-plugin3.2.0indirect
Mavenorg.apache.maven.plugins:maven-ear-plugin3.4.0indirect
Mavenorg.apache.maven.plugins:maven-ejb-plugin3.3.0indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin25indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin3.7.0indirect
Mavenorg.apache.maven.plugins:maven-failsafe-plugin—indirect
Mavenorg.apache.maven.plugins:maven-gpg-plugin—indirect
Mavenorg.apache.maven.plugins:maven-gpg-plugin3.2.8indirect
Mavenorg.apache.maven.plugins:maven-help-plugin3.5.2indirect
Mavenorg.apache.maven.plugins:maven-install-plugin3.2.0indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin3.5.1indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin—indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin3.12.0indirect
Mavenorg.apache.maven.plugins:maven-jxr-plugin3.6.0indirect
Mavenorg.apache.maven.plugins:maven-plugin-plugin3.16.0indirect
Mavenorg.apache.maven.plugins:maven-pmd-plugin3.28.0indirect
Mavenorg.apache.maven.plugins:maven-rar-plugin3.1.0indirect
Mavenorg.apache.maven.plugins:maven-release-plugin3.3.1indirect
Mavenorg.apache.maven.plugins:maven-resources-plugin3.5.0indirect
Mavenorg.apache.maven.plugins:maven-shade-plugin3.2.4indirect
Mavenorg.apache.maven.plugins:maven-site-plugin3.22.0indirect
Mavenorg.apache.maven.plugins:maven-source-plugin—indirect
Mavenorg.apache.maven.plugins:maven-source-plugin3.4.0indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin—indirect
Mavenorg.apache.maven.plugins:maven-surefire-report-plugin—indirect
Mavenorg.apache.maven.plugins:maven-war-plugin3.5.1indirect
Mavenorg.codehaus.mojo:build-helper-maven-plugin3.8.0indirect
Mavenorg.codehaus.mojo:buildnumber-maven-plugin—indirect
Mavenorg.codehaus.mojo:buildnumber-maven-plugin3.4.0indirect
Mavenorg.codehaus.mojo:cobertura-maven-plugin2.7indirect
Mavenorg.codehaus.mojo:exec-maven-plugin3.7.0indirect
Mavenorg.codehaus.mojo:findbugs-maven-plugin3.0.5indirect
Mavenorg.codehaus.mojo:javancss-maven-plugin2.1indirect
Mavenorg.codehaus.mojo:license-maven-plugin2.9.0indirect
Mavenorg.codehaus.mojo:versions-maven-plugin2.25.1indirect
Mavenorg.eclipse.m2e:lifecycle-mapping1.0.0indirect
Mavenorg.jboss.maven.plugins:maven-injection-plugin1.0.2indirect
Mavenorg.sonarsource.scanner.maven:sonar-maven-plugin5.8.0.7211indirect
Mavenorg.sonatype.central:central-publishing-maven-plugin—indirect
Mavenorg.sonatype.central:central-publishing-maven-plugin0.12.0indirect
Mavenorg.sonatype.plugins:nxrm3-maven-plugin—indirect
Mavenorg.sonatype.plugins:nxrm3-maven-plugin1.0.13indirect
Mavenorg.zanata:zanata-maven-plugin4.6.2indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 48 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 11 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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