Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 19:33 UTC

thingspect / proto

Thingspect Proto (Protobuf + gRPC definitions and example code)

Dart · PythonISC★ 2 stars⑂ 0 forkssince Nov 2020View on GitHub ↗
KindNetwork serviceLibraryhow this is determined

thingspect/proto holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on Vitality (65/100) and lowest on Engineering Quality (17/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ThingspectOrganization · verified domain
0 followers2 public repossince Sep 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/thingspect/proto/gov1.1.22-5610 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
4.2/36Commit cadence — 6/52 weeks with commits
11.9/18Commit volume — 20 commits in the last year
10/10OpenSSF Scorecard: Maintained — 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year20
human_commit_share1
days_since_last_push10
active_weeks_last_year6
How it's scored
16.2/27Ships releases — 50 version tags (no GitHub releases)
36/36Release recency — latest release 10 days ago
19.8/27Release cadence — a release every ~56 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count50
latest_release_tagv1.1.22
releases_from_tagsyes
days_since_latest_release10
mean_days_between_releases56
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?

24At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (ISC)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
29.8/30PR acceptance — 142/143 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/15 approved changesets -- score normalized to 0
Inputs used
merged_prs142
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio—
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
0/25Owner reach — 0 followers of thingspect
15.4/25Track record — 2 public repos, account ~5 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedyes
owner_loginthingspect
public_repos2
account_age_days2,185

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 10 days ago
20/20Version history — 56 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/thingspect/proto/go
ecosystemsgo
any_deprecatedno
min_days_since_publish10

Engineering Quality

Are baseline engineering and documentation practices in place?

17Critical · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 15 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
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?

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/15 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 12 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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages9
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 9 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.

55Moderate · 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://docs.docker.com/llms.txt)
26.7/40Legible commit history — 50 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.docker.com/llms.txt
legible_history_share0.5
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile, cpp/Makefile, dart/Makefile, go/Makefile, php/Makefile, python/Makefile, ruby/Makefile
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Dart (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, cpp/Makefile, dart/Makefile, go/Makefile, php/Makefile, python/Makefile, ruby/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Dart (statically typed)
51/55Manageable file sizes — 20/273 source files over 60KB
Inputs used
primary_languageDart
largest_source_bytes329,735
source_files_sampled273
oversized_source_files20
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — protobuf/api/thingspect_alert.proto, protobuf/api/thingspect_datapoint.proto, protobuf/api/thingspect_device.proto, protobuf/api/thingspect_event.proto, protobuf/api/thingspect_openapi-templ.proto, protobuf/api/thingspect_org.proto, protobuf/api/thingspect_role.proto, protobuf/api/thingspect_rule_alarm.proto, protobuf/api/thingspect_session.proto, protobuf/api/thingspect_status.proto, protobuf/api/thingspect_tag.proto, protobuf/api/thingspect_user.proto, protobuf/common/thingspect_datapoint.proto, protobuf/mqtt/thingspect_payload.proto
0/20MCP server
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_filesprotobuf/api/thingspect_alert.proto, protobuf/api/thingspect_datapoint.proto, protobuf/api/thingspect_device.proto, protobuf/api/thingspect_event.proto, protobuf/api/thingspect_openapi-templ.proto, protobuf/api/thingspect_org.proto, protobuf/api/thingspect_role.proto, protobuf/api/thingspect_rule_alarm.proto, protobuf/api/thingspect_session.proto, protobuf/api/thingspect_status.proto, protobuf/api/thingspect_tag.proto, protobuf/api/thingspect_user.proto, protobuf/common/thingspect_datapoint.proto, protobuf/mqtt/thingspect_payload.proto
interfaces_expected_ofnetwork-service

Key facts

2GitHub stars
1contributors
20commits, last 12 months
10days since last push
50releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 3.9 / 10
3.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-09-18 19:32 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
0CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/15 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 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
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Gobuf.build/gen/go/bufbuild/protovalidate/protocolbuffers/gov1.36.12-20260825204119-511051f7f437.2go/go.mod
Gogithub.com/grpc-ecosystem/grpc-gateway/v2v2.30.0go/go.mod
Gogoogle.golang.org/genproto/googleapis/apiv0.0.0-20260908043556-f8649ddbbfe6go/go.mod
Gogoogle.golang.org/grpcv1.83.2go/go.mod
Gogoogle.golang.org/protobufv1.36.12go/go.mod
All dependencies 9

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

RegistryPackageVersionRelation
Gobuf.build/gen/go/bufbuild/protovalidate/protocolbuffers/gov1.36.12-20260825204119-511051f7f437.2direct
Gogithub.com/grpc-ecosystem/grpc-gateway/v2v2.30.0direct
Gogoogle.golang.org/genproto/googleapis/apiv0.0.0-20260908043556-f8649ddbbfe6direct
Gogoogle.golang.org/grpcv1.83.2direct
Gogoogle.golang.org/protobufv1.36.12direct
Gogolang.org/x/netv0.58.0indirect
Gogolang.org/x/sysv0.48.0indirect
Gogolang.org/x/textv0.41.0indirect
Gogoogle.golang.org/genproto/googleapis/rpcv0.0.0-20260908043556-f8649ddbbfe6indirect
Dependency advisories 0

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

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