Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-29 01:05 UTC

foru17 / neko-master

A modern and elegant dashboard for network traffic visualization and analysis.

TypeScriptMIT★ 3,046 stars⑂ 201 forkssince Feb 2026View on GitHub ↗
KindWeb interfaceNetwork servicehow this is determined

foru17/neko-master holds a health index of 71 out of 100, placing it in the Good band. It scores highest on AI Readiness (84/100) and lowest on Security (21/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Luo LeiPersonal account
1,802 followers37 public repossince Jul 2012

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/foru17/neko-masterv1.4.0-79 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
28.8/36Push recencylast push 9 days ago
9/36Commit cadence13/52 weeks with commits
18/18Commit volume175 commits in the last year
10/10OpenSSF Scorecard: Maintained27 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year175
human_commit_share1
days_since_last_push9
active_weeks_last_year13
How it's scored
27/27Ships releases18 releases published
36/36Release recencylatest release 9 days ago
27/27Release cadencea release every ~16 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count18
latest_release_tagagent-v1.4.5
releases_from_tagsno
days_since_latest_release9
mean_days_between_releases16

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

75Good · 17% of overall
How it's scored
56.5/60Stars3,046 stars
19.2/25Forks201 forks
4.7/15Watchers8 watchers
Inputs used
forks201
stars3,046
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?

52Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.2/22.5Commit distributiontop contributor authored 99% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.989
How it's scored
29.3/42Issue resolution70% of issues closed
6/30PR acceptance2/10 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues20
closed_issues46
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.697
closed_unmerged_prs8
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
23.4/25Owner reach1,802 followers of foru17
23.5/25Track record37 public repos, account ~14 yr old
Inputs used
followers1,802
owner_typeUser
is_verified
owner_loginforu17
public_repos37
account_age_days5,137
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 9 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/foru17/neko-master
ecosystemsgo
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsclash, openclash, traffic-monitor, dashboard, visualization, surge
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?

21At Risk · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowdangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained27 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities28 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate2.1
Excluded from scoring (no data or not applicable): CI-Tests. 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history98 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.98
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes12,446
How it's scored
12.6/18One-command bootstrapapps/agent/go.mod (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingapps/collector/tsconfig.json, apps/web/tsconfig.json, packages/shared/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice40 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsapps/collector/tsconfig.json, apps/web/tsconfig.json, packages/shared/tsconfig.json
agent_commit_share0.4
toolchain_manifestsapps/agent/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.8/55Manageable file sizes1/225 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes133,769
source_files_sampled225
oversized_source_files1

Key facts

3,046GitHub stars
3contributors
175commits, last 12 months
9days since last push
18releases
1bus factor
20open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@neko-master/collector' from its registry
  • Could not fetch npm package '@neko-master/shared' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 201 ⇿
0Stars
201Forks
18Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

04080120160200200232026-022026-052026-07
Major 0Minor 1Patch 2
OpenSSF Scorecard 2.1 / 10
2.1aggregate

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-29 01:05 UTC

9Binary-Artifactsbinaries present in source code
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/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained27 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities28 existing vulnerabilities detected
Direct dependencies 42
RegistryPackageVersion constraintManifest
npm@fastify/cookie^11.0.2apps/collector/package.json
npm@fastify/cors^11.2.0apps/collector/package.json
npm@neko-master/sharedworkspace:*apps/collector/package.json
npmbetter-sqlite3^12.10.0apps/collector/package.json
npmdotenv^17.4.2apps/collector/package.json
npmfastify^5.8.5apps/collector/package.json
npmmaxmind^5.0.6apps/collector/package.json
npmws^8.21.0apps/collector/package.json
npm@ducanh2912/next-pwa^10.2.9apps/web/package.json
npm@neko-master/sharedworkspace:*apps/web/package.json
npm@radix-ui/react-alert-dialog^1.1.16apps/web/package.json
npm@radix-ui/react-dropdown-menu^2.1.17apps/web/package.json
npm@radix-ui/react-popover^1.1.16apps/web/package.json
npm@radix-ui/react-radio-group^1.4.0apps/web/package.json
npm@radix-ui/react-scroll-area^1.2.11apps/web/package.json
npm@radix-ui/react-select^2.3.0apps/web/package.json
npm@radix-ui/react-separator^1.1.9apps/web/package.json
npm@radix-ui/react-slot^1.2.5apps/web/package.json
npm@radix-ui/react-switch^1.3.0apps/web/package.json
npm@radix-ui/react-tabs^1.1.14apps/web/package.json
npm@tanstack/react-query^5.101.0apps/web/package.json
npm@xyflow/react^12.11.0apps/web/package.json
npmclass-variance-authority^0.7.1apps/web/package.json
npmclsx^2.1.1apps/web/package.json
npmcountry-flag-icons^1.6.17apps/web/package.json
npmd3-scale^4.0.2apps/web/package.json
npmdate-fns^4.4.0apps/web/package.json
npmframer-motion^12.40.0apps/web/package.json
npmlucide-react^1.17.0apps/web/package.json
npmnext^16.2.7apps/web/package.json
npmnext-intl^4.13.0apps/web/package.json
npmnext-themes^0.4.6apps/web/package.json
npmradix-ui^1.5.0apps/web/package.json
npmreact^19.2.7apps/web/package.json
npmreact-copy-to-clipboard^5.1.1apps/web/package.json
npmreact-day-picker^10.0.1apps/web/package.json
npmreact-dom^19.2.7apps/web/package.json
npmreact-simple-maps^3.0.0apps/web/package.json
npmrecharts^3.8.1apps/web/package.json
npmsonner^2.0.7apps/web/package.json
npmtailwind-merge^3.6.0apps/web/package.json
npmvaul^1.1.2apps/web/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.27.0 — full methodology · metrics wiki.

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