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

smallrye / smallrye-mutiny-zero

Zero-dependency Reactive Streams publishers library

JavaApache-2.0★ 24 stars⑂ 5 forkssince Jun 2021View on GitHub ↗

smallrye/smallrye-mutiny-zero holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (85/100) and lowest on Community & Adoption (47/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

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.

80
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 68 is calibrated to 80 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.reactive:mutiny-zero1.3.1-1745 days ago
Mavenio.smallrye.reactive:mutiny-zero-flow-adapters1.3.1-1045 days ago
Mavenio.smallrye.reactive:mutiny-zero-vertx-publishers1.3.1-945 days ago
Mavenio.smallrye.reactive:mutiny-zero-reactive-streams-junit5-tck1.3.1-1345 days ago

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 5 days ago
29.1/36Commit cadence — 42/52 weeks with commits
17.6/18Commit volume — 89 commits in the last year
10/10OpenSSF Scorecard: Maintained — 29 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year89
human_commit_share0.12
days_since_last_push5
active_weeks_last_year42
How it's scored
27/27Ships releases — 15 releases published
27/36Release recency — latest release 144 days ago
12.6/27Release cadence — a release every ~157.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count15
latest_release_tag1.2.1
releases_from_tagsno
days_since_latest_release144
mean_days_between_releases157.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?

47Weak · 17% of overall
How it's scored
22.1/60Stars — 24 stars
5/25Forks — 5 forks
0/15Watchers — 1 watchers
Inputs used
forks5
stars24
watchers1
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_badges2
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?

72Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.3/22.5Commit distribution — top contributor authored 85% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.854
How it's scored
42/42Issue resolution — 100% of issues closed
26.7/30PR acceptance — 326/366 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 1/9 approved changesets -- score normalized to 1
Inputs used
merged_prs326
open_issues0
closed_issues9
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs40
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
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 45 days ago
20/20Version history — 17 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesio.smallrye.reactive:mutiny-zero, io.smallrye.reactive:mutiny-zero-flow-adapters, io.smallrye.reactive:mutiny-zero-vertx-publishers, io.smallrye.reactive:mutiny-zero-reactive-streams-junit5-tck
ecosystemsmaven
any_deprecatedno
min_days_since_publish45

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 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
18/20OpenSSF Scorecard: CI-Tests — 25 out of 26 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://smallrye.io/smallrye-mutiny-zero/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://smallrye.io/smallrye-mutiny-zero/
docs_sitehttps://smallrye.io/smallrye-mutiny-zero/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 25 out of 26 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 1/9 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 11 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 — 29 commit(s) and 1 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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.4
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_packages1
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.reactive:mutiny-zero@1.3.1 runtime dependency closure — what installing the published package pulls in — 1 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://smallrye.io/llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtyes
llms_txt_urlhttps://smallrye.io/llms.txt
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
12.6/18One-command bootstrap — mutiny-zero-flow-adapters/pom.xml, mutiny-zero-reactive-streams-junit5-tck/pom.xml, mutiny-zero-vertx-publishers/pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 80 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
lockfilesuv.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsmutiny-zero-flow-adapters/pom.xml, mutiny-zero-reactive-streams-junit5-tck/pom.xml, mutiny-zero-vertx-publishers/pom.xml, mutiny-zero/pom.xml, pom.xml
dependency_bot_commit_share0.8
How it's scored
45/45Type-checkable code — Java (statically typed)
55/55Manageable file sizes — 0/99 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes43,166
source_files_sampled99
oversized_source_files0

Key facts

24GitHub stars
5contributors
89commits, last 12 months
5days since last push
15releases
1bus factor
0open issues
Maven, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'mutiny-zero' from its registry

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
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.

12345512022-092024-092026-10
Major 1Minor 3Patch 2

Each point covers 4 days.

OpenSSF Scorecard 5.4 / 10
5.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 08:19 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests25 out of 26 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/9 approved changesets -- score normalized to 1
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained29 commit(s) and 1 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 16
RegistryPackageVersion constraintManifest
Mavenorg.reactivestreams:reactive-streams—mutiny-zero-flow-adapters/pom.xml
Mavenorg.jspecify:jspecify—mutiny-zero-flow-adapters/pom.xml
Mavenorg.reactivestreams:reactive-streams—mutiny-zero-reactive-streams-junit5-tck/pom.xml
Mavenio.smallrye.reactive:mutiny-zero${project.version}mutiny-zero-vertx-publishers/pom.xml
Mavenio.vertx:vertx-core${vertx.version}mutiny-zero-vertx-publishers/pom.xml
Mavenorg.jspecify:jspecify—mutiny-zero-vertx-publishers/pom.xml
Mavenorg.jspecify:jspecify—mutiny-zero/pom.xml
Mavenorg.jspecify:jspecify${jspecify.version}pom.xml
Mavenorg.reactivestreams:reactive-streams${reactive-streams.version}pom.xml
Mavenorg.revapi:revapi-java${revapi-java.version}pom.xml
Mavenorg.revapi:revapi-reporter-json${revapi-reporter-json.version}pom.xml
Mavenorg.revapi:revapi-reporter-text${revapi-reporter-text.version}pom.xml
PyPImkdocs-material>=9.5.48pyproject.toml
PyPImkdocs>=1.6.1pyproject.toml
PyPImkdocs-macros-plugin>=1.3.7pyproject.toml
PyPImike>=2.1.3pyproject.toml
All dependencies 73

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

RegistryPackageVersionRelation
Mavenio.smallrye.reactive:mutiny-zero1.3.2-SNAPSHOTdirect
Mavenio.vertx:vertx-core—direct
Mavenorg.jspecify:jspecify—direct
Mavenorg.jspecify:jspecify1.0.1direct
Mavenorg.reactivestreams:reactive-streams—direct
Mavenorg.reactivestreams:reactive-streams1.0.4direct
Mavenorg.revapi:revapi-java0.28.4direct
Mavenorg.revapi:revapi-reporter-json0.5.1direct
Mavenorg.revapi:revapi-reporter-text0.15.1direct
PyPImike2.2.0direct
PyPImkdocs1.6.1direct
PyPImkdocs-macros-plugin1.5.0direct
PyPImkdocs-material9.7.7direct
Mavenbiz.aQute.bnd:bnd-maven-plugin—indirect
Mavench.qos.logback:logback-classic—indirect
Mavench.qos.logback:logback-classic1.6.5indirect
Mavenio.smallrye.reactive:mutiny—indirect
Mavenio.smallrye.reactive:mutiny3.3.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin—indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin—indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin—indirect
Mavenorg.apache.maven.plugins:maven-source-plugin—indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin—indirect
Mavenorg.assertj:assertj-core—indirect
Mavenorg.assertj:assertj-core3.27.7indirect
Mavenorg.awaitility:awaitility—indirect
Mavenorg.awaitility:awaitility4.3.0indirect
Mavenorg.junit.jupiter:junit-jupiter—indirect
Mavenorg.junit.jupiter:junit-jupiter6.1.3indirect
Mavenorg.junit.support:testng-engine—indirect
Mavenorg.junit.support:testng-engine1.1.0indirect
Mavenorg.junit.vintage:junit-vintage-engine—indirect
Mavenorg.junit.vintage:junit-vintage-engine6.1.3indirect
Mavenorg.reactivestreams:reactive-streams-tck—indirect
Mavenorg.reactivestreams:reactive-streams-tck1.0.4indirect
Mavenorg.reactivestreams:reactive-streams-tck-flow—indirect
Mavenorg.reactivestreams:reactive-streams-tck-flow1.0.4indirect
Mavenorg.revapi:revapi-maven-plugin0.15.1indirect
Mavenorg.testng:testng—indirect
Mavenorg.testng:testng7.12.0indirect
PyPIbabel2.18.0indirect
PyPIbackrefs8.0indirect
PyPIcertifi2026.7.22indirect
PyPIcharset-normalizer3.4.9indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIghp-import2.1.0indirect
PyPIhjson3.1.0indirect
PyPIidna3.18indirect
PyPIjinja23.1.6indirect
PyPImarkdown3.10.3indirect
PyPImarkupsafe3.0.3indirect
PyPImergedeep1.3.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImutiny-zero999indirect
PyPIpackaging26.3indirect
PyPIpaginate0.5.7indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.2indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions11.0.1indirect
PyPIpyparsing3.3.2indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrequests2.34.2indirect
PyPIsix1.17.0indirect
PyPIsuper-collections0.6.2indirect
PyPItermcolor3.3.0indirect
PyPIurllib32.8.0indirect
PyPIverspec0.1.0indirect
PyPIwatchdog6.0.0indirect
Dependency advisories 0

Installing maven:io.smallrye.reactive:mutiny-zero@1.3.1 pulls in 1 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.