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

IOTechSystems / go-mod-central-ext

Edge Central extension go module

GoNo license detected★ 0 stars⑂ 1 forksince Nov 2024View on GitHub ↗

IOTechSystems/go-mod-central-ext holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (80/100) and lowest on Community & Adoption (13/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

overall / 100

Moderate

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

Ownership

IOTechOrganization

20 followers60 public repossince Aug 2017

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/IOTechSystems/go-mod-central-ext/v4	v4.0.107	-	108	15 days ago

Metrics by category

Vitality

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

73Good · 21% of overall

Development activity

87Excellent

How it's scored

36/36	Push recency — last push 2 days ago
24.2/36	Commit cadence — 35/52 weeks with commits
17.2/18	Commit volume — 82 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	82
human_commit_share	0.71
days_since_last_push	2
active_weeks_last_year	35

Release discipline

52Moderate

How it's scored

27/27	Ships releases — 1 releases published
7.2/36	Release recency — latest release 499 days ago
12.6/27	Release cadence — cadence unknown (single release)
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	1
latest_release_tag	v4.0.48
releases_from_tags	no
days_since_latest_release	499
mean_days_between_releases	—

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?

13Critical · 17% of overall

Popularity & adoption

3Critical

How it's scored

0/60	Stars — 0 stars
0/25	Forks — 1 forks
2.7/15	Watchers — 4 watchers

Inputs used

forks	1
stars	0
watchers	4
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

25At Risk

How it's scored

22.5/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	yes
has_license	no
readme_badges	0
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?

72Good · 23% of overall

Maintainer resilience (bus factor)

56Moderate

How it's scored

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

Inputs used

bus_factor	2
contributors_sampled	7
top_contributor_share	0.484

Issue & PR responsiveness

78Good

How it's scored

0/42	Issue resolution — no issues or no data
20.2/30	PR acceptance — 109/162 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15	OpenSSF Scorecard: Code-Review — all changesets reviewed

Inputs used

merged_prs	109
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	3
prs_decided_30d	3
issue_closed_ratio	—
closed_unmerged_prs	53
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

64Moderate

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
9.5/25	Owner reach — 20 followers of IOTechSystems
25/25	Track record — 60 public repos, account ~9 yr old

Inputs used

followers	20
owner_type	Organization
is_verified	no
owner_login	IOTechSystems
public_repos	60
account_age_days	3,300

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	github.com/IOTechSystems/go-mod-central-ext/v4
ecosystems	go
any_deprecated	no
min_days_since_publish	15

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall

Engineering practices

74Good

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

50Moderate

How it's scored

30/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	yes
has_docs_dir	no
has_description	yes

Security

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

61Moderate · 16% of overall

Security posture

51Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
1.2/2.5	CI-Tests — 8 out of 16 merged PRs checked by a CI test -- score normalized to 5
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5	Code-Review — all changesets reviewed
2.5/2.5	Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
0/2.5	License — license file not detected
7.5/7.5	Maintained — 21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
3.8/7.5	Vulnerabilities — 5 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	5.1

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

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	5
affected_packages	2
assessed_packages	30
unassessed_packages	0
affected_by_severity	unknown 2
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 30 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.

80Excellent · 4% of overall

Agent context & guidance

85Excellent

How it's scored

45/45	Agent instructions — CLAUDE.md
0/15	Machine-readable docs (llms.txt)
40/40	Legible commit history — 63 of 71 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.887
agent_instruction_files	CLAUDE.md
agent_instruction_max_bytes	2,091

Verify loop (build / test / typecheck)

80Excellent

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
11/11	Lint / format config — .golangci.yml
11/11	Static type checking — Go (statically typed)
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 29 of the last 100 commits are automated dependency updates
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	Makefile
has_devcontainer	no
has_linter_config	yes
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	go.mod
dependency_bot_commit_share	0.29

Code legibility for models

100Exceptional

How it's scored

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

Inputs used

primary_language	Go
largest_source_bytes	87,479
source_files_sampled	149
oversized_source_files	1

Machine-readable interfaces

50Moderate

How it's scored

40/40	API schema (OpenAPI/GraphQL/proto) — pkg/protobuf/event.proto, pkg/sparkplug/protobuf/sparkplug_b.proto
0/20	MCP server — not applicable to this kind of software
0/40	Runnable examples

Inputs used

example_dirs	—
has_mcp_signal	no
api_schema_files	pkg/protobuf/event.proto, pkg/sparkplug/protobuf/sparkplug_b.proto
interfaces_expected_of	—

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

Key facts

0GitHub stars

7contributors

82commits, last 12 months

2days since last push

1releases

2bus factor

0open issues

Gopackage ecosystems

More detail

OpenSSF Scorecard 5.1 / 10

5.1aggregate

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-09-10 17:09 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
5	CI-Tests	8 out of 16 merged PRs checked by a CI test -- score normalized to 5
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
10	Code-Review	all changesets reviewed
10	Contributors	project has 3 contributing companies or organizations -- score normalized to 10
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
0	License	license file not detected
10	Maintained	21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
5	Vulnerabilities	5 existing vulnerabilities detected

Direct dependencies 9

Registry	Package	Version constraint	Manifest
Go	github.com/edgexfoundry/go-mod-core-contracts/v4	`v4.1.0-dev.45`	go.mod
Go	github.com/go-playground/validator/v10	`v10.30.3`	go.mod
Go	github.com/google/uuid	`v1.6.0`	go.mod
Go	github.com/spf13/cast	`v1.10.0`	go.mod
Go	github.com/stretchr/testify	`v1.12.1`	go.mod
Go	github.com/vmihailenco/msgpack/v5	`v5.4.1`	go.mod
Go	github.com/xuri/excelize/v2	`v2.11.0`	go.mod
Go	go.einride.tech/can	`v0.17.0`	go.mod
Go	google.golang.org/protobuf	`v1.36.12`	go.mod

All dependencies 30

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

Registry	Package	Version	Relation
Go	github.com/edgexfoundry/go-mod-core-contracts/v4	`v4.1.0-dev.45`	direct
Go	github.com/go-playground/validator/v10	`v10.30.3`	direct
Go	github.com/google/uuid	`v1.6.0`	direct
Go	github.com/spf13/cast	`v1.10.0`	direct
Go	github.com/stretchr/testify	`v1.12.1`	direct
Go	github.com/vmihailenco/msgpack/v5	`v5.4.1`	direct
Go	github.com/xuri/excelize/v2	`v2.11.0`	direct
Go	go.einride.tech/can	`v0.17.0`	direct
Go	google.golang.org/protobuf	`v1.36.12`	direct
Go	github.com/davecgh/go-spew	`v1.1.2-0.20180830191138-d8f796af33cc`	indirect
Go	github.com/fxamacker/cbor/v2	`v2.9.3`	indirect
Go	github.com/gabriel-vasile/mimetype	`v1.4.13`	indirect
Go	github.com/go-kit/log	`v0.2.1`	indirect
Go	github.com/go-logfmt/logfmt	`v0.5.1`	indirect
Go	github.com/go-playground/locales	`v0.14.1`	indirect
Go	github.com/go-playground/universal-translator	`v0.18.1`	indirect
Go	github.com/leodido/go-urn	`v1.4.0`	indirect
Go	github.com/richardlehane/mscfb	`v1.0.7`	indirect
Go	github.com/richardlehane/msoleps	`v1.0.6`	indirect
Go	github.com/stretchr/objx	`v0.5.3`	indirect
Go	github.com/tiendc/go-deepcopy	`v1.7.2`	indirect
Go	github.com/vmihailenco/tagparser/v2	`v2.0.0`	indirect
Go	github.com/x448/float16	`v0.8.4`	indirect
Go	github.com/xuri/efp	`v0.0.1`	indirect
Go	github.com/xuri/nfp	`v0.0.2-0.20250530014748-2ddeb826f9a9`	indirect
Go	go.yaml.in/yaml/v3	`v3.0.5`	indirect
Go	golang.org/x/crypto	`v0.53.0`	indirect
Go	golang.org/x/net	`v0.56.0`	indirect
Go	golang.org/x/sys	`v0.46.0`	indirect
Go	golang.org/x/text	`v0.38.0`	indirect

Dependency advisories 2

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

Package	Version	Relation	Severity	Advisories	Fixed in
golang.org/x/crypto	`v0.53.0`	indirect	unknown	4	`0.56.0`
golang.org/x/text	`v0.38.0`	indirect	unknown	1	`0.39.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