Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 23:33 UTC

leehainuo / coco

Coco is an elegant and beautiful OpenAPI UI library for Go

Go · Vue · TypeScriptMIT★ 122 stars⑂ 8 forkssince May 2026View on GitHub ↗
KindNetwork serviceLibraryWeb interfacehow this is determined

leehainuo/coco holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Vitality (68/100) and lowest on Security (14/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

LeehainuoPersonal account
11 followers21 public repossince Sep 2024

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 publish
Gogithub.com/leehainuo/cocov0.2.0-26 days ago

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recencylast push 6 days ago
2.1/36Commit cadence3/52 weeks with commits
7.6/18Commit volume6 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year6
human_commit_share
days_since_last_push6
active_weeks_last_year3

Release discipline

100Exceptional
How it's scored
27/27Ships releases2 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~0 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tagv0.2.0
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases0
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?

57Moderate · 17% of overall
How it's scored
33.8/60Stars122 stars
7/25Forks8 forks
4.7/15Watchers8 watchers
Inputs used
forks8
stars122
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance1/1 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
7.8/25Owner reach11 followers of leehainuo
13.4/25Track record21 public repos, account ~1 yr old
Inputs used
followers11
owner_typeUser
is_verified
owner_loginleehainuo
public_repos21
account_age_days663
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 6 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/leehainuo/coco
ecosystemsgo
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 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

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsapi-docs, api-documentation, go, golang, openapi, swagger, swagger-ui, tailwindcss, vue3
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

14Critical · 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 0/3 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
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
0/7.5Vulnerabilities28 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.4
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.

51Moderate · 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
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingfrontend/tsconfig.json
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, package-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsfrontend/tsconfig.json
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/86 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes14,403
source_files_sampled86
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)example/basic/cmd/embedded/openapi.json, example/basic/cmd/i18n/openapi.json, example/basic/cmd/local/openapi.json, example/framework/chi/swag/docs/swagger.json, example/framework/chi/swag/docs/swagger.yaml, example/framework/echo/swag/docs/swagger.json, example/framework/echo/swag/docs/swagger.yaml, example/framework/fiber/swag/docs/swagger.json, example/framework/fiber/swag/docs/swagger.yaml, example/framework/gin/swag/docs/swagger.json, example/framework/gin/swag/docs/swagger.yaml, example/framework/nethttp/swag/docs/swagger.json, example/framework/nethttp/swag/docs/swagger.yaml, internal/testdata/openapi.json
0/20MCP server
40/40Runnable examplesexample
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_filesexample/basic/cmd/embedded/openapi.json, example/basic/cmd/i18n/openapi.json, example/basic/cmd/local/openapi.json, example/framework/chi/swag/docs/swagger.json, example/framework/chi/swag/docs/swagger.yaml, example/framework/echo/swag/docs/swagger.json, example/framework/echo/swag/docs/swagger.yaml, example/framework/fiber/swag/docs/swagger.json, example/framework/fiber/swag/docs/swagger.yaml, example/framework/gin/swag/docs/swagger.json, example/framework/gin/swag/docs/swagger.yaml, example/framework/nethttp/swag/docs/swagger.json, example/framework/nethttp/swag/docs/swagger.yaml, internal/testdata/openapi.json
interfaces_expected_ofnetwork-service

Key facts

122GitHub stars
1contributors
6commits, last 12 months
6days since last push
2releases
1bus factor
0open issues
Go, npmpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 1.4 / 10
1.4aggregate

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-18 23:33 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 0/3 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
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
0Vulnerabilities28 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
Gogithub.com/danielgtaylor/huma/v2v2.38.0example/go.mod
Gogithub.com/gin-gonic/ginv1.12.0example/go.mod
Gogithub.com/go-chi/chi/v5v5.2.5example/go.mod
Gogithub.com/gofiber/fiber/v3v3.2.0example/go.mod
Gogithub.com/labstack/echo/v4v4.15.2example/go.mod
Gogithub.com/leehainuo/cocov0.0.0-00010101000000-000000000000example/go.mod
Gogithub.com/swaggo/swagv1.16.6example/go.mod
npmtailwind-merge^3.6.0frontend/package.json
npmtw-animate-css^1.4.0frontend/package.json
npmvue^3.4.0frontend/package.json
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.

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

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