Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 12:17 UTC

streamnative / pulsar-function-go

The StreamNative Go SDK for Pulsar Functions

Go · ShellNo license detected★ 0 stars⑂ 0 forkssince Mar 2024View on GitHub ↗

streamnative/pulsar-function-go holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (69/100) and lowest on Community & Adoption (4/100). It was last updated 93 days ago. A single contributor accounts for most of its recent work.

overall / 100

Weak

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.

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)

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

Ownership

StreamNativeOrganization · verified domain

247 followers117 public repossince Oct 2018

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
Go	github.com/streamnative/pulsar-function-go	v0.4.0	-	4	96 days ago

Metrics by category

Vitality

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

46Weak · 21% of overall

Development activity

24At Risk

How it's scored

9.9/36	Push recency — last push 93 days ago
3.5/36	Commit cadence — 5/52 weeks with commits
10.8/18	Commit volume — 15 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	15
human_commit_share	—
days_since_last_push	93
active_weeks_last_year	5

Release discipline

78Good

How it's scored

16.2/27	Ships releases — 4 version tags (no GitHub releases)
27/36	Release recency — latest release 96 days ago
27/27	Release cadence — a release every ~15.3 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	4
latest_release_tag	v0.4.0
releases_from_tags	yes
days_since_latest_release	96
mean_days_between_releases	15.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?

4Critical · 17% of overall

Popularity & adoption

6Critical

How it's scored

0/60	Stars — 0 stars
0/25	Forks — 0 forks
5.6/15	Watchers — 11 watchers

Inputs used

forks	0
stars	0
watchers	11
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

1Critical

How it's scored

0/22.5	README
0/22.5	License — no license file detected
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	no
has_license	no
readme_badges	—
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?

69Good · 23% of overall

Maintainer resilience (bus factor)

16Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
1.3/22.5	Commit distribution — top contributor authored 94% of commits
2.7/13.5	Contributor breadth — 2 contributors
3/10	OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3

Inputs used

bus_factor	1
contributors_sampled	2
top_contributor_share	0.944

Issue & PR responsiveness

93Exceptional

How it's scored

0/42	Issue resolution — no issues or no data
30/30	PR acceptance — 6/6 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15	OpenSSF Scorecard: Code-Review — Found 6/7 approved changesets -- score normalized to 8

Inputs used

merged_prs	6
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	—
closed_unmerged_prs	0
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

92Excellent

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
17.2/25	Owner reach — 247 followers of streamnative
25/25	Track record — 117 public repos, account ~7 yr old

Inputs used

followers	247
owner_type	Organization
is_verified	yes
owner_login	streamnative
public_repos	117
account_age_days	2,911

Package maintenance

92Excellent

How it's scored

25/25	Published & resolvable — 1 package(s) on go
35/35	Publish recency — latest publish 96 days ago
12/20	Version history — 4 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	github.com/streamnative/pulsar-function-go
ecosystems	go
any_deprecated	no
min_days_since_publish	96

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall

Engineering practices

64Moderate

How it's scored

24/24	CI workflows — 1 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
16/20	OpenSSF Scorecard: CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

20At Risk

How it's scored

0/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	no
has_docs_dir	no
has_description	yes

Security

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

42Weak · 16% of overall

Security posture

40Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2/2.5	CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5	Code-Review — Found 6/7 approved changesets -- score normalized to 8
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
0/2.5	License — license file not 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 — dependency not pinned by hash detected -- score normalized to 0
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
7.5/7.5	Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5	Vulnerabilities — 28 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	15
scorecard_version	v5.5.0
checks_inconclusive	3
scorecard_aggregate	4

Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

48Weak

How it's scored

8/35	Direct dependencies free of known advisories — 2 affected: google.golang.org/grpc v1.62.0 (critical 9.1), google.golang.org/protobuf v1.32.0 (high 7.5)
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
28.3/40	No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 959 days ago

Inputs used

source	osv
advisories	38
affected_packages	5
assessed_packages	10
unassessed_packages	0
affected_by_severity	critical 1, high 1, moderate 1, unknown 2
direct_affected_packages	2

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 10 resolved dependencies against OSV. 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.

58Moderate · 4% of overall

Agent context & guidance

1Critical

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	—

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

68Good

How it's scored

12.6/18	One-command bootstrap — examples/go.mod, go.mod (toolchain convention, no task runner)
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — Go (statically typed)
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no data
0/8	Automated maintenance — no data
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	yes
lockfiles	go.sum
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	—
toolchain_manifests	examples/go.mod, go.mod
dependency_bot_commit_share	—

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — Go (statically typed)
55/55	Manageable file sizes — 0/21 source files over 60KB

Inputs used

primary_language	Go
largest_source_bytes	43,634
source_files_sampled	21
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

40/40	API schema (OpenAPI/GraphQL/proto) — context.proto
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
api_schema_files	context.proto
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

0GitHub stars

2contributors

15commits, last 12 months

93days since last push

4releases

1bus factor

0open issues

Gopackage ecosystems

More detail

OpenSSF Scorecard 4.0 / 10

4.0aggregate

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-21 12:17 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal 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
8	CI-Tests	5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
8	Code-Review	Found 6/7 approved changesets -- score normalized to 8
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
0	License	license file not 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
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
10	Token-Permissions	GitHub workflow tokens follow principle of least privilege
0	Vulnerabilities	28 existing vulnerabilities detected

Direct dependencies 4

Registry	Package	Version constraint	Manifest
Go	github.com/golang/protobuf	`v1.5.3`	go.mod
Go	github.com/sirupsen/logrus	`v1.9.3`	go.mod
Go	google.golang.org/grpc	`v1.62.0`	go.mod
Go	google.golang.org/protobuf	`v1.32.0`	go.mod

All dependencies 10

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

Registry	Package	Version	Relation
Go	github.com/golang/protobuf	`v1.5.3`	direct
Go	github.com/sirupsen/logrus	`v1.9.3`	direct
Go	google.golang.org/grpc	`v1.62.0`	direct
Go	google.golang.org/protobuf	`v1.32.0`	direct
Go	github.com/streamnative/pulsar-function-go	`0.0.0`	indirect
Go	github.com/stretchr/testify	`1.8.4`	indirect
Go	golang.org/x/net	`v0.20.0`	indirect
Go	golang.org/x/sys	`v0.16.0`	indirect
Go	golang.org/x/text	`v0.14.0`	indirect
Go	google.golang.org/genproto/googleapis/rpc	`v0.0.0-20240123012728-ef4313101c80`	indirect

Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 10 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 2 are direct.

Package	Version	Relation	Severity	Advisories	Fixed in
google.golang.org/grpc	`v1.62.0`	direct	critical	10	`1.85.0-dev.0.20260825072537-93e31b48545e`
google.golang.org/protobuf	`v1.32.0`	direct	high	2	`1.33.0`
golang.org/x/net	`v0.20.0`	indirect	moderate	23	`1.27.2`
golang.org/x/sys	`v0.16.0`	indirect	unknown	1	`0.44.0`
golang.org/x/text	`v0.14.0`	indirect	unknown	2	`0.41.0`

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 — Go.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

More detail

Feedback

Related records