Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 01:30 UTC

yeying-community / router

A unified AI gateway and operations platform for multi-provider model routing, channel management, billing, subscriptions, cost analytics, and monitoring.

Go · JavaScriptMIT★ 0 stars⑂ 6 forkssince Nov 2025View on GitHub ↗
KindNetwork serviceWeb interfacehow this is determined

yeying-community/router holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (87/100) and lowest on Community & Adoption (30/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

yeying-communityOrganization
9 followers33 public repossince Sep 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/yeying-community/routerv0.0.103-1032 days ago

Metrics by category

Vitality

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

87Excellent · 21% of overall

Development activity

86Excellent
How it's scored
36/36Push recency — last push 2 days ago
22.2/36Commit cadence — 32/52 weeks with commits
18/18Commit volume — 1,105 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,105
human_commit_share—
days_since_last_push2
active_weeks_last_year32

Release discipline

88Excellent
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~0.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.0.103
releases_from_tagsyes
days_since_latest_release2
mean_days_between_releases0.4
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?

30At Risk · 17% of overall

Popularity & adoption

6Critical
How it's scored
0/60Stars — 0 stars
5.8/25Forks — 6 forks
0/15Watchers — 1 watchers
Inputs used
forks6
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

57Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/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_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

68Good · 23% of overall

Maintainer resilience (bus factor)

25At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.6/22.5Commit distribution — top contributor authored 57% of commits
6.8/13.5Contributor breadth — 5 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.573

Issue & PR responsiveness

90Excellent
How it's scored
37.3/42Issue resolution — 89% of issues closed
28.6/30PR acceptance — 178/187 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 6/7 approved changesets -- score normalized to 8
Inputs used
merged_prs178
open_issues5
closed_issues40
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.889
closed_unmerged_prs9
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.

Ownership & stewardship

70Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
7.2/25Owner reach — 9 followers of yeying-community
18.9/25Track record — 33 public repos, account ~3 yr old
Inputs used
followers9
owner_typeOrganization
is_verified—
owner_loginyeying-community
public_repos33
account_age_days1,410
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 2 days ago
20/20Version history — 103 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/yeying-community/router
ecosystemsgo
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall

Engineering practices

68Good
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

75Good
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
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?

42Weak · 16% of overall

Security posture

42Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 6/7 approved changesets -- score normalized to 8
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 — 30 commit(s) and 2 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 — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 52 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

42Weak · 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)

52Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_files—
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. Remaining weights renormalized.

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — Go (statically typed)
54/55Manageable file sizes — 12/693 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes203,402
source_files_sampled693
oversized_source_files12

Machine-readable interfaces

40Weak
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

0GitHub stars
5contributors
1,105commits, last 12 months
2days since last push
100releases
1bus factor
5open 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 4.2 / 10
4.2aggregate

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-16 01:30 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 6/7 approved changesets -- score normalized to 8
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities52 existing vulnerabilities detected
Direct dependencies 47
RegistryPackageVersion constraintManifest
Gocloud.google.com/go/iamv1.1.10go.mod
Gogithub.com/aws/aws-sdk-go-v2v1.27.0go.mod
Gogithub.com/aws/aws-sdk-go-v2/credentialsv1.17.15go.mod
Gogithub.com/aws/aws-sdk-go-v2/service/bedrockruntimev1.8.3go.mod
Gogithub.com/ethereum/go-ethereumv1.14.12go.mod
Gogithub.com/gin-contrib/corsv1.7.2go.mod
Gogithub.com/gin-contrib/gzipv1.0.1go.mod
Gogithub.com/gin-contrib/sessionsv1.0.1go.mod
Gogithub.com/gin-contrib/staticv1.1.2go.mod
Gogithub.com/gin-gonic/ginv1.10.0go.mod
Gogithub.com/go-playground/validator/v10v10.20.0go.mod
Gogithub.com/go-redis/redis/v8v8.11.5go.mod
Gogithub.com/golang-jwt/jwtv3.2.2+incompatiblego.mod
Gogithub.com/google/uuidv1.6.0go.mod
Gogithub.com/gorilla/websocketv1.5.1go.mod
Gogithub.com/jinzhu/copierv0.4.0go.mod
Gogithub.com/patrickmn/go-cachev2.1.0+incompatiblego.mod
Gogithub.com/pkg/errorsv0.9.1go.mod
Gogithub.com/pkoukk/tiktoken-gov0.1.8go.mod
Gogithub.com/smartystreets/goconveyv1.8.1go.mod
Gogithub.com/stretchr/testifyv1.9.0go.mod
Gogolang.org/x/cryptov0.32.0go.mod
Gogolang.org/x/imagev0.18.0go.mod
Gogolang.org/x/syncv0.10.0go.mod
Gogoogle.golang.org/apiv0.187.0go.mod
Gogorm.io/driver/postgresv1.5.7go.mod
Gogorm.io/gormv1.25.10go.mod
Gogithub.com/golang-jwt/jwt/v5v5.2.1go.mod
Gogopkg.in/natefinch/lumberjack.v2v2.2.1go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
npm@ant-design/icons^6.2.2web/package.json
npm@yeying-community/web3-bs1.0.16web/package.json
npmantd^6.3.7web/package.json
npmaxios^0.27.2web/package.json
npmhistory^5.3.0web/package.json
npmi18next23.16.8web/package.json
npmi18next-browser-languagedetector^8.0.2web/package.json
npmmarked^4.1.1web/package.json
npmmoment^2.30.1web/package.json
npmreact^18.2.0web/package.json
npmreact-dom^18.2.0web/package.json
npmreact-dropzone^14.2.3web/package.json
npmreact-i18next15.5.0web/package.json
npmreact-router-dom^7.0.0web/package.json
npmreact-toastify^9.0.8web/package.json
npmreact-turnstile^1.0.5web/package.json
npmrecharts^2.15.1web/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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with yeying-community/router. Read them side by side →

100coder/coderSecure environments for developers and their agentsExceptional100apache/airflowApache Airflow - A platform to programmatically author, schedule, and monitor workflowsExceptional100mattermost/mattermostMattermost is an open source platform for secure collaboration across the entire software development lifecycle..Exceptional100hashicorp/consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.Exceptional99kubernetes-sigs/kueueKubernetes-native Job QueueingExceptional99lima-vm/limaLinux virtual machines, with a focus on running containersExceptional

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