Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 09:10 UTC

LINBIt / golinstor

golang bindings for linstor

GoApache-2.0★ 14 stars⑂ 11 forkssince Jan 2018View on GitHub ↗

LINBIt/golinstor holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Vitality (76/100) and lowest on Engineering Quality (38/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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

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

Ownership

LINBITOrganization
175 followers94 public repossince Dec 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/LINBIT/golinstorv0.64.1-1073 days ago

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
9.7/36Commit cadence14/52 weeks with commits
12.6/18Commit volume24 commits in the last year
10/10OpenSSF Scorecard: Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year24
human_commit_share
days_since_last_push1
active_weeks_last_year14
How it's scored
16.2/27Ships releases99 version tags (no GitHub releases)
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~31.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count99
latest_release_tagv0.64.1
releases_from_tagsyes
days_since_latest_release3
mean_days_between_releases31.5
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?

40Weak · 17% of overall
How it's scored
18.1/60Stars14 stars
8.3/25Forks11 forks
5/15Watchers9 watchers
Inputs used
forks11
stars14
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
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?

75Good · 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
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled6
top_contributor_share0.445
How it's scored
36.8/42Issue resolution88% of issues closed
20/30PR acceptance8/12 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/29 approved changesets -- score normalized to 0
Inputs used
merged_prs8
open_issues1
closed_issues7
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.875
closed_unmerged_prs4
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
16.1/25Owner reach175 followers of LINBIT
25/25Track record94 public repos, account ~12 yr old
Inputs used
followers175
owner_typeOrganization
is_verified
owner_loginLINBIT
public_repos94
account_age_days4,605
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 3 days ago
20/20Version history107 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/LINBIT/golinstor
ecosystemsgo
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicslinstor, golang
has_wikiyes
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?

39Weak · 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
0/2.5CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/29 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 4 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
7.5/7.5Vulnerabilities0 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): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
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.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/39 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes39,331
source_files_sampled39
oversized_source_files0

Key facts

14GitHub stars
6contributors
24commits, last 12 months
1days since last push
99releases
2bus factor
1open issues
Gopackage ecosystems

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

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 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 1/29 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
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
n/aPinned-Dependenciesno dependencies found
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 7
RegistryPackageVersion constraintManifest
Gogithub.com/BurntSushi/tomlv1.6.0go.mod
Gogithub.com/donovanhide/eventsourcev0.0.0-20210830082556-c59027999da0go.mod
Gogithub.com/google/go-querystringv1.2.0go.mod
Gogithub.com/sirupsen/logrusv1.9.4go.mod
Gogithub.com/stretchr/testifyv1.11.1go.mod
Gogolang.org/x/timev0.15.0go.mod
Gomoul.io/http2curl/v2v2.3.0go.mod
All dependencies 20

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

RegistryPackageVersionRelation
Gogithub.com/burntsushi/tomlv1.6.0direct
Gogithub.com/donovanhide/eventsourcev0.0.0-20210830082556-c59027999da0direct
Gogithub.com/google/go-querystringv1.2.0direct
Gogithub.com/sirupsen/logrusv1.9.4direct
Gogithub.com/stretchr/testifyv1.11.1direct
Gogolang.org/x/timev0.15.0direct
Gomoul.io/http2curl/v2v2.3.0direct
Gogithub.com/boumenot/gocover-coberturav1.5.0indirect
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/google/go-cmpv0.7.0indirect
Gogithub.com/jstemmer/go-junit-report/v2v2.1.0indirect
Gogithub.com/kr/prettyv0.3.1indirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogithub.com/rogpeppe/go-internalv1.14.1indirect
Gogolang.org/x/modv0.35.0indirect
Gogolang.org/x/syncv0.20.0indirect
Gogolang.org/x/sysv0.45.0indirect
Gogolang.org/x/toolsv0.44.0indirect
Gogopkg.in/check.v1v1.0.0-20201130134442-10cb98267c6cindirect
Gogopkg.in/yaml.v3v3.0.1indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo.