Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 02:44 UTC

verisoft-ai / appium-wincore-driver

Appium driver for Windows desktop UI automation — supports UWP, WinForms, WPF, and Win32 apps via Windows UI Automation APIs.

TypeScript · C#Apache-2.0★ 3 stars⑂ 1 forksince Mar 2026forkView on GitHub ↗
KindLibraryDesktop applicationhow this is determined

verisoft-ai/appium-wincore-driver holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (93/100) and lowest on Community & Adoption (20/100). It was last updated 1 day ago. A single contributor accounts 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

VeriSoftOrganization
2 followers12 public repossince Jun 2023

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmappium-wincore-driver2.8.316041 day agoappiumwincoredesktopuiautomationautomated-testingwindowsverisoftdesktop-automation

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
23.5/36Commit cadence — 34/52 weeks with commits
18/18Commit volume — 486 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year486
human_commit_share1
days_since_last_push1
active_weeks_last_year34

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 48 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~2.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count48
latest_release_tagv2.8.3
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases2.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?

20At Risk · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars3
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
29.4/80Monthly downloads — 160 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesappium-wincore-driver
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads160
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.3/22.5Commit distribution — top contributor authored 72% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.722
How it's scored
34.6/42Issue resolution — 82% of issues closed
25.1/30PR acceptance — 51/61 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs51
open_issues3
closed_issues14
prs_merged_7d2
prs_decided_7d2
prs_merged_30d17
prs_decided_30d19
issue_closed_ratio0.824
closed_unmerged_prs10
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
30/30Ownership backing — organization-owned
0/20Verified domain
3.4/25Owner reach — 2 followers of verisoft-ai
14.5/25Track record — 12 public repos, account ~3 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_loginverisoft-ai
public_repos12
account_age_days1,167
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 1 days ago
12/20Version history — 4 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesappium-wincore-driver
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 5 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 — 3 out of 3 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

50Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://verisoft-ai.github.io/appium-wincore-driver/
0/10Repository description
10/10Topics — 12 topics
0/10Wiki
Inputs used
topicsappium, appium-driver, desktop-automation, mcp, powershell, typescript, ui-automation, uwp, win32, windows, winforms, wpf
has_wikino
homepagehttps://verisoft-ai.github.io/appium-wincore-driver/
docs_sitehttps://verisoft-ai.github.io/appium-wincore-driver/
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

61Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 3 out of 3 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/11 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 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 5 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 — no data
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): Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
14.4/25Indirect dependencies free of known advisories — 1 affected: morgan 1.11.0 (moderate 5.3)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages246
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages0
Matched the npm:appium-wincore-driver@2.8.3 runtime dependency closure — what installing the published package pulls in — 246 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.99
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,883
How it's scored
12.6/18One-command bootstrap — csharp/BridgeInjectorX86Stub/BridgeInjectorX86Stub.csproj, csharp/DesktopDriverServer.Tests/DesktopDriverServer.Tests.csproj, csharp/DesktopDriverServer/DesktopDriverServer.csproj (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice — 54 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
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_configyes
typecheck_configstsconfig.json
agent_commit_share0.54
toolchain_manifestscsharp/BridgeInjectorX86Stub/BridgeInjectorX86Stub.csproj, csharp/DesktopDriverServer.Tests/DesktopDriverServer.Tests.csproj, csharp/DesktopDriverServer/DesktopDriverServer.csproj, csharp/IEBridge/IEBridge.csproj, dotnet-bridge-agent-core/BridgeAgentCore.csproj, examples/C#/CalculatorTest/CalculatorTest/CalculatorTest.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.7/55Manageable file sizes — 1/188 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes91,482
source_files_sampled188
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

3GitHub stars
7contributors
486commits, last 12 months
1days since last push
48releases
1bus factor
3open issues
npm, NuGetpackage ecosystems

Data collection warnings

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

More detail

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-09-10 02:44 UTC

9Binary-Artifactsbinaries present in source code
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests3 out of 3 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/11 approved changesets -- score normalized to 0
10Contributorsproject has 4 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 5 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@appium/css-locator-to-native^1.0.6package.json
npm@appium/support^7.2.6package.json
npmappium-chromedriver^8.3.1package.json
npmasyncbox^6.3.5package.json
npmbezier-easing^2.1.0package.json
npmkoffi^2.14.1package.json
All dependencies 28

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

RegistryPackageVersionRelation
npm@appium/css-locator-to-native^1.0.6direct
npm@appium/support^7.2.6direct
npmappium-chromedriver^8.3.1direct
npmasyncbox^6.3.5direct
npmbezier-easing^2.1.0direct
npmkoffi^2.14.1direct
npm@appium/eslint-config-appium-ts^2.0.3indirect
npm@appium/tsconfig^1.1.0indirect
npm@appium/types^1.1.0indirect
npm@semantic-release/changelog^6.0.3indirect
npm@semantic-release/git^10.0.1indirect
npm@types/node^24.8.1indirect
npmconventional-changelog-conventionalcommits^9.1.0indirect
npmeslint^9.38.0indirect
npmglobals^15.15.0indirect
npmsemantic-release^25.0.1indirect
npmtypescript^5.9.3indirect
npmtypescript-eslint^8.46.1indirect
npmvitest^2.1.0indirect
npmwebdriverio^9.30.1indirect
NuGetAppium.WebDriver7.2.0indirect
NuGetMicrosoft.NET.Test.Sdk17.11.1indirect
NuGetMicrosoft.NET.Test.Sdk17.8.0indirect
NuGetNUnit3.14.0indirect
NuGetNUnit.Analyzers3.9.0indirect
NuGetNUnit3TestAdapter4.5.0indirect
NuGetxunit2.9.2indirect
NuGetxunit.runner.visualstudio2.8.2indirect
Dependency advisories 1

Installing npm:appium-wincore-driver@2.8.3 pulls in 246 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
morgan1.11.0indirectmoderate11.12.0

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.