Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 15:13 UTC

electron / windows-sign

Codesign Electron apps for Windows

TypeScriptBSD-2-Clause★ 66 stars⑂ 20 forkssince May 2023View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

electron/windows-sign holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (80/100) and lowest on Engineering Quality (57/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ElectronOrganization · verified domain
4,091 followers114 public repossince Jul 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@electron/windows-sign2.1.019,383,7881740 days ago

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
28.8/36Push recency — last push 9 days ago
17.1/36Commit cadence — 26/52 weeks with commits, discounted for automation: 38 of the last 100 commits human-authored, spanning 171 days
14.5/18Commit volume — 49 commits in the last year, discounted for automation: 38 of the last 100 commits human-authored, spanning 171 days
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year49
human_commit_share0.38
days_since_last_push9
active_weeks_last_year26
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 40 days ago
19.8/27Release cadence — a release every ~63.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagv2.1.0
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases63.6
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?

65Good · 17% of overall
How it's scored
29.4/60Stars — 66 stars
10.7/25Forks — 20 forks
4.3/15Watchers — 7 watchers
Inputs used
forks20
stars66
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-2-Clause)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 19,383,788 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@electron/windows-sign
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads19,383,788
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?

80Excellent · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11/22.5Commit distribution — top contributor authored 51% of commits
12.2/13.5Contributor breadth — 9 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.512
How it's scored
33.6/42Issue resolution — 80% of issues closed
28.9/30PR acceptance — 104/108 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs104
open_issues3
closed_issues12
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.8
closed_unmerged_prs4
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
20/20Verified domain
25/25Owner reach — 4,091 followers of electron
25/25Track record — 114 public repos, account ~11 yr old
Inputs used
followers4,091
owner_typeOrganization
is_verifiedyes
owner_loginelectron
public_repos114
account_age_days4,109

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 — 17 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@electron/windows-sign
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
0/16Linter config
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_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
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?

74Good · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
3/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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 16 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
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
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
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 10 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.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@electron/windows-sign@2.1.0 runtime dependency closure — what installing the published package pulls in — 5 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.

70Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.digicert.com/llms.txt)
40/40Legible commit history — 38 of 38 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.digicert.com/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 10 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 46 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesyarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.1
toolchain_manifests—
dependency_bot_commit_share0.46
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
52.2/55Manageable file sizes — 1/20 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,990,158
source_files_sampled20
oversized_source_files1

Key facts

66GitHub stars
9contributors
49commits, last 12 months
9days since last push
16releases
1bus factor
3open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 20 ⇿
0Stars
20Forks
11Releases

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.

0481216202012024-032025-062026-08
Major 1Minor 1Patch 9

Each point covers 3 days.

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-10-19 15:13 UTC

9Binary-Artifactsbinaries present in source code
4Branch-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
10Code-Reviewall changesets reviewed
10Contributorsproject has 16 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmdebug^4.3.4package.json
npmgraceful-fs^4.2.11package.json
npmpostject^1.0.0-alpha.6package.json
All dependencies 119

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

RegistryPackageVersionRelation
npmdebug4.3.4direct
npmgraceful-fs4.2.11direct
npmpostject1.0.0-alpha.6direct
npm@electron/fsevents2.3.3-forkindirect
npm@esbuild/android-arm0.18.20indirect
npm@esbuild/android-arm640.18.20indirect
npm@esbuild/android-x640.18.20indirect
npm@esbuild/darwin-arm640.18.20indirect
npm@esbuild/darwin-x640.18.20indirect
npm@esbuild/freebsd-arm640.18.20indirect
npm@esbuild/freebsd-x640.18.20indirect
npm@esbuild/linux-arm0.18.20indirect
npm@esbuild/linux-arm640.18.20indirect
npm@esbuild/linux-ia320.18.20indirect
npm@esbuild/linux-loong640.18.20indirect
npm@esbuild/linux-mips64el0.18.20indirect
npm@esbuild/linux-ppc640.18.20indirect
npm@esbuild/linux-riscv640.18.20indirect
npm@esbuild/linux-s390x0.18.20indirect
npm@esbuild/linux-x640.18.20indirect
npm@esbuild/netbsd-x640.18.20indirect
npm@esbuild/openbsd-x640.18.20indirect
npm@esbuild/sunos-x640.18.20indirect
npm@esbuild/win32-arm640.18.20indirect
npm@esbuild/win32-ia320.18.20indirect
npm@esbuild/win32-x640.18.20indirect
npm@gerrit0/mini-shiki3.23.0indirect
npm@oxfmt/binding-android-arm-eabi0.71.0indirect
npm@oxfmt/binding-android-arm640.71.0indirect
npm@oxfmt/binding-darwin-arm640.71.0indirect
npm@oxfmt/binding-darwin-x640.71.0indirect
npm@oxfmt/binding-freebsd-x640.71.0indirect
npm@oxfmt/binding-linux-arm-gnueabihf0.71.0indirect
npm@oxfmt/binding-linux-arm-musleabihf0.71.0indirect
npm@oxfmt/binding-linux-arm64-gnu0.71.0indirect
npm@oxfmt/binding-linux-arm64-musl0.71.0indirect
npm@oxfmt/binding-linux-ppc64-gnu0.71.0indirect
npm@oxfmt/binding-linux-riscv64-gnu0.71.0indirect
npm@oxfmt/binding-linux-riscv64-musl0.71.0indirect
npm@oxfmt/binding-linux-s390x-gnu0.71.0indirect
npm@oxfmt/binding-linux-x64-gnu0.71.0indirect
npm@oxfmt/binding-linux-x64-musl0.71.0indirect
npm@oxfmt/binding-openharmony-arm640.71.0indirect
npm@oxfmt/binding-win32-arm64-msvc0.71.0indirect
npm@oxfmt/binding-win32-ia32-msvc0.71.0indirect
npm@oxfmt/binding-win32-x64-msvc0.71.0indirect
npm@oxlint-tsgolint/darwin-arm640.20.0indirect
npm@oxlint-tsgolint/darwin-x640.20.0indirect
npm@oxlint-tsgolint/linux-arm640.20.0indirect
npm@oxlint-tsgolint/linux-x640.20.0indirect
npm@oxlint-tsgolint/win32-arm640.20.0indirect
npm@oxlint-tsgolint/win32-x640.20.0indirect
npm@oxlint/binding-android-arm-eabi1.59.0indirect
npm@oxlint/binding-android-arm641.59.0indirect
npm@oxlint/binding-darwin-arm641.59.0indirect
npm@oxlint/binding-darwin-x641.59.0indirect
npm@oxlint/binding-freebsd-x641.59.0indirect
npm@oxlint/binding-linux-arm-gnueabihf1.59.0indirect
npm@oxlint/binding-linux-arm-musleabihf1.59.0indirect
npm@oxlint/binding-linux-arm64-gnu1.59.0indirect
npm@oxlint/binding-linux-arm64-musl1.59.0indirect
npm@oxlint/binding-linux-ppc64-gnu1.59.0indirect
npm@oxlint/binding-linux-riscv64-gnu1.59.0indirect
npm@oxlint/binding-linux-riscv64-musl1.59.0indirect
npm@oxlint/binding-linux-s390x-gnu1.59.0indirect
npm@oxlint/binding-linux-x64-gnu1.59.0indirect
npm@oxlint/binding-linux-x64-musl1.59.0indirect
npm@oxlint/binding-openharmony-arm641.59.0indirect
npm@oxlint/binding-win32-arm64-msvc1.59.0indirect
npm@oxlint/binding-win32-ia32-msvc1.59.0indirect
npm@oxlint/binding-win32-x64-msvc1.59.0indirect
npm@shikijs/engine-oniguruma3.23.0indirect
npm@shikijs/langs3.23.0indirect
npm@shikijs/themes3.23.0indirect
npm@shikijs/types3.23.0indirect
npm@shikijs/vscode-textmate10.0.2indirect
npm@tsconfig/node2222.0.1indirect
npm@types/debug4.1.10indirect
npm@types/graceful-fs4.1.9indirect
npm@types/hast3.0.4indirect
npm@types/ms0.7.31indirect
npm@types/node16.11.6indirect
npm@types/node22.10.10indirect
npm@types/unist3.0.3indirect
npmargparse2.0.1indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.5indirect
npmbuffer-from1.1.2indirect
npmcommander9.5.0indirect
npmentities4.5.0indirect
npmesbuild0.18.20indirect
npmfsevents2.3.3-forkindirect
npmget-tsconfig4.7.2indirect
npmhusky9.1.7indirect
npmlinkify-it5.0.1indirect
npmlint-staged17.4.1indirect
npmlunr2.3.9indirect
npmmarkdown-it14.2.0indirect
npmmdurl2.0.0indirect
npmminimatch10.2.5indirect
npmms2.1.2indirect
npmoxfmt0.71.0indirect
npmoxlint1.59.0indirect
npmoxlint-tsgolint0.20.0indirect
npmpicomatch4.0.7indirect
npmpunycode.js2.3.1indirect
npmresolve-pkg-maps1.0.0indirect
npmsource-map0.6.1indirect
npmsource-map-support0.5.21indirect
npmstring-argv0.3.2indirect
npmtinyexec1.3.0indirect
npmtinypool2.2.0indirect
npmtsx3.14.0indirect
npmtypedoc0.28.18indirect
npmtypescript6.0.2indirect
npmuc.micro2.1.0indirect
npmundici-types6.20.0indirect
npmyaml2.8.3indirect
npmyaml2.9.0indirect
Dependency advisories 0

Installing npm:@electron/windows-sign@2.1.0 pulls in 5 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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

How one result sits in the wider record: aggregate statistics — npm.