Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 09:14 UTC

lovasoa / highs-js

Javascript linear programming library

Linear Programming · JavaScript · TypeScriptMIT★ 86 stars⑂ 24 forkssince Mar 2021View on GitHub ↗

lovasoa/highs-js holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (77/100) and lowest on AI Readiness (53/100). It was last updated 31 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Ophir LOJKINEPersonal account
648 followers363 public repossince Jan 2011@datadog

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
npmhighs1.15.284,4143536 days agolinear-programminglpmilpsolvermathsoroptimization

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
18/36Push recencylast push 31 days ago
2.8/36Commit cadence4/52 weeks with commits
17.8/18Commit volume95 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year95
human_commit_share1
days_since_last_push31
active_weeks_last_year4
How it's scored
27/27Ships releases35 releases published
36/36Release recencylatest release 31 days ago
27/27Release cadencea release every ~6.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count35
latest_release_tagv1.15.3-pre.4
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases6.7

Community & Adoption

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

56Moderate · 17% of overall
How it's scored
31.3/60Stars86 stars
11.3/25Forks24 forks
1.7/15Watchers3 watchers
Inputs used
forks24
stars86
watchers3
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, badgen.net, github.com
has_pull_request_templateno
How it's scored
65.7/80Monthly downloads84,414 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageshighs
dependents
ecosystemsnpm
total_downloads
monthly_downloads84,414
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 factor1 contributor(s) cover half of all commits
3.2/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth11 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.856
How it's scored
40.7/42Issue resolution97% of issues closed
24.8/30PR acceptance19/23 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs19
open_issues1
closed_issues32
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.97
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20.2/25Owner reach648 followers of lovasoa
25/25Track record363 public repos, account ~15 yr old
Inputs used
followers648
owner_typeUser
is_verified
owner_loginlovasoa
public_repos363
account_age_days5,711
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 36 days ago
20/20Version history35 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageshighs
ecosystemsnpm
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://lovasoa.github.io/highs-js/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://lovasoa.github.io/highs-js/
docs_sitehttps://lovasoa.github.io/highs-js/
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-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 contributing companies or organizations
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 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.3

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages48
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 48 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

53Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
5.3/40Legible commit history10 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes12,461
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingdocs-tooling/tsconfig.json, test-dts/tsconfig.json, tsconfig.json
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontaineryes
has_linter_configno
typecheck_configsdocs-tooling/tsconfig.json, test-dts/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeLinear Programming with type-check config (docs-tooling/tsconfig.json, test-dts/tsconfig.json, tsconfig.json)
52.9/55Manageable file sizes3/78 source files over 60KB
Inputs used
primary_languageLinear Programming
largest_source_bytes130,398
source_files_sampled78
oversized_source_files3

Key facts

86GitHub stars
11contributors
95commits, last 12 months
31days since last push
35releases
1bus factor
1open 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 ★ / 24 ⇿
0Stars
24Forks
19Releases

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.

048121620242422021-052023-122026-07
Major 1Minor 5Patch 13

Each point covers 5 days.

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-08-28 09:14 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 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 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 48

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

RegistryPackageVersionRelation
npm@gerrit0/mini-shiki3.23.0indirect
npm@playwright/test1.61.1indirect
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/recommended1.0.13indirect
npm@types/hast3.0.5indirect
npm@types/unist3.0.3indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npmargparse2.0.1indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.8indirect
npmentities4.5.0indirect
npmfsevents2.3.2indirect
npmlinkify-it5.0.2indirect
npmlunr2.3.9indirect
npmmarkdown-it14.3.0indirect
npmmdurl2.1.0indirect
npmminimatch10.2.5indirect
npmplaywright1.61.1indirect
npmplaywright-core1.61.1indirect
npmpunycode.js2.3.1indirect
npmtypedoc0.28.20indirect
npmtypescript6.0.3indirect
npmtypescript7.0.2indirect
npmuc.micro2.1.0indirect
npmyaml2.9.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 48 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion5.0.8indirecthigh15.0.9

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