Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 11:47 UTC

wxsms / uiv

Bootstrap 3 components implemented by Vue.js.

JavaScript · VueMIT★ 937 stars⑂ 182 forkssince Feb 2017View on GitHub ↗

wxsms/uiv holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on Security (54/100). It was last updated today. A single contributor accounts for most of its recent work.

87
overall / 100
Excellent

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.

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

Ownership

wxsmPersonal account
169 followers87 public repossince Nov 2013KingSoft Office

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
15.2/36Commit cadence — 22/52 weeks with commits
18/18Commit volume — 213 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_year213
human_commit_share0.14
days_since_last_push0
active_weeks_last_year22
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 40 days ago
12.6/27Release cadence — a release every ~185.9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv2.0.7
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases185.9

Community & Adoption

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

77Good · 17% of overall
How it's scored
48.2/60Stars — 937 stars
18.8/25Forks — 182 forks
8/15Watchers — 29 watchers
Inputs used
forks182
stars937
watchers29
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadgen.net, codecov.io, github.com
has_pull_request_templateyes
How it's scored
66/80Monthly downloads — 88,479 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesuiv
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads88,479
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?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.5/22.5Commit distribution — top contributor authored 80% of commits
13.5/13.5Contributor breadth — 47 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled47
top_contributor_share0.802
How it's scored
41.2/42Issue resolution — 98% of issues closed
27.9/30PR acceptance — 634/681 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs634
open_issues5
closed_issues254
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.981
closed_unmerged_prs47
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
16/25Owner reach — 169 followers of wxsms
25/25Track record — 87 public repos, account ~12 yr old
Inputs used
followers169
owner_typeUser
is_verified—
owner_loginwxsms
public_repos87
account_age_days4,718
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 40 days ago
20/20Version history — 128 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesuiv
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/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_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://wxsms.github.io/uiv/
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsvue, bootstrap, ui, vue3
has_wikino
homepagehttps://wxsms.github.io/uiv/
docs_sitehttps://wxsms.github.io/uiv/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
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 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 6 contributing companies or organizations
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
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Branch-Protection. 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.

70Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes2,990
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — docs/jsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 86 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
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsdocs/jsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.86
How it's scored
27/45Type-checkable code — JavaScript with type-check config (docs/jsconfig.json)
55/55Manageable file sizes — 0/84 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes41,016
source_files_sampled84
oversized_source_files0

Key facts

937GitHub stars
47contributors
213commits, last 12 months
0days since last push
100releases
1bus factor
5open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OSV advisory lookup failed: [Errno 101] Network is unreachable

More detail

Star and fork history 0 ★ / 182 ⇿
0Stars
182Forks
99Releases

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.

0408012016020018062017-032021-122026-08
Major 2Minor 30Patch 62

Each point covers 9 days.

OpenSSF Scorecard 5.4 / 10
5.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-10-19 11:46 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
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 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
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
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
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 15

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

RegistryPackageVersionRelation
npm@pnpm/exe.android-arm6412.10.1indirect
npm@pnpm/exe.android-x6412.10.1indirect
npm@pnpm/exe.darwin-arm6412.10.1indirect
npm@pnpm/exe.darwin-x6412.10.1indirect
npm@pnpm/exe.freebsd-x6412.10.1indirect
npm@pnpm/exe.linux-arm6412.10.1indirect
npm@pnpm/exe.linux-arm64-musl12.10.1indirect
npm@pnpm/exe.linux-ppc6412.10.1indirect
npm@pnpm/exe.linux-riscv6412.10.1indirect
npm@pnpm/exe.linux-s390x12.10.1indirect
npm@pnpm/exe.linux-x6412.10.1indirect
npm@pnpm/exe.linux-x64-musl12.10.1indirect
npm@pnpm/exe.win32-arm6412.10.1indirect
npm@pnpm/exe.win32-x6412.10.1indirect
npmpnpm12.10.1indirect
Dependency advisories not assessed

Advisory matching could not run for this report: OSV advisory lookup failed: [Errno 101] Network is unreachable

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.