Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 11:34 UTC

josephg / node-foundationdb

Modern Node.js FoundationDB bindings

TypeScript · JavaScript · C++Custom license★ 128 stars⑂ 20 forkssince Apr 2018forkView on GitHub ↗
KindLibraryhow this is determined
#foundationdb#nodejs

josephg/node-foundationdb holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (58/100) and lowest on Vitality (22/100). It was last updated 513 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Seph GentlePersonal account
1,328 followers165 public repossince Jan 2009

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
npmfoundationdb2.0.113,957411186 days agofoundationdbfdbdatabasenosqlacid

Metrics by category

Vitality

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

22At Risk · 21% of overall

Development activity

1Critical
How it's scored
0/36Push recency — last push 513 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 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_push513
active_weeks_last_year0

Release discipline

54Moderate
How it's scored
27/27Ships releases — 26 releases published
0/36Release recency — latest release 2,018 days ago
27/27Release cadence — a release every ~31.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count26
latest_release_tagrelease-test
releases_from_tagsno
days_since_latest_release2,018
mean_days_between_releases31.1

Community & Adoption

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

44Weak · 17% of overall

Popularity & adoption

51Moderate
How it's scored
34.1/60Stars — 128 stars
10.7/25Forks — 20 forks
6.4/15Watchers — 15 watchers
Inputs used
forks20
stars128
watchers15
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

19Critical
How it's scored
0/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

69Good
How it's scored
55.3/80Monthly downloads — 13,957 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfoundationdb
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads13,957
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?

58Moderate · 23% of overall

Maintainer resilience (bus factor)

34At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.9/22.5Commit distribution — top contributor authored 92% of commits
13.5/13.5Contributor breadth — 12 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.917

Issue & PR responsiveness

65Good
How it's scored
32.9/42Issue resolution — 78% of issues closed
22.1/30PR acceptance — 14/19 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 4/29 approved changesets -- score normalized to 1
Inputs used
merged_prs14
open_issues13
closed_issues47
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.783
closed_unmerged_prs5
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.

Ownership & stewardship

72Good
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
22.5/25Owner reach — 1,328 followers of josephg
25/25Track record — 165 public repos, account ~17 yr old
Inputs used
followers1,328
owner_typeUser
is_verified—
owner_loginjosephg
public_repos165
account_age_days6,389
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

69Good
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 1,186 days ago
20/20Version history — 41 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesfoundationdb
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,186

Engineering Quality

Are baseline engineering and documentation practices in place?

37Weak · 19% of overall

Engineering practices

48Weak
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 5 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

20At Risk
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicsfoundationdb, nodejs
has_wikiyes
homepage—
docs_site—
has_readmeno
has_docs_dirno
has_descriptionno

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

30At Risk · 16% of overall

Security posture

30At Risk
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 4/29 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 17 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.2/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 19 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3
Excluded from scoring (no data or not applicable): Packaging. 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.

42Weak · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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.

Verify loop (build / test / typecheck)

52Moderate
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
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesyarn.lock
has_dockerfileno
typed_languageyes
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. Remaining weights renormalized.

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.9/55Manageable file sizes — 1/48 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes73,905
source_files_sampled48
oversized_source_files1

Key facts

128GitHub stars
12contributors
0commits, last 12 months
513days since last push
26releases
1bus factor
13open issues
npmpackage ecosystems

Data collection warnings

  • Community profile unavailable

More detail

OpenSSF Scorecard 3.0 / 10
3.0aggregate

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-17 11:34 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 5 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 4/29 approved changesets -- score normalized to 1
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities19 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmfdb-tuple^1.0.0package.json
npmnode-gyp-build^4.2.3package.json
All dependencies 130

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

RegistryPackageVersionRelation
npmfdb-tuple1.0.0direct
npmnode-gyp-build4.6.0direct
npm@cspotcode/source-map-support0.8.1indirect
npm@jridgewell/resolve-uri3.1.0indirect
npm@jridgewell/sourcemap-codec1.4.14indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@tsconfig/node101.0.9indirect
npm@tsconfig/node121.0.11indirect
npm@tsconfig/node141.0.3indirect
npm@tsconfig/node161.0.3indirect
npm@types/bindings1.5.1indirect
npm@types/mocha10.0.1indirect
npm@types/node18.14.0indirect
npm@types/xml2js0.4.11indirect
npmacorn8.8.2indirect
npmacorn-walk8.2.0indirect
npmansi-colors4.1.1indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.3indirect
npmarg4.1.3indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbase64-js1.5.1indirect
npmbinary-extensions2.2.0indirect
npmbl4.1.0indirect
npmbrace-expansion1.1.11indirect
npmbrace-expansion2.0.1indirect
npmbraces3.0.2indirect
npmbrowser-stdout1.3.1indirect
npmbuffer5.7.1indirect
npmcamelcase6.3.0indirect
npmchalk4.1.2indirect
npmchokidar3.5.3indirect
npmchownr1.1.4indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcreate-require1.1.1indirect
npmdebug4.3.4indirect
npmdecamelize4.0.0indirect
npmdiff4.0.2indirect
npmdiff5.0.0indirect
npmemoji-regex8.0.0indirect
npmend-of-stream1.4.4indirect
npmescalade3.1.1indirect
npmescape-string-regexp4.0.0indirect
npmexecspawn1.0.1indirect
npmfill-range7.0.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfs-constants1.0.0indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.2indirect
npmget-caller-file2.0.5indirect
npmglob7.2.0indirect
npmglob-parent5.1.2indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npmieee7541.2.1indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmjs-yaml4.1.0indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmlru-cache6.0.0indirect
npmmake-error1.3.6indirect
npmminimatch3.1.2indirect
npmminimatch5.0.1indirect
npmminimist1.2.8indirect
npmmkdirp-classic0.5.3indirect
npmmocha10.2.0indirect
npmms2.1.2indirect
npmms2.1.3indirect
npmnanoid3.3.3indirect
npmnode-abi3.33.0indirect
npmnormalize-path3.0.0indirect
npmnpm-run-path3.1.0indirect
npmonce1.4.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpicomatch2.3.1indirect
npmprebuildify5.0.1indirect
npmpump3.0.0indirect
npmrandombytes2.1.0indirect
npmreadable-stream3.6.0indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmsafe-buffer5.2.1indirect
npmsax1.2.4indirect
npmsemver7.3.8indirect
npmserialize-javascript6.0.0indirect
npmstring-width4.2.3indirect
npmstring_decoder1.3.0indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtar-fs2.1.1indirect
npmtar-stream2.2.0indirect
npmto-regex-range5.0.1indirect
npmts-node10.9.1indirect
npmtypescript4.9.5indirect
npmutil-deprecate1.0.2indirect
npmutil-extend1.0.3indirect
npmv8-compile-cache-lib3.0.1indirect
npmworkerpool6.2.1indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmxml2js0.5.0indirect
npmxmlbuilder11.0.1indirect
npmy18n5.0.8indirect
npmyallist4.0.0indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.4indirect
npmyargs-parser20.2.9indirect
npmyargs-unparser2.0.0indirect
npmyn3.1.1indirect
npmyocto-queue0.1.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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with josephg/node-foundationdb. Read them side by side →

98mongodb/node-mongodb-nativeThe official MongoDB Node.js driverExceptional98Automattic/mongooseMongoDB object modeling designed to work in an asynchronous environment.Exceptional99taskforcesh/bullmqBullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQLExceptional98valkey-io/valkey-glideAn open source Valkey client library that supports Valkey, and Redis open source 6.2, 7.0 and 7.2. Valkey GLIDE is designed for reliability, optimized performance, and high-availability, for Valkey and Redis OSS based applications. GLIDE is a multi language client library, written in Rust with programming language bindings, such as Java and PythonExceptional97firebase/firebase-admin-nodeFirebase Admin Node.js SDKExceptional96mikro-orm/mikro-ormTypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, MariaDB, MS SQL Server, PostgreSQL and SQLite/libSQL databases.Exceptional

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

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