Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 16:53 UTC

kanvekin / Kernixcord

The other cutest Discord client mod Kernixcord

TypeScriptGPL-3.0★ 13 stars⑂ 1 forksince Oct 2025View on GitHub ↗

kanvekin/Kernixcord holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (96/100) and lowest on Security (39/100). It was last updated 3 days ago. 2 contributors account 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

kaanseasPersonal account
5 followers12 public repossince Feb 2023

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
npm@equicord/discord-typespoints to another repo — not scored1.0.531677 days ago
npm@equicord/types1.14.151,0731177 days ago

Metrics by category

Vitality

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

96Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 3 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume2,916 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_year2,916
human_commit_share1
days_since_last_push3
active_weeks_last_year52
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 64 days ago
27/27Release cadencea release every ~1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag2026-07-16
releases_from_tagsno
days_since_latest_release64
mean_days_between_releases1

Community & Adoption

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

53Moderate · 17% of overall
How it's scored
17.5/60Stars13 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars13
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

63Moderate · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.8/22.5Commit distributiontop contributor authored 47% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 50 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.474
How it's scored
0/42Issue resolutionno issues or no data
27.5/30PR acceptance11/12 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_prs11
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
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
5.6/25Owner reach5 followers of kanvekin
15.2/25Track record12 public repos, account ~3 yr old
Inputs used
followers5
owner_typeUser
is_verified
owner_loginkanvekin
public_repos12
account_age_days1,299
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 npm
35/35Publish recencylatest publish 77 days ago
20/20Version history11 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@equicord/types
ecosystemsnpm
any_deprecatedno
min_days_since_publish77

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
0/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configyes
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/10Topics8 topics
10/10Wiki
Inputs used
topicsdiscord, equicord, equicord-plugins, equicord-userplugins, plugin, vencord, vencord-plugins, kernixcord
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?

39Weak · 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
2.5/2.5Contributorsproject has 50 contributing companies or organizations
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
0/5Packagingno data
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.5Vulnerabilities48 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3
Excluded from scoring (no data or not applicable): CI-Tests, Packaging. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: moment 2.22.2 (high 7.5)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
33.7/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,627 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages3
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:@equicord/discord-types@1.0.5 runtime dependency closure — what installing the published package pulls in — 3 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.

47Weak · 4% of overall
How it's scored
18/45Agent instructionsAGENTS.md, CLAUDE.md, GEMINI.md (stub)
0/15Machine-readable docs (llms.txt)
19.2/40Legible commit history36 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.36
agent_instruction_filesAGENTS.md, CLAUDE.md, GEMINI.md
agent_instruction_max_bytes6
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
2/10Demonstrated agent practice1 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_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.7/55Manageable file sizes9/1,506 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes175,731
source_files_sampled1,506
oversized_source_files9

Key facts

13GitHub stars
100contributors
2,916commits, last 12 months
3days since last push
100releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'Kernixcord' from its registry
  • npm package '@equicord/discord-types' points at a different repository (https://github.com/Equicord/Equicord); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.0 / 10
3.0aggregate

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-09-18 16:53 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
10Contributorsproject has 50 contributing companies or organizations
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
n/aPackagingpackaging workflow not 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
0Vulnerabilities48 existing vulnerabilities detected
Direct dependencies 26
RegistryPackageVersion constraintManifest
npm@ffmpeg/ffmpeg^0.12.10package.json
npm@ffmpeg/util^0.12.1package.json
npm@intrnl/xxhash64^0.1.2package.json
npm@song-spotlight/api^2.2.0package.json
npm@streamparser/json^0.0.22package.json
npm@vap/core0.0.12package.json
npm@vap/shiki0.10.5package.json
npmfflate^0.8.3package.json
npmgifencgithub:mattdesl/gifenc#64842fca317b112a8590f8fef2bf3825da8f6fe3package.json
npmgifuct-js^2.1.2package.json
npmidb8.0.3package.json
npmjsqr1.4.0package.json
npmmonaco-editor^0.55.1package.json
npmnanoid^5.1.16package.json
npmnative-file-system-adapter^3.0.1package.json
npmvirtual-merge^1.0.1package.json
npmyaml-js^0.3.1package.json
npmmoment2.22.2packages/discord-types/package.json
npmtype-fest^5.7.0packages/discord-types/package.json
npm@types/lodash4.17.19packages/vencord-types/package.json
npm@types/node^26.0.1packages/vencord-types/package.json
npm@vencord/discord-types^1.0.2packages/vencord-types/package.json
npmhighlight.js11.11.1packages/vencord-types/package.json
npmmoment^2.22.2packages/vencord-types/package.json
npmts-pattern^5.6.0packages/vencord-types/package.json
npmtype-fest^5.7.0packages/vencord-types/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

Dependency advisories 1

Installing npm:@equicord/discord-types@1.0.5 pulls in 3 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
moment2.22.2directhigh22.29.4

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.