Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 09:13 UTC

overwolf / ow-electron-packages-types

Types repository for all ow-electron packages

JavaScriptMIT★ 3 stars⑂ 6 forkssince Jul 2023View on GitHub ↗

overwolf/ow-electron-packages-types holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (77/100) and lowest on AI Readiness (13/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

Overwolf Ltd.Organization
229 followers46 public repossince Jun 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@overwolf/ow-electron-packages-types1.1.5-26,488766 days agotypesnpmpackageoverwolfow-electronoverlaygame-list

Metrics by category

Vitality

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

49Weak · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
17.3/36Commit cadence25/52 weeks with commits
18/18Commit volume149 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year149
human_commit_share
days_since_last_push3
active_weeks_last_year25
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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
4.9/60Stars3 stars
5.8/25Forks6 forks
2.7/15Watchers4 watchers
Inputs used
forks6
stars3
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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
50.8/80Monthly downloads6,488 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@overwolf/ow-electron-packages-types
dependents
ecosystemsnpm
total_downloads
monthly_downloads6,488
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?

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.7/22.5Commit distributiontop contributor authored 30% of commits
10.8/13.5Contributor breadth8 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor2
contributors_sampled8
top_contributor_share0.3
How it's scored
42/42Issue resolution100% of issues closed
22.5/30PR acceptance9/12 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs9
open_issues0
closed_issues1
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs3
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
17/25Owner reach229 followers of overwolf
24.2/25Track record46 public repos, account ~12 yr old
Inputs used
followers229
owner_typeOrganization
is_verified
owner_loginoverwolf
public_repos46
account_age_days4,410
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 6 days ago
20/20Version history76 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@overwolf/ow-electron-packages-types
ecosystemsnpm
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
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?

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

13Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilesyarn.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
38.5/55Manageable file sizes3/10 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes171,863
source_files_sampled10
oversized_source_files3

Key facts

3GitHub stars
8contributors
149commits, last 12 months
3days since last push
0releases
2bus factor
0open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-20 09:12 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
0SASTSAST tool is not run on all commits -- score normalized to 0
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 1
RegistryPackageVersion constraintManifest
npmglob^13.0.0package.json
All dependencies 94

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

RegistryPackageVersionRelation
npm@electron/get1.14.1indirect
npm@overwolf/ow-electron28.3.2indirect
npm@sindresorhus/is0.14.0indirect
npm@szmarczak/http-timer1.1.2indirect
npm@types/node16.18.104indirect
npmboolean3.2.0indirect
npmbuffer-crc320.2.13indirect
npmbuffer-from1.1.2indirect
npmcacheable-request6.1.0indirect
npmclone-response1.0.3indirect
npmconcat-stream1.6.2indirect
npmconfig-chain1.1.13indirect
npmcore-util-is1.0.3indirect
npmdebug2.6.9indirect
npmdebug4.3.5indirect
npmdecompress-response3.3.0indirect
npmdefer-to-connect1.1.3indirect
npmdefine-data-property1.1.4indirect
npmdefine-properties1.2.1indirect
npmdetect-node2.1.0indirect
npmduplexer30.1.5indirect
npmencodeurl1.0.2indirect
npmend-of-stream1.4.4indirect
npmenv-paths2.2.1indirect
npmes-define-property1.0.0indirect
npmes-errors1.3.0indirect
npmes6-error4.1.1indirect
npmescape-string-regexp4.0.0indirect
npmextract-zip1.7.0indirect
npmfd-slicer1.1.0indirect
npmfs-extra8.1.0indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.2.4indirect
npmget-stream4.1.0indirect
npmget-stream5.2.0indirect
npmglobal-agent3.0.0indirect
npmglobal-tunnel-ng2.7.1indirect
npmglobalthis1.0.4indirect
npmgopd1.0.1indirect
npmgot9.6.0indirect
npmgraceful-fs4.2.11indirect
npmhas-property-descriptors1.0.2indirect
npmhas-proto1.0.3indirect
npmhas-symbols1.0.3indirect
npmhasown2.0.2indirect
npmhttp-cache-semantics4.1.1indirect
npminherits2.0.4indirect
npmini1.3.8indirect
npmisarray1.0.0indirect
npmjson-buffer3.0.0indirect
npmjson-stringify-safe5.0.1indirect
npmjsonfile4.0.0indirect
npmkeyv3.1.0indirect
npmlodash4.17.21indirect
npmlowercase-keys1.0.1indirect
npmlowercase-keys2.0.0indirect
npmmatcher3.0.0indirect
npmmimic-response1.0.1indirect
npmminimist1.2.8indirect
npmmkdirp0.5.6indirect
npmms2.0.0indirect
npmms2.1.2indirect
npmnormalize-url4.5.1indirect
npmnpm-conf1.1.3indirect
npmobject-keys1.1.1indirect
npmonce1.4.0indirect
npmp-cancelable1.1.0indirect
npmpend1.2.0indirect
npmpify3.0.0indirect
npmprepend-http2.0.0indirect
npmprocess-nextick-args2.0.1indirect
npmprogress2.0.3indirect
npmproto-list1.2.4indirect
npmpump3.0.0indirect
npmreadable-stream2.3.8indirect
npmresponselike1.0.2indirect
npmroarr2.15.4indirect
npmsafe-buffer5.1.2indirect
npmsemver6.3.1indirect
npmsemver7.6.3indirect
npmsemver-compare1.0.0indirect
npmserialize-error7.0.1indirect
npmsprintf-js1.1.3indirect
npmstring_decoder1.1.1indirect
npmsumchecker3.0.1indirect
npmto-readable-stream1.0.0indirect
npmtunnel0.0.6indirect
npmtype-fest0.13.1indirect
npmtypedarray0.0.6indirect
npmuniversalify0.1.2indirect
npmurl-parse-lax3.0.0indirect
npmutil-deprecate1.0.2indirect
npmwrappy1.0.2indirect
npmyauzl2.10.0indirect
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.15.0 — full methodology · metrics wiki.

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