Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 22:58 UTC

SPLOX-HQ / node-sdk

Official Splox SDK

TypeScriptMIT★ 0 stars⑂ 0 forkssince Feb 2026View on GitHub ↗

SPLOX-HQ/node-sdk holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (52/100) and lowest on Sustainability & Governance (15/100). It was last updated 62 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

SploxOrganization
0 followers4 public repossince Jul 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmsploxpoints to another repo — not scored0.5.4680396 days agosploxaiharnessagentsdkapi

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
18/36Push recencylast push 62 days ago
3.5/36Commit cadence5/52 weeks with commits
10.6/18Commit volume14 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year14
human_commit_share
days_since_last_push62
active_weeks_last_year5
How it's scored
16.2/27Ships releases3 version tags (no GitHub releases)
27/36Release recencylatest release 91 days ago
19.8/27Release cadencea release every ~59 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv0.0.16
releases_from_tagsyes
days_since_latest_release91
mean_days_between_releases59
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?

24At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
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_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

15Critical · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/14 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
0/25Owner reach0 followers of SPLOX-HQ
5.4/25Track record4 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginSPLOX-HQ
public_repos4
account_age_days50

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 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
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
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?

38Weak · 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-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/14 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.2
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

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
advisories16
affected_packages8
assessed_packages155
unassessed_packages0
affected_by_severitycritical 2, high 4, moderate 1, low 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 155 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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.splox.io/llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.splox.io/llms.txt
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-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
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.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/23 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes17,896
source_files_sampled23
oversized_source_files0

Key facts

0GitHub stars
1contributors
14commits, last 12 months
62days since last push
3releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • npm package 'splox' points at a different repository (https://github.com/splox-ai/node-sdk); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 2.2 / 10
2.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-09-05 22:58 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/14 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities16 existing vulnerabilities detected
All dependencies 155

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

RegistryPackageVersionRelation
npm@esbuild/aix-ppc640.21.5indirect
npm@esbuild/aix-ppc640.27.3indirect
npm@esbuild/android-arm0.21.5indirect
npm@esbuild/android-arm0.27.3indirect
npm@esbuild/android-arm640.21.5indirect
npm@esbuild/android-arm640.27.3indirect
npm@esbuild/android-x640.21.5indirect
npm@esbuild/android-x640.27.3indirect
npm@esbuild/darwin-arm640.21.5indirect
npm@esbuild/darwin-arm640.27.3indirect
npm@esbuild/darwin-x640.21.5indirect
npm@esbuild/darwin-x640.27.3indirect
npm@esbuild/freebsd-arm640.21.5indirect
npm@esbuild/freebsd-arm640.27.3indirect
npm@esbuild/freebsd-x640.21.5indirect
npm@esbuild/freebsd-x640.27.3indirect
npm@esbuild/linux-arm0.21.5indirect
npm@esbuild/linux-arm0.27.3indirect
npm@esbuild/linux-arm640.21.5indirect
npm@esbuild/linux-arm640.27.3indirect
npm@esbuild/linux-ia320.21.5indirect
npm@esbuild/linux-ia320.27.3indirect
npm@esbuild/linux-loong640.21.5indirect
npm@esbuild/linux-loong640.27.3indirect
npm@esbuild/linux-mips64el0.21.5indirect
npm@esbuild/linux-mips64el0.27.3indirect
npm@esbuild/linux-ppc640.21.5indirect
npm@esbuild/linux-ppc640.27.3indirect
npm@esbuild/linux-riscv640.21.5indirect
npm@esbuild/linux-riscv640.27.3indirect
npm@esbuild/linux-s390x0.21.5indirect
npm@esbuild/linux-s390x0.27.3indirect
npm@esbuild/linux-x640.21.5indirect
npm@esbuild/linux-x640.27.3indirect
npm@esbuild/netbsd-arm640.27.3indirect
npm@esbuild/netbsd-x640.21.5indirect
npm@esbuild/netbsd-x640.27.3indirect
npm@esbuild/openbsd-arm640.27.3indirect
npm@esbuild/openbsd-x640.21.5indirect
npm@esbuild/openbsd-x640.27.3indirect
npm@esbuild/openharmony-arm640.27.3indirect
npm@esbuild/sunos-x640.21.5indirect
npm@esbuild/sunos-x640.27.3indirect
npm@esbuild/win32-arm640.21.5indirect
npm@esbuild/win32-arm640.27.3indirect
npm@esbuild/win32-ia320.21.5indirect
npm@esbuild/win32-ia320.27.3indirect
npm@esbuild/win32-x640.21.5indirect
npm@esbuild/win32-x640.27.3indirect
npm@jridgewell/gen-mapping0.3.13indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@rollup/rollup-android-arm-eabi4.57.1indirect
npm@rollup/rollup-android-arm644.57.1indirect
npm@rollup/rollup-darwin-arm644.57.1indirect
npm@rollup/rollup-darwin-x644.57.1indirect
npm@rollup/rollup-freebsd-arm644.57.1indirect
npm@rollup/rollup-freebsd-x644.57.1indirect
npm@rollup/rollup-linux-arm-gnueabihf4.57.1indirect
npm@rollup/rollup-linux-arm-musleabihf4.57.1indirect
npm@rollup/rollup-linux-arm64-gnu4.57.1indirect
npm@rollup/rollup-linux-arm64-musl4.57.1indirect
npm@rollup/rollup-linux-loong64-gnu4.57.1indirect
npm@rollup/rollup-linux-loong64-musl4.57.1indirect
npm@rollup/rollup-linux-ppc64-gnu4.57.1indirect
npm@rollup/rollup-linux-ppc64-musl4.57.1indirect
npm@rollup/rollup-linux-riscv64-gnu4.57.1indirect
npm@rollup/rollup-linux-riscv64-musl4.57.1indirect
npm@rollup/rollup-linux-s390x-gnu4.57.1indirect
npm@rollup/rollup-linux-x64-gnu4.57.1indirect
npm@rollup/rollup-linux-x64-musl4.57.1indirect
npm@rollup/rollup-openbsd-x644.57.1indirect
npm@rollup/rollup-openharmony-arm644.57.1indirect
npm@rollup/rollup-win32-arm64-msvc4.57.1indirect
npm@rollup/rollup-win32-ia32-msvc4.57.1indirect
npm@rollup/rollup-win32-x64-gnu4.57.1indirect
npm@rollup/rollup-win32-x64-msvc4.57.1indirect
npm@types/estree1.0.8indirect
npm@types/node20.19.33indirect
npm@vitest/expect2.1.9indirect
npm@vitest/mocker2.1.9indirect
npm@vitest/pretty-format2.1.9indirect
npm@vitest/runner2.1.9indirect
npm@vitest/snapshot2.1.9indirect
npm@vitest/spy2.1.9indirect
npm@vitest/utils2.1.9indirect
npmacorn8.15.0indirect
npmany-promise1.3.0indirect
npmassertion-error2.0.1indirect
npmbundle-require5.1.0indirect
npmcac6.7.14indirect
npmchai5.3.3indirect
npmcheck-error2.1.3indirect
npmchokidar4.0.3indirect
npmcommander4.1.1indirect
npmconfbox0.1.8indirect
npmconsola3.4.2indirect
npmdebug4.4.3indirect
npmdeep-eql5.0.2indirect
npmes-module-lexer1.7.0indirect
npmesbuild0.21.5indirect
npmesbuild0.27.3indirect
npmestree-walker3.0.3indirect
npmexpect-type1.3.0indirect
npmfdir6.5.0indirect
npmfix-dts-default-cjs-exports1.0.1indirect
npmfsevents2.3.3indirect
npmjoycon3.1.1indirect
npmlilconfig3.1.3indirect
npmlines-and-columns1.2.4indirect
npmload-tsconfig0.2.5indirect
npmloupe3.2.1indirect
npmmagic-string0.30.21indirect
npmmlly1.8.0indirect
npmms2.1.3indirect
npmmz2.7.0indirect
npmnanoid3.3.11indirect
npmobject-assign4.1.1indirect
npmpathe1.1.2indirect
npmpathe2.0.3indirect
npmpathval2.0.1indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.3indirect
npmpirates4.0.7indirect
npmpkg-types1.3.1indirect
npmpostcss8.5.6indirect
npmpostcss-load-config6.0.1indirect
npmreaddirp4.1.2indirect
npmresolve-from5.0.0indirect
npmrollup4.57.1indirect
npmsiginfo2.0.0indirect
npmsource-map0.7.6indirect
npmsource-map-js1.2.1indirect
npmstackback0.0.2indirect
npmstd-env3.10.0indirect
npmsucrase3.35.1indirect
npmthenify3.3.1indirect
npmthenify-all1.6.0indirect
npmtinybench2.9.0indirect
npmtinyexec0.3.2indirect
npmtinyglobby0.2.15indirect
npmtinypool1.1.1indirect
npmtinyrainbow1.2.0indirect
npmtinyspy3.0.2indirect
npmtree-kill1.2.2indirect
npmts-interface-checker0.1.13indirect
npmtsup8.5.1indirect
npmtypescript5.9.3indirect
npmufo1.6.3indirect
npmundici-types6.21.0indirect
npmvite5.4.21indirect
npmvite-node2.1.9indirect
npmvitest2.1.9indirect
npmwhy-is-node-running2.3.0indirect
Dependency advisories 8

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

PackageVersionRelationSeverityAdvisoriesFixed in
rollup4.57.1indirectcritical14.59.0
vitest2.1.9indirectcritical14.1.0
nanoid3.3.11indirecthigh35.1.16
picomatch4.0.3indirecthigh24.0.4
postcss8.5.6indirecthigh48.5.23
vite5.4.21indirecthigh38.0.16
esbuild0.21.5indirectmoderate10.25.0
esbuild0.27.3indirectlow10.28.1

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.