Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 21:56 UTC

petabite / golinks

golinks for your personal setup

Rust · GoGPL-3.0★ 2 stars⑂ 0 forkssince Apr 2023View on GitHub ↗
#gin#golang#golinks#gorm#rust#webassembly#yew

petabite/golinks holds a health index of 18 out of 100, placing it in the Critical band. It scores highest on AI Readiness (43/100) and lowest on Vitality (18/100). It was last updated 1180 days ago. A single contributor accounts for most of its recent work.

18
overall / 100
Critical

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.

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

Ownership

Philip ZhangPersonal account
30 followers34 public repossince Dec 2016

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioclientpoints to another repo — not scored0.1.1-beta1521901 days agochatlightweb3blockchainclient
Gogithub.com/petabite/golinksv0.1.0-11180 days ago—

Metrics by category

Vitality

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

18Critical · 21% of overall

Development activity

1Critical
How it's scored
0/36Push recency — last push 1,180 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share—
days_since_last_push1,180
active_weeks_last_year0

Release discipline

44Weak
How it's scored
27/27Ships releases — 1 releases published
0/36Release recency — latest release 1,180 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv0.1.0
releases_from_tagsno
days_since_latest_release1,180
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?

24At Risk · 17% of overall

Popularity & adoption

1Critical
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

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.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?

31At Risk · 23% of overall

Maintainer resilience (bus factor)

20At Risk
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
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1

Issue & PR responsiveness

1Critical
How it's scored
0/42Issue resolution — 0% of issues closed
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues1
closed_issues0
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0
closed_unmerged_prs0
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

55Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.7/25Owner reach — 30 followers of petabite
23.2/25Track record — 34 public repos, account ~9 yr old
Inputs used
followers30
owner_typeUser
is_verified—
owner_loginpetabite
public_repos34
account_age_days3,508
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

53Moderate
How it's scored
25/25Published & resolvable — 1 package(s) on go
4/35Publish recency — latest publish 1,180 days ago
4/20Version history — 1 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/petabite/golinks
ecosystemsgo
any_deprecatedno
min_days_since_publish1,180

Engineering Quality

Are baseline engineering and documentation practices in place?

25At Risk · 19% of overall

Engineering practices

1Critical
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 — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsgin, golang, golinks, gorm, rust, webassembly, yew
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?

19Critical · 16% of overall

Security posture

19Critical
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/22 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 8 contributing companies or organizations
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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 44 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate1.9
Excluded from scoring (no data or not applicable): CI-Tests, 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.

43Weak · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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.

Verify loop (build / test / typecheck)

54Moderate
How it's scored
18/18One-command bootstrap — Makefile, client/Makefile, server/Makefile
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilesCargo.lock, go.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, client/Makefile, server/Makefile
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.

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/14 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes4,618
source_files_sampled14
oversized_source_files0

Key facts

2GitHub stars
1contributors
0commits, last 12 months
1,180days since last push
1releases
1bus factor
1open issues
crates.io, Gopackage ecosystems

Data collection warnings

  • crates package 'client' points at a different repository (https://github.com/dravenk/client/); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 1.9 / 10
1.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 21:56 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/22 approved changesets -- score normalized to 0
10Contributorsproject has 8 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities44 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
crates.ioyew0.20.0client/Cargo.toml
crates.ioyew-router0.17client/Cargo.toml
crates.iogloo-net0.2client/Cargo.toml
crates.iogloo-console0.2.3client/Cargo.toml
crates.ioserde1.0client/Cargo.toml
crates.ioserde_json1.0.96client/Cargo.toml
crates.iowasm-bindgen-futures0.4client/Cargo.toml
crates.ioweb-sys0.3.61client/Cargo.toml
crates.iowasm-bindgen0.2.84client/Cargo.toml
crates.iostylist0.12.0client/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with petabite/golinks. Read them side by side →

98valkey-io/valkey-glideAn open source Valkey client library that supports Valkey, and Redis open source 6.2, 7.0 and 7.2. Valkey GLIDE is designed for reliability, optimized performance, and high-availability, for Valkey and Redis OSS based applications. GLIDE is a multi language client library, written in Rust with programming language bindings, such as Java and PythonExceptional96wormhole-foundation/wormholeA reference implementation for the Wormhole blockchain interoperability protocol.Exceptional98boa-dev/boaBoa is an embeddable Javascript engine written in Rust.Exceptional98apache/foryA blazingly fast multi-language serialization framework for idiomatic domain objects, schema IDL, and cross-language data exchange.Exceptional97wasmerio/wasmer🚀 Fast, secure, lightweight containers based on WebAssemblyExceptional96bytecodealliance/wasmtimeA lightweight WebAssembly runtime that is fast, secure, and standards-compliantExceptional

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.12.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io, Go.