Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 01:02 UTC

jaystack / odata-v4-sql

OData V4 SQL

JavaScript · TypeScriptNo license detected★ 22 stars⑂ 19 forkssince Nov 2016View on GitHub ↗

jaystack/odata-v4-sql holds a health index of 23 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (48/100) and lowest on Vitality (1/100). It was last updated 1187 days ago. A single contributor accounts for most of its recent work.

23
overall / 100
At Risk

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.

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

Ownership

11 followers106 public repossince Sep 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmodata-v4-sql0.1.223,06742914 days agoodatav4sql

Metrics by category

Vitality

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

1Critical · 21% of overall
How it's scored
0/36Push recencylast push 1,187 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share
days_since_last_push1,187
active_weeks_last_year0
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?

42Weak · 17% of overall
How it's scored
21.4/60Stars22 stars
10.5/25Forks19 forks
5.3/15Watchers10 watchers
Inputs used
forks19
stars22
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
58.2/80Monthly downloads23,067 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesodata-v4-sql
dependents
ecosystemsnpm
total_downloads
monthly_downloads23,067
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.7/22.5Commit distributiontop contributor authored 62% of commits
5.4/13.5Contributor breadth4 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.615
How it's scored
0/42Issue resolution0% of issues closed
30/30PR acceptance2/2 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/12 approved changesets -- score normalized to 1
Inputs used
merged_prs2
open_issues6
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0
closed_unmerged_prs0
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
7.8/25Owner reach11 followers of jaystack
25/25Track record106 public repos, account ~13 yr old
Inputs used
followers11
owner_typeOrganization
is_verified
owner_loginjaystack
public_repos106
account_age_days5,055
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 2,914 days ago
12/20Version history4 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesodata-v4-sql
ecosystemsnpm
any_deprecatedno
min_days_since_publish2,914

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
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
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
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?

13Critical · 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
0/2.5CI-Tests0 out of 2 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.8/7.5Code-ReviewFound 2/12 approved changesets -- score normalized to 1
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
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
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities33 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

43Weak · 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
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesyarn.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
27/45Type-checkable codeJavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes0/7 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes12,398
source_files_sampled7
oversized_source_files0

Key facts

22GitHub stars
4contributors
0commits, last 12 months
1,187days since last push
0releases
1bus factor
6open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 1.3 / 10
1.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-07-18 01:02 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/12 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities33 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmodata-v4-literal^0.1.0package.json
npmodata-v4-parser0.1.13package.json
All dependencies 126

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

RegistryPackageVersionRelation
npmodata-v4-literal0.1.0direct
npmodata-v4-parser0.1.13direct
npm@types/body-parser0.0.33indirect
npm@types/config0.0.30indirect
npm@types/cors0.0.33indirect
npm@types/express4.0.33indirect
npm@types/express-serve-static-core4.0.39indirect
npm@types/extend2.0.30indirect
npm@types/mime0.0.29indirect
npm@types/mssql3.1.29indirect
npm@types/node6.0.46indirect
npm@types/qs6.2.30indirect
npm@types/serve-static1.7.31indirect
npmaccepts1.3.3indirect
npmarray-flatten1.1.1indirect
npmasap2.0.5indirect
npmassertion-error1.0.2indirect
npmbabel-runtime5.8.38indirect
npmbalanced-match0.4.2indirect
npmbig-number0.3.1indirect
npmbl1.1.2indirect
npmbody-parser1.15.2indirect
npmbrace-expansion1.1.6indirect
npmbrowser-stdout1.3.0indirect
npmbuffer-shims1.0.0indirect
npmbytes2.4.0indirect
npmchai3.5.0indirect
npmcommander2.9.0indirect
npmconcat-map0.0.1indirect
npmconfig1.24.0indirect
npmcontent-disposition0.5.1indirect
npmcontent-type1.0.2indirect
npmcookie0.3.1indirect
npmcookie-signature1.0.6indirect
npmcore-js1.2.7indirect
npmcore-util-is1.0.2indirect
npmcors2.8.1indirect
npmdebug2.2.0indirect
npmdeep-eql0.1.3indirect
npmdepd1.1.0indirect
npmdestroy1.0.4indirect
npmdiff1.4.0indirect
npmee-first1.1.1indirect
npmencodeurl1.0.1indirect
npmescape-html1.0.3indirect
npmescape-string-regexp1.0.5indirect
npmetag1.7.0indirect
npmexpress4.14.0indirect
npmextend3.0.0indirect
npmfinalhandler0.5.0indirect
npmforwarded0.1.0indirect
npmfresh0.3.0indirect
npmfs.realpath1.0.0indirect
npmgeneric-pool2.4.4indirect
npmglob7.0.5indirect
npmgraceful-readlink1.0.1indirect
npmgrowl1.9.2indirect
npmhas-flag1.0.0indirect
npmhttp-errors1.5.0indirect
npmiconv-lite0.4.13indirect
npminflight1.0.6indirect
npminherits2.0.1indirect
npminherits2.0.3indirect
npmipaddr.js1.1.1indirect
npmisarray1.0.0indirect
npmjson33.3.2indirect
npmjson50.4.0indirect
npmlodash._baseassign3.2.0indirect
npmlodash._basecopy3.0.1indirect
npmlodash._basecreate3.0.3indirect
npmlodash._getnative3.9.1indirect
npmlodash._isiterateecall3.0.9indirect
npmlodash.create3.1.1indirect
npmlodash.isarguments3.1.0indirect
npmlodash.isarray3.0.4indirect
npmlodash.keys3.1.2indirect
npmmedia-typer0.3.0indirect
npmmerge-descriptors1.0.1indirect
npmmethods1.1.2indirect
npmmime1.3.4indirect
npmmime-db1.24.0indirect
npmmime-types2.1.12indirect
npmminimatch3.0.3indirect
npmminimist0.0.8indirect
npmmkdirp0.5.1indirect
npmmocha3.1.2indirect
npmms0.7.1indirect
npmmssql3.3.0indirect
npmnegotiator0.6.1indirect
npmodata-v4-metadata0.1.3indirect
npmodata-v4-server0.1.5indirect
npmodata-v4-service-document0.0.3indirect
npmodata-v4-service-metadata0.1.5indirect
npmon-finished2.3.0indirect
npmonce1.4.0indirect
npmparseurl1.3.1indirect
npmpath-is-absolute1.0.1indirect
npmpath-to-regexp0.1.7indirect
npmprocess-nextick-args1.0.7indirect
npmpromise7.1.1indirect
npmproxy-addr1.1.2indirect
npmqs6.2.0indirect
npmqs6.3.0indirect
npmrange-parser1.2.0indirect
npmraw-body2.1.7indirect
npmreadable-stream2.0.6indirect
npmreadable-stream2.1.5indirect
npmreflect-metadata0.1.8indirect
npmsemver5.3.0indirect
npmsend0.14.1indirect
npmserve-static1.11.1indirect
npmsetprototypeof1.0.1indirect
npmsprintf0.1.5indirect
npmstatuses1.3.0indirect
npmstring_decoder0.10.31indirect
npmsupports-color3.1.2indirect
npmtedious1.14.0indirect
npmtype-detect0.1.1indirect
npmtype-detect1.0.0indirect
npmtype-is1.6.13indirect
npmtypescript2.0.7indirect
npmunpipe1.0.0indirect
npmutil-deprecate1.0.2indirect
npmutils-merge1.0.0indirect
npmvary1.1.0indirect
npmwrappy1.0.2indirect
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.12.0 — full methodology · metrics wiki.

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