Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 08:40 UTC

sutras / cosey

基于 Vue3 的后台管理框架

TypeScript · VueMIT★ 16 stars⑂ 2 forkssince May 2025View on GitHub ↗
KindLibraryWeb interfacehow this is determined

sutras/cosey holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Vitality (72/100) and lowest on Sustainability & Governance (36/100). It was last updated 55 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

sutrasPersonal account
14 followers40 public repossince Dec 2020

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
npm@cosey/mock0.1.6458286 days ago
npmcosey0.12.72,0482424 days agoadminbackstage-management-systemvue3vite
npm@cosey/icons0.2.0312106 days ago
npm@cosey/request-interceptor0.1.5486286 days ago

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
18/36Push recencylast push 55 days ago
20.1/36Commit cadence29/52 weeks with commits
18/18Commit volume195 commits in the last year
5/10OpenSSF Scorecard: Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year195
human_commit_share1
days_since_last_push55
active_weeks_last_year29
How it's scored
16.2/27Ships releases10 version tags (no GitHub releases)
36/36Release recencylatest release 55 days ago
27/27Release cadencea release every ~24.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count10
latest_release_tagv0.11.9
releases_from_tagsyes
days_since_latest_release55
mean_days_between_releases24.3
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?

39Weak · 17% of overall
How it's scored
19.1/60Stars16 stars
0/25Forks2 forks
0/15Watchers1 watchers
Inputs used
forks2
stars16
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/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_templateno
How it's scored
44.2/80Monthly downloads2,048 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagescosey
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,048
unverified_packages_excluded@cosey/mock, @cosey/icons, @cosey/request-interceptor
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?

36Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
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_prs0
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
8.5/25Owner reach14 followers of sutras
23/25Track record40 public repos, account ~5 yr old
Inputs used
followers14
owner_typeUser
is_verified
owner_loginsutras
public_repos40
account_age_days2,048
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable4 package(s) on npm
35/35Publish recencylatest publish 4 days ago
20/20Version history242 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@cosey/mock, cosey, @cosey/icons, @cosey/request-interceptor
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
0/24CI workflows
0/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_cino
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttp://docs.cosey.wzt.zone/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttp://docs.cosey.wzt.zone/
docs_sitehttp://docs.cosey.wzt.zone/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

46Weak · 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
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-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages100
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 2 resolved dependencies against OSV. 100 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history96 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.96
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format configeslint.config.mjs
11/11Static type checkingdocs/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsdocs/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/750 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes41,767
source_files_sampled750
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

16GitHub stars
1contributors
195commits, last 12 months
55days since last push
10releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • deps.dev does not index npm:cosey@0.12.7; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 16 ★ / 2 ⇿
16Stars
2Forks
6Releases

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.

048121616222025-052025-102026-03
Major 0Minor 1Patch 5
OpenSSF Scorecard 3.1 / 10
3.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-22 08:40 UTC

10Binary-Artifactsno binaries found in the repo
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
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
npm@casl/ability^6.7.3package.json
npm@casl/vue^2.2.2package.json
npm@cosey/mockworkspace:^package.json
npm@gunny/mock^1.2.0package.json
npm@iconify-json/carbon^1.2.8package.json
npm@tailwindcss/vite^4.0.9package.json
npmaxios^1.7.9package.json
npmcoseyworkspace:^package.json
npmdayjs^1.11.13package.json
npmelement-plus^2.11.4package.json
npmlodash-es^4.17.21package.json
npmvue^3.5.21package.json
npmvue-i18n^11.1.10package.json
npmvue-router^4.5.0package.json
npm@cosey/icons^0.1.8packages/cosey/package.json
All dependencies 102

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

RegistryPackageVersionRelation
npm@casl/ability^6.7.3direct
npm@casl/vue^2.2.2direct
npm@cosey/icons^0.1.8direct
npm@cosey/mock^0.1.6direct
npm@gunny/mock^1.2.0direct
npm@iconify-json/carbon^1.2.8direct
npm@tailwindcss/vite^4.0.9direct
npmaxios^1.7.9direct
npmdayjs^1.11.13direct
npmelement-plus^2.11.4direct
npmlodash-es^4.17.21direct
npmvue^3.5.21direct
npmvue-i18n^11.1.10direct
npmvue-router^4.5.0direct
npm@babel/core^7.27.1indirect
npm@commitlint/cli^19.6.0indirect
npm@commitlint/config-conventional^19.6.0indirect
npm@commitlint/prompt-cli^19.6.0indirect
npm@ctrl/tinycolor^4.1.0indirect
npm@element-plus/icons-vue^2.3.1indirect
npm@emotion/hash^0.9.2indirect
npm@emotion/unitless^0.10.0indirect
npm@eslint/compat^1.2.9indirect
npm@eslint/js^9.27.0indirect
npm@floating-ui/dom^1.6.13indirect
npm@gunny/persist^1.0.3indirect
npm@iconify/types^2.0.0indirect
npm@rollup/plugin-json^6.1.0indirect
npm@types/babel__core^7.20.5indirect
npm@types/conventional-changelog^6.0.0indirect
npm@types/crypto-js^4.2.2indirect
npm@types/fs-extra^11.0.4indirect
npm@types/gh-pages^6.1.0indirect
npm@types/identicon.js^2.3.5indirect
npm@types/inquirer^9.0.7indirect
npm@types/is-hotkey^0.1.10indirect
npm@types/lodash-es^4.17.12indirect
npm@types/markdown-it^14.1.2indirect
npm@types/markdown-it-container^2.0.10indirect
npm@types/nprogress^0.2.3indirect
npm@types/prismjs^1.26.5indirect
npm@types/semver^7.7.0indirect
npm@types/shelljs^0.8.17indirect
npm@types/stylis^4.2.7indirect
npm@vitejs/plugin-vue^5.2.1indirect
npm@vitejs/plugin-vue-jsx^4.1.1indirect
npm@vue/babel-plugin-jsx^1.4.0indirect
npm@vue/runtime-core^3.5.13indirect
npm@vue/shared^3.5.13indirect
npm@vueuse/core^13.2.0indirect
npmajv^8.17.1indirect
npmclassnames^2.5.1indirect
npmconsola^3.3.3indirect
npmconventional-changelog^7.1.1indirect
npmcross-env^7.0.3indirect
npmcrypto-js^4.2.0indirect
npmcsstype^3.1.3indirect
npmdexie^4.0.11indirect
npmecharts^5.6.0indirect
npmesbuild^0.25.4indirect
npmeslint^9.27.0indirect
npmeslint-plugin-vue^10.1.0indirect
npmfs-extra^11.2.0indirect
npmgh-pages^6.3.0indirect
npmglob^11.0.2indirect
npmglobals^16.1.0indirect
npmhusky^9.1.7indirect
npmidenticon.js^2.3.3indirect
npminquirer^12.3.0indirect
npmis-hotkey^0.2.0indirect
npmjszip^3.10.1indirect
npmkatex^0.16.22indirect
npmlint-staged^15.2.10indirect
npmmarkdown-it^14.1.0indirect
npmmarkdown-it-container^4.0.0indirect
npmmime^4.0.7indirect
npmnprogress^0.2.0indirect
npmora^8.2.0indirect
npmpinia^3.0.2indirect
npmprettier3.4.2indirect
npmprettier-plugin-tailwindcss^0.6.11indirect
npmprismjs^1.30.0indirect
npmrimraf^6.0.1indirect
npmrollup^4.40.2indirect
npmsass^1.82.0indirect
npmsass^1.89.0indirect
npmsemver^7.7.1indirect
npmshelljs^0.10.0indirect
npmslate-vue3^0.10.0indirect
npmstylis^4.3.6indirect
npmsvga^2.1.1indirect
npmtailwindcss^4.0.9indirect
npmtsx^4.19.2indirect
npmtypescript^5.7.2indirect
npmtypescript-eslint^8.32.1indirect
npmvite^7.1.7indirect
npmvite-plugin-svg-icons^2.0.1indirect
npmvite-plugin-vue-devtools^8.0.2indirect
npmvitepress2.0.0-alpha.12indirect
npmvitepress^1.6.3indirect
npmvitepress-plugin-group-icons^1.6.1indirect
npmvue-tsc^2.2.8indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 2 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 100 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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

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