Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 16:55 UTC

fy0 / CodeKanban

Manage all your terminals and ai coding agents from one unified page.

Go · Vue · TypeScriptApache-2.0★ 224 stars⑂ 26 forkssince Nov 2025View on GitHub ↗
KindNetwork serviceCommand-line toolWeb interfaceLibraryhow this is determined

fy0/CodeKanban holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (82/100) and lowest on Security (47/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

fyPersonal account
291 followers120 public repossince Mar 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
npmuipoints to another repo — not scored0.2.433,48475483 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
28.8/36Push recencylast push 9 days ago
18.7/36Commit cadence27/52 weeks with commits
18/18Commit volume491 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year491
human_commit_share1
days_since_last_push9
active_weeks_last_year27
How it's scored
27/27Ships releases46 releases published
36/36Release recencylatest release 9 days ago
27/27Release cadencea release every ~10.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count46
latest_release_tagv0.45.0
releases_from_tagsno
days_since_latest_release9
mean_days_between_releases10.1

Community & Adoption

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

50Moderate · 17% of overall
How it's scored
38.1/60Stars224 stars
11.7/25Forks26 forks
0/15Watchers0 watchers
Inputs used
forks26
stars224
watchers0
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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
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.3/22.5Commit distributiontop contributor authored 99% of commits
6.8/13.5Contributor breadth5 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.988
How it's scored
33.6/42Issue resolution80% of issues closed
30/30PR acceptance6/6 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/30 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues3
closed_issues12
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.8
closed_unmerged_prs0
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.7/25Owner reach291 followers of fy0
25/25Track record120 public repos, account ~14 yr old
Inputs used
followers291
owner_typeUser
is_verified
owner_loginfy0
public_repos120
account_age_days5,261
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicsaiprogramming, claude-code, codex, coding-agents, kanban, vibe-coding, vibecoding, terminal
has_wikino
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?

47Weak · 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
2.5/2.5CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/30 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous 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.5Maintained30 commit(s) and 0 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/5SASTSAST tool is not run on all commits -- score normalized to 0
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.5Vulnerabilities59 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.4

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:ui@0.2.4 runtime dependency closure — what installing the published package pulls in — 1 packages. Reachability is not analyzed.

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.

69Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,196
How it's scored
12.6/18One-command bootstrapgo.mod, tools/filetime/go.mod, tools/proctime/go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingui/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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
lockfilesgo.sum, pnpm-lock.yaml
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsui/tsconfig.json
agent_commit_share0
toolchain_manifestsgo.mod, tools/filetime/go.mod, tools/proctime/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
53.7/55Manageable file sizes14/598 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes339,870
source_files_sampled598
oversized_source_files14
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)openapi.json
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filesopenapi.json
interfaces_expected_ofnetwork-service

Key facts

224GitHub stars
5contributors
491commits, last 12 months
9days since last push
46releases
1bus factor
3open issues
Go, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'ui' points at a different repository (https://github.com/marcuswestin/ui.js); excluded from ecosystem scoring
  • Could not fetch npm package '@codekanban/sdk' from its registry
  • Could not fetch npm package '@codekanban/cli' 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 ★ / 26 ⇿
0Stars
26Forks
44Releases

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.

0510152025302622025-112026-032026-08
Major 0Minor 42Patch 2
OpenSSF Scorecard 3.4 / 10
3.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-08-22 16:55 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 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
0SASTSAST tool is not run on all commits -- score normalized to 0
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
0Vulnerabilities59 existing vulnerabilities detected
Direct dependencies 66
RegistryPackageVersion constraintManifest
Gogithub.com/DATA-DOG/go-sqlmockv1.5.2go.mod
Gogithub.com/Masterminds/semver/v3v3.4.0go.mod
Gogithub.com/charmbracelet/x/xptyv0.1.3go.mod
Gogithub.com/danielgtaylor/huma/v2v2.34.1go.mod
Gogithub.com/glebarez/sqlitev1.11.0go.mod
Gogithub.com/go-git/go-billy/v6v6.0.0-alpha.2go.mod
Gogithub.com/go-git/go-git/v6v6.0.0-alpha.5go.mod
Gogithub.com/gofiber/fiber/v2v2.52.9go.mod
Gogithub.com/google/shlexv0.0.0-20191202100458-e7afc7fbc510go.mod
Gogithub.com/gorilla/websocketv1.5.3go.mod
Gogithub.com/jessevdk/go-flagsv1.6.1go.mod
Gogithub.com/kardianos/servicev1.2.4go.mod
Gogithub.com/knadh/koanf/parsers/yamlv1.1.0go.mod
Gogithub.com/knadh/koanf/providers/filev1.2.0go.mod
Gogithub.com/knadh/koanf/providers/structsv1.0.0go.mod
Gogithub.com/knadh/koanf/v2v2.3.0go.mod
Gogithub.com/matoous/go-nanoid/v2v2.1.0go.mod
Gogithub.com/mattn/go-sqlite3v1.14.22go.mod
Gogithub.com/patrickmn/go-cachev2.1.0+incompatiblego.mod
Gogithub.com/samber/lov1.51.0go.mod
Gogithub.com/sergi/go-diffv1.4.0go.mod
Gogithub.com/shirou/gopsutil/v4v4.25.10go.mod
Gogithub.com/tuzig/vt10xv0.0.0-20251129150011-c2f2317a3188go.mod
Gogithub.com/valyala/fasthttpv1.62.0go.mod
Gogo.uber.org/zapv1.27.0go.mod
Gogolang.org/x/cryptov0.54.0go.mod
Gogolang.org/x/netv0.57.0go.mod
Gogolang.org/x/sysv0.47.0go.mod
Gogolang.org/x/textv0.40.0go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
Gogorm.io/driver/sqlitev1.6.0go.mod
Gogorm.io/gormv1.30.0go.mod
npm@noble/hashes^2.0.1ui/package.json
npm@tiptap/core3.29.2ui/package.json
npm@tiptap/extension-document3.29.2ui/package.json
npm@tiptap/extension-hard-break3.29.2ui/package.json
npm@tiptap/extension-paragraph3.29.2ui/package.json
npm@tiptap/extension-text3.29.2ui/package.json
npm@tiptap/extensions3.29.2ui/package.json
npm@tiptap/pm3.29.2ui/package.json
npm@tiptap/vue-33.29.2ui/package.json
npm@vicons/ionicons5^0.12.0ui/package.json
npm@vueuse/core^14.0.0ui/package.json
npm@xterm/addon-fit^0.10.0ui/package.json
npm@xterm/addon-search^0.15.0ui/package.json
npm@xterm/addon-serialize^0.13.0ui/package.json
npm@xterm/addon-web-links^0.11.0ui/package.json
npm@xterm/addon-webgl^0.18.0ui/package.json
npm@xterm/xterm^5.3.0ui/package.json
npmalova^3.3.4ui/package.json
npmdayjs^1.11.18ui/package.json
npmes-toolkit^1.39.10ui/package.json
npmeventemitter3^5.0.1ui/package.json
npmfilesize^11.0.13ui/package.json
npmhighlight.js^11.11.1ui/package.json
npmmarked^17.0.0ui/package.json
npmnaive-ui^2.43.1ui/package.json
npmpinia^3.0.3ui/package.json
npmsortablejs^1.14.0ui/package.json
npmvue^3.5.18ui/package.json
npmvue-i18n^11.1.12ui/package.json
npmvue-router^4.5.1ui/package.json
npmvuedraggable^4.1.0ui/package.json
npm@codekanban/sdk0.1.0packages/codekanban-cli/package.json
Gogithub.com/djherbis/timesv1.6.0tools/filetime/go.mod
Gogithub.com/shirou/gopsutil/v3v3.24.5tools/proctime/go.mod
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

Dependency advisories 0

Installing npm:ui@0.2.4 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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

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