Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-30 04:05 UTC

streamnative / pulsar-rs

Rust Client library for Apache Pulsar

RustCustom license★ 411 stars⑂ 145 forkssince Oct 2018View on GitHub ↗

streamnative/pulsar-rs holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (79/100) and lowest on Security (43/100). It was last updated 5 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

StreamNativeOrganization · verified domain
243 followers115 public repossince Oct 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iopulsar6.9.0134,263445 days agoapiclientpulsar

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
15.2/36Commit cadence22/52 weeks with commits
13.9/18Commit volume34 commits in the last year
2/10OpenSSF Scorecard: Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year34
human_commit_share1
days_since_last_push5
active_weeks_last_year22
How it's scored
27/27Ships releases24 releases published
36/36Release recencylatest release 5 days ago
19.8/27Release cadencea release every ~61.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count24
latest_release_tagv6.9.0
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases61.3
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?

64Moderate · 17% of overall
How it's scored
42.4/60Stars411 stars
18/25Forks145 forks
8.5/15Watchers35 watchers
Inputs used
forks145
stars411
watchers35
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
68.4/80Monthly downloads134,263 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespulsar
dependents
ecosystemscrates
total_downloads2,311,982
monthly_downloads134,263
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

79Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.5/22.5Commit distributiontop contributor authored 44% of commits
13.5/13.5Contributor breadth70 contributors
10/10OpenSSF Scorecard: Contributorsproject has 20 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled70
top_contributor_share0.443
How it's scored
27.4/42Issue resolution65% of issues closed
25.9/30PR acceptance184/213 decided PRs merged
6.5/13Newcomer PR acceptance1/2 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 25/30 approved changesets -- score normalized to 8
Inputs used
merged_prs184
open_issues68
closed_issues128
prs_merged_7d1
prs_decided_7d2
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.653
closed_unmerged_prs29
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
17.2/25Owner reach243 followers of streamnative
25/25Track record115 public repos, account ~7 yr old
Inputs used
followers243
owner_typeOrganization
is_verifiedyes
owner_loginstreamnative
public_repos115
account_age_days2,859

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 5 days ago
20/20Version history44 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespulsar
ecosystemscrates
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
16/16Linter configrustfmt.toml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/pulsar
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicspulsar, rust
has_wikino
homepage
docs_sitehttps://docs.rs/pulsar
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

43Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 25/30 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 20 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
1.5/7.5Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history85 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.85
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml (toolchain convention, no task runner)
0/22Automated tests
11/11Lint / format configrustfmt.toml
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
50.4/55Manageable file sizes3/36 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes75,250
source_files_sampled36
oversized_source_files3
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)PulsarApi.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesPulsarApi.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

411GitHub stars
70contributors
34commits, last 12 months
5days since last push
24releases
2bus factor
68open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 145 ⇿
0Stars
145Forks
23Releases

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.

025507510012515013832019-042022-122026-08
Major 3Minor 10Patch 10

Each point covers 7 days.

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-30 04:04 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 25/30 approved changesets -- score normalized to 8
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
2Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
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 39
RegistryPackageVersion constraintManifest
crates.ioasync-channel^2.3.1Cargo.toml
crates.ioasync-trait^0.1.88Cargo.toml
crates.ioasync-std^1.13.1Cargo.toml
crates.ioasync-native-tls^0.5.0Cargo.toml
crates.ioasynchronous-codec^0.7.0Cargo.toml
crates.iobytes^1.9.0Cargo.toml
crates.iobase640.22Cargo.toml
crates.iochrono^0.4.41Cargo.toml
crates.iocrc^3.3.0Cargo.toml
crates.iodata-url^0.3.1Cargo.toml
crates.ioflate2^1.1.1Cargo.toml
crates.iofutures^0.3.31Cargo.toml
crates.iofutures-rustls^0.26.0Cargo.toml
crates.iolog^0.4.27Cargo.toml
crates.iolz4^1.28.0Cargo.toml
crates.iomurmur30.5.2Cargo.toml
crates.ionative-tls^0.2.12Cargo.toml
crates.ionom^7.1.3Cargo.toml
crates.ioopenidconnect^4.0.0Cargo.toml
crates.iooauth2^5.0.0Cargo.toml
crates.iopem^3.0.4Cargo.toml
crates.ioprost^0.13.4Cargo.toml
crates.ioprost-derive^0.13.4Cargo.toml
crates.iorand^0.8.5Cargo.toml
crates.ioreqwest0.13Cargo.toml
crates.ioregex^1.11.1Cargo.toml
crates.iorustls^0.23.27Cargo.toml
crates.iosnap^1.1.1Cargo.toml
crates.ioserde^1.0.219Cargo.toml
crates.ioserde_json^1.0.140Cargo.toml
crates.iotokio^1.45.0Cargo.toml
crates.iotokio-util^0.7.15Cargo.toml
crates.iotokio-rustls0.26.2Cargo.toml
crates.iotokio-native-tls^0.3.1Cargo.toml
crates.iotracing^0.1.41Cargo.toml
crates.iourl^2.5.4Cargo.toml
crates.iouuid^1.16.0Cargo.toml
crates.iowebpki-roots^1.0.0Cargo.toml
crates.iozstd^0.13.2Cargo.toml
All dependencies 43

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

RegistryPackageVersionRelation
crates.ioasync-channeldirect
crates.ioasync-native-tlsdirect
crates.ioasync-stddirect
crates.ioasync-traitdirect
crates.ioasynchronous-codecdirect
crates.iobase64direct
crates.iobytesdirect
crates.iochronodirect
crates.iocrcdirect
crates.iodata-urldirect
crates.ioflate2direct
crates.iofuturesdirect
crates.iofutures-rustlsdirect
crates.iologdirect
crates.iolz4direct
crates.iomurmur3direct
crates.ionative-tlsdirect
crates.ionomdirect
crates.iooauth2direct
crates.ioopenidconnectdirect
crates.iopemdirect
crates.ioprostdirect
crates.ioprost-derivedirect
crates.ioranddirect
crates.ioregexdirect
crates.ioreqwestdirect
crates.iorustlsdirect
crates.ioserdedirect
crates.ioserde_jsondirect
crates.iosnapdirect
crates.iotokiodirect
crates.iotokio-native-tlsdirect
crates.iotokio-rustlsdirect
crates.iotokio-utildirect
crates.iotracingdirect
crates.iourldirect
crates.iouuiddirect
crates.iowebpki-rootsdirect
crates.iozstddirect
crates.ioassert_matchesindirect
crates.ioenv_loggerindirect
crates.ioprost-buildindirect
crates.ioprotobuf-srcindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 statisticscrates.io.