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

smallrye / smallrye-certificate-generator

Utilities to generated signed and self-signed certificates

JavaApache-2.0★ 5 stars⑂ 8 forkssince Jul 2024View on GitHub ↗
KindPluginLibraryhow this is determined

smallrye/smallrye-certificate-generator holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (79/100) and lowest on Community & Adoption (42/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

SmallRyeOrganization · verified domain
180 followers54 public repossince May 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenio.smallrye.certs:smallrye-certificate-generator1.1.3-1114 days ago
Mavenio.smallrye.certs:smallrye-private-key-pem-parser1.1.3-914 days ago
Mavenio.smallrye.certs:smallrye-certificate-generator-junit51.1.3-1114 days ago
Mavenio.smallrye.certs:smallrye-certificate-generator-maven-plugin1.1.3-1114 days ago

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
8.3/36Commit cadence — 12/52 weeks with commits
15.3/18Commit volume — 50 commits in the last year
10/10OpenSSF Scorecard: Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year50
human_commit_share0.48
days_since_last_push6
active_weeks_last_year12
How it's scored
27/27Ships releases — 10 releases published
36/36Release recency — latest release 14 days ago
19.8/27Release cadence — a release every ~91.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tag1.1.3
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases91.5
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?

42Weak · 17% of overall
How it's scored
9.8/60Stars — 5 stars
7/25Forks — 8 forks
0/15Watchers — 0 watchers
Inputs used
forks8
stars5
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.4/22.5Commit distribution — top contributor authored 90% of commits
10.8/13.5Contributor breadth — 8 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.895
How it's scored
29.4/42Issue resolution — 70% of issues closed
20/30PR acceptance — 64/96 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 6/17 approved changesets -- score normalized to 3
Inputs used
merged_prs64
open_issues3
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d4
issue_closed_ratio0.7
closed_unmerged_prs32
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
16.2/25Owner reach — 180 followers of smallrye
24.7/25Track record — 54 public repos, account ~8 yr old
Inputs used
followers180
owner_typeOrganization
is_verifiedyes
owner_loginsmallrye
public_repos54
account_age_days3,092

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 4 package(s) on maven
35/35Publish recency — latest publish 14 days ago
20/20Version history — 11 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesio.smallrye.certs:smallrye-certificate-generator, io.smallrye.certs:smallrye-private-key-pem-parser, io.smallrye.certs:smallrye-certificate-generator-junit5, io.smallrye.certs:smallrye-certificate-generator-maven-plugin
ecosystemsmaven
any_deprecatedno
min_days_since_publish14

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 19 out of 19 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

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?

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 19 out of 19 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
2.2/7.5Code-Review — Found 6/17 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 4 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
2.5/2.5License — license file detected
7.5/7.5Maintained — 23 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
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): 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
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no 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:io.smallrye.certs:smallrye-certificate-generator@1.1.3 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
32.2/40Legible commit history — 29 of 48 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.604
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — certificate-generator-junit5/pom.xml, certificate-generator-maven-plugin/pom.xml, certificate-generator/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
8/8Automated maintenance — 34 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_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestscertificate-generator-junit5/pom.xml, certificate-generator-maven-plugin/pom.xml, certificate-generator/pom.xml, pom.xml, private-key-pem-parser/pom.xml
dependency_bot_commit_share0.34
How it's scored
45/45Type-checkable code — Java (statically typed)
55/55Manageable file sizes — 0/49 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes25,636
source_files_sampled49
oversized_source_files0

Key facts

5GitHub stars
8contributors
50commits, last 12 months
6days since last push
10releases
1bus factor
3open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 8 ⇿
0Stars
8Forks
8Releases

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.

02468812024-082025-092026-09
Major 0Minor 2Patch 6

Each point covers 2 days.

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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:13 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests19 out of 19 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 6/17 approved changesets -- score normalized to 3
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 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
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
Mavenorg.junit.jupiter:junit-jupiter—certificate-generator-junit5/pom.xml
Mavenorg.junit.jupiter:junit-jupiter-api—certificate-generator-junit5/pom.xml
Mavenorg.junit.jupiter:junit-jupiter-params—certificate-generator-junit5/pom.xml
Mavenio.smallrye.certs:smallrye-certificate-generator${project.version}certificate-generator-junit5/pom.xml
Mavenio.smallrye.certs:smallrye-certificate-generator${project.version}certificate-generator-maven-plugin/pom.xml
Mavenorg.bouncycastle:bcprov-jdk18on—certificate-generator/pom.xml
Mavenorg.bouncycastle:bcpkix-jdk18on—certificate-generator/pom.xml
Mavenio.smallrye.common:smallrye-common-os${smallrye-common-constraint.version}certificate-generator/pom.xml
Mavencom.googlecode.plist:dd-plist${dd-plist.version}certificate-generator/pom.xml
Mavenorg.junit:junit-bom${junit-bom.version}pom.xml
Mavenorg.bouncycastle:bcprov-jdk18on${bouncycastle.version}pom.xml
Mavenorg.bouncycastle:bcpkix-jdk18on${bouncycastle.version}pom.xml
Mavenio.smallrye.common:smallrye-common-constraint${smallrye-common-constraint.version}private-key-pem-parser/pom.xml
Mavenio.vertx:vertx-core—private-key-pem-parser/pom.xml
All dependencies 26

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

RegistryPackageVersionRelation
Mavencom.googlecode.plist:dd-plist—direct
Mavenio.smallrye.certs:smallrye-certificate-generator999-SNAPSHOTdirect
Mavenio.smallrye.common:smallrye-common-constraint—direct
Mavenio.smallrye.common:smallrye-common-os—direct
Mavenio.vertx:vertx-core—direct
Mavenio.vertx:vertx-core5.2.0direct
Mavenorg.bouncycastle:bcpkix-jdk18on—direct
Mavenorg.bouncycastle:bcpkix-jdk18on1.86direct
Mavenorg.bouncycastle:bcprov-jdk18on—direct
Mavenorg.bouncycastle:bcprov-jdk18on1.86direct
Mavenorg.junit.jupiter:junit-jupiter—direct
Mavenorg.junit.jupiter:junit-jupiter-api—direct
Mavenorg.junit.jupiter:junit-jupiter-params—direct
Mavenorg.junit:junit-bom6.1.3direct
Mavenio.smallrye.certs:smallrye-private-key-pem-parser999-SNAPSHOTindirect
Mavenio.smallrye:jandex-maven-plugin3.5.3indirect
Mavennet.revelc.code:impsort-maven-plugin1.13.0indirect
Mavenorg.apache.maven.plugin-tools:maven-plugin-annotations—indirect
Mavenorg.apache.maven.plugin-tools:maven-plugin-annotations3.16.0indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin3.12.0indirect
Mavenorg.apache.maven.plugins:maven-plugin-plugin—indirect
Mavenorg.apache.maven:maven-plugin-api—indirect
Mavenorg.apache.maven:maven-plugin-api3.9.16indirect
Mavenorg.assertj:assertj-core—indirect
Mavenorg.assertj:assertj-core3.27.7indirect
Mavenorg.junit.jupiter:junit-jupiter-engine—indirect
Dependency advisories 0

Installing maven:io.smallrye.certs:smallrye-certificate-generator@1.1.3 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 statistics — Maven.