Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-03 08:02 UTC

agracio / electron-edge-js

Run .NET code in Electron on Windows, MacOS, and Linux

C++MIT★ 391 stars⑂ 87 forkssince Sep 2017View on GitHub ↗

agracio/electron-edge-js holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (75/100) and lowest on Security (46/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

agracioPersonal account
42 followers34 public repossince Aug 2015

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
npmelectron-edge-js44.0.09,1798135 days agoowinedgenetdotnetclrcoreclrc#monomanagededge-jselectron

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
15.9/36Commit cadence — 23/52 weeks with commits
16.7/18Commit volume — 72 commits in the last year
10/10OpenSSF Scorecard: Maintained — 22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year72
human_commit_share0.89
days_since_last_push1
active_weeks_last_year23
How it's scored
16.2/27Ships releases — 28 version tags (no GitHub releases)
27/36Release recency — latest release 91 days ago
19.8/27Release cadence — a release every ~48.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count28
latest_release_tagv43.0.0
releases_from_tagsyes
days_since_latest_release91
mean_days_between_releases48.2
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?

60Moderate · 17% of overall
How it's scored
42/60Stars — 391 stars
16.1/25Forks — 87 forks
6.5/15Watchers — 16 watchers
Inputs used
forks87
stars391
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
52.8/80Monthly downloads — 9,179 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageselectron-edge-js
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads9,179
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.2/22.5Commit distribution — top contributor authored 95% of commits
13.5/13.5Contributor breadth — 15 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.946
How it's scored
41.5/42Issue resolution — 99% of issues closed
24.4/30PR acceptance — 48/59 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/20 approved changesets -- score normalized to 0
Inputs used
merged_prs48
open_issues2
closed_issues147
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.987
closed_unmerged_prs11
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
11.7/25Owner reach — 42 followers of agracio
23.2/25Track record — 34 public repos, account ~11 yr old
Inputs used
followers42
owner_typeUser
is_verified—
owner_loginagracio
public_repos34
account_age_days4,074
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 35 days ago
20/20Version history — 81 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageselectron-edge-js
ecosystemsnpm
any_deprecatedno
min_days_since_publish35

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 5 out of 5 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 9 topics
0/10Wiki
Inputs used
topicscoreclr, csharp, dotnet, dotnet-core, dotnet-framework, dotnetcore, dotnetframework, electron, nodejs
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?

46Weak · 16% of overall
How it's scored
0/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 5 out of 5 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/20 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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 — 22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
0/7.5Vulnerabilities — 14 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.2
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_packages2
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-edge-js@44.0.0 runtime dependency closure — what installing the published package pulls in — 2 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
7.8/40Legible commit history — 13 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.146
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — lib/bootstrap/bootstrap.csproj, src/double/Edge.js/Edge.js.csproj, test/test.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C++ (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 11 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
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestslib/bootstrap/bootstrap.csproj, src/double/Edge.js/Edge.js.csproj, test/test.csproj
dependency_bot_commit_share0.11
How it's scored
45/45Type-checkable code — C++ (statically typed)
52.1/55Manageable file sizes — 6/114 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes384,408
source_files_sampled114
oversized_source_files6

Key facts

391GitHub stars
15contributors
72commits, last 12 months
1days since last push
28releases
1bus factor
2open issues
npm, NuGetpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 87 ⇿
0Stars
87Forks
15Releases

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.

0204060807932017-102021-072025-04
Major 4Minor 3Patch 8

Each point covers 7 days.

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-03 08:02 UTC

0Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests5 out of 5 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/20 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained22 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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities14 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmedge-csnpm:@agracio/edge-cs@^1.3.7package.json
npmnan^2.28.0package.json
All dependencies 140

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

RegistryPackageVersionRelation
npmnan2.28.0direct
npm@agracio/edge-cs1.3.7indirect
npm@electron-internal/extract-zip1.0.5indirect
npm@electron/get5.0.0indirect
npm@isaacs/cliui8.0.2indirect
npm@pkgjs/parseargs0.11.0indirect
npm@types/node24.13.3indirect
npmansi-regex5.0.1indirect
npmansi-regex6.1.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.1indirect
npmargparse2.0.1indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.9indirect
npmbrowser-stdout1.3.1indirect
npmcamelcase6.3.0indirect
npmchalk4.1.2indirect
npmchokidar4.0.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcolors1.4.0indirect
npmcross-spawn7.0.6indirect
npmdateformat4.6.3indirect
npmdebug4.3.5indirect
npmdecamelize4.0.0indirect
npmdiff5.2.2indirect
npmdiff7.0.0indirect
npmeastasianwidth0.2.0indirect
npmelectron44.0.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmenv-paths3.0.0indirect
npmescalade3.1.2indirect
npmescape-html1.0.3indirect
npmescape-string-regexp4.0.0indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfollow-redirects1.16.0indirect
npmforeground-child3.3.1indirect
npmfs-extra10.1.0indirect
npmfs-extra11.3.0indirect
npmfsu1.1.1indirect
npmget-caller-file2.0.5indirect
npmglob10.5.0indirect
npmglob13.0.6indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmjs-tokens4.0.0indirect
npmjs-yaml4.3.2indirect
npmjson-stringify-safe5.0.1indirect
npmjsonfile6.1.0indirect
npmjsonfile6.2.0indirect
npmlocate-path6.0.0indirect
npmlodash.isfunction3.0.9indirect
npmlog-symbols4.1.0indirect
npmloose-envify1.4.0indirect
npmlru-cache10.4.3indirect
npmlru-cache11.2.7indirect
npmminimatch10.2.4indirect
npmminimatch9.0.9indirect
npmminipass7.1.3indirect
npmmocha11.8.0indirect
npmmochawesome8.0.1indirect
npmmochawesome-merge5.1.1indirect
npmmochawesome-report-generator6.3.2indirect
npmms2.1.2indirect
npmms2.1.3indirect
npmobject-assign4.1.1indirect
npmopener1.5.2indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpath-scurry2.0.2indirect
npmpicocolors1.1.1indirect
npmprogress2.0.3indirect
npmprop-types15.8.1indirect
npmreact-is16.13.1indirect
npmreaddirp4.1.2indirect
npmrequire-directory2.1.1indirect
npmsemver7.8.0indirect
npmserialize-javascript7.0.7indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.0indirect
npmstrip-json-comments3.1.1indirect
npmsumchecker3.0.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtcomb3.2.29indirect
npmtcomb-validation3.4.1indirect
npmundici7.29.0indirect
npmundici-types7.18.2indirect
npmuniversalify2.0.1indirect
npmwhich2.0.2indirect
npmworkerpool9.3.2indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
NuGetMicrosoft.CodeAnalysis4.9.2indirect
NuGetMicrosoft.CSharp4.7.0indirect
NuGetMicrosoft.DotNet.InternalAbstractions1.0.0indirect
NuGetMicrosoft.Extensions.DependencyModel8.0.2indirect
NuGetNewtonsoft.Json13.0.3indirect
NuGetSystem.AppContext4.3.0indirect
NuGetSystem.Collections.Specialized4.3.0indirect
NuGetSystem.Console4.3.1indirect
NuGetSystem.Data.Common4.3.0indirect
NuGetSystem.Dynamic.Runtime4.3.0indirect
NuGetSystem.IO.FileSystem4.3.0indirect
NuGetSystem.Linq4.3.0indirect
NuGetSystem.Linq.Expressions4.3.0indirect
NuGetSystem.Private.Uri4.3.2indirect
NuGetSystem.Reflection4.3.0indirect
NuGetSystem.Reflection.TypeExtensions4.5.1indirect
NuGetSystem.Runtime4.3.1indirect
NuGetSystem.Runtime.InteropServices4.3.0indirect
NuGetSystem.Runtime.Loader4.3.0indirect
NuGetSystem.Text.RegularExpressions4.3.1indirect
NuGetSystem.Xml.ReaderWriter4.3.1indirect
NuGetSystem.Xml.XmlSerializer4.3.0indirect
NuGetSystem.Xml.XPath.XmlDocument4.3.0indirect
Dependency advisories 0

Installing npm:electron-edge-js@44.0.0 pulls in 2 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.