Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 18:23 UTC

CloudeaSoft / koishi-plugin-warframe

A koishi tool plugin for warframers.

TypeScriptGPL-3.0★ 2 stars⑂ 0 forkssince Dec 2025View on GitHub ↗
KindLibraryPluginhow this is determined

CloudeaSoft/koishi-plugin-warframe holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (88/100) and lowest on Community & Adoption (45/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

CloudeaPersonal account
4 followers19 public repossince Mar 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 publishTags
npmkoishi-plugin-warframe1.19.133,731948 days agochatbotkoishiplugin

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
15.9/36Commit cadence — 23/52 weeks with commits
18/18Commit volume — 246 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year246
human_commit_share0.82
days_since_last_push1
active_weeks_last_year23

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 89 releases published
36/36Release recency — latest release 8 days ago
27/27Release cadence — a release every ~1.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count89
latest_release_tagv1.19.13
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases1.9
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?

45Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
47.6/80Monthly downloads — 3,731 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageskoishi-plugin-warframe
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,731
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.4/22.5Commit distribution — top contributor authored 76% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.759
How it's scored
28/42Issue resolution — 67% of issues closed
26.3/30PR acceptance — 134/153 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/24 approved changesets -- score normalized to 0
Inputs used
merged_prs134
open_issues1
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d22
prs_decided_30d23
issue_closed_ratio0.667
closed_unmerged_prs19
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
5/25Owner reach — 4 followers of CloudeaSoft
16.8/25Track record — 19 public repos, account ~3 yr old
Inputs used
followers4
owner_typeUser
is_verified—
owner_loginCloudeaSoft
public_repos19
account_age_days1,330
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 npm
35/35Publish recency — latest publish 8 days ago
20/20Version history — 94 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageskoishi-plugin-warframe
ecosystemsnpm
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.npmjs.com/package/koishi-plugin-warframe
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://www.npmjs.com/package/koishi-plugin-warframe
docs_sitehttps://www.npmjs.com/package/koishi-plugin-warframe
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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
0/7.5Code-Review — Found 1/24 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 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
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
10/25Indirect dependencies free of known advisories — 1 affected: uuid 9.0.1 (high 7.5)
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 208 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages60
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:koishi-plugin-warframe@1.19.13 runtime dependency closure — what installing the published package pulls in — 60 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.

77Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://code.visualstudio.com/llms.txt)
40/40Legible commit history — 82 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://code.visualstudio.com/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes10,285
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tests/tsconfig.json, tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice — 39 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstests/tsconfig.json, tsconfig.json
agent_commit_share0.39
toolchain_manifests—
dependency_bot_commit_share0.05
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.5/55Manageable file sizes — 2/205 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes145,064
source_files_sampled205
oversized_source_files2

Key facts

2GitHub stars
2contributors
246commits, last 12 months
1days since last push
89releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 6.6 / 10
6.6aggregate

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-11-17 18:23 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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 1/24 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
npmasync-cache-dedupe^3.4.0package.json
npmofetch^1.5.1package.json
npmpinyin-pro^3.29.5package.json
npmtencentcloud-sdk-nodejs-ocr^4.1.267package.json
npmwarframe-public-export-plus^0.6.12package.json
npmwarframe-weekly-rivens^0.0.3package.json
npmwarframe-worldstate-data^3.19.0package.json
npmwarframe-worldstate-parser^5.5.11package.json
npmwfm-api-client^0.0.4package.json
All dependencies 44

Full resolved dependency set from the GitHub dependency graph: 9 direct and 35 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmasync-cache-dedupe^3.4.0direct
npmofetch^1.5.1direct
npmpinyin-pro^3.29.5direct
npmtencentcloud-sdk-nodejs-ocr^4.1.267direct
npmwarframe-public-export-plus^0.6.12direct
npmwarframe-weekly-rivens^0.0.3direct
npmwarframe-worldstate-data^3.19.0direct
npmwarframe-worldstate-parser^5.5.11direct
npmwfm-api-client^0.0.4direct
npm@antfu/eslint-config9.1.0indirect
npm@eslint/markdown^8.0.2indirect
npm@koishijs/client^5.30.11indirect
npm@koishijs/plugin-database-memory^3.7.0indirect
npm@koishijs/plugin-help^2.4.6indirect
npm@koishijs/plugin-mock^2.6.6indirect
npm@satorijs/element^3.2.0indirect
npm@semantic-release/commit-analyzer^13.0.1indirect
npm@semantic-release/github^12.0.9indirect
npm@semantic-release/npm^13.1.5indirect
npm@semantic-release/release-notes-generator^14.1.1indirect
npm@types/chai^5.2.3indirect
npm@types/node^25.9.5indirect
npm@typescript-eslint/eslint-plugin^8.62.0indirect
npm@typescript-eslint/parser^8.62.0indirect
npm@vitest/coverage-v84.1.10indirect
npmchai^6.2.2indirect
npmconventional-changelog-conventionalcommits^9.3.1indirect
npmesbuild^0.28.1indirect
npmeslint^10.7.0indirect
npmglobals^17.7.0indirect
npmhusky^9.1.7indirect
npmjiti^2.7.0indirect
npmkoishi^4.18.11indirect
npmkoishi-plugin-cron^3.1.0indirect
npmkoishi-plugin-puppeteer^3.9.0indirect
npmlzma^2.3.2indirect
npmreflect-metadata^0.2.2indirect
npmsemantic-release^25.0.9indirect
npmtypescript^5.9.3indirect
npmtypescript-eslint^8.62.0indirect
npmvitest4.1.10indirect
npmyakumo^1.0.0indirect
npmyakumo-esbuild^1.0.0indirect
npmyakumo-tsc^1.0.0indirect
Dependency advisories 1

Installing npm:koishi-plugin-warframe@1.19.13 pulls in 60 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
uuid9.0.1indirecthigh113.0.1

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