Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 12:06 UTC

synatic / noql

Converts SQL queries into MongoDB queries or aggregation pipelines

JavaScriptGPL-3.0★ 55 stars⑂ 14 forkssince Mar 2021View on GitHub ↗

synatic/noql holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (84/100) and lowest on Community & Adoption (48/100). It was last updated 38 days ago. A single contributor accounts for most of its recent work.

81
overall / 100
Excellent

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.

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

Ownership

SynaticOrganization · verified domain
13 followers21 public repossince Jul 2019

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

Package ecosystems

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
18/36Push recency — last push 38 days ago
12.5/36Commit cadence — 18/52 weeks with commits
18/18Commit volume — 106 commits in the last year
10/10OpenSSF Scorecard: Maintained — 19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year106
human_commit_share1
days_since_last_push38
active_weeks_last_year18

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 40 days ago
27/27Release cadence — a release every ~10.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv6.0.18
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases10.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?

48Weak · 17% of overall
How it's scored
28.1/60Stars — 55 stars
9.3/25Forks — 14 forks
2.7/15Watchers — 4 watchers
Inputs used
forks14
stars55
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
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
47/80Monthly downloads — 3,320 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@synatic/noql
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,320
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 factor — 1 contributor(s) cover half of all commits
9.2/22.5Commit distribution — top contributor authored 59% of commits
13.5/13.5Contributor breadth — 10 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.59
How it's scored
25.2/42Issue resolution — 60% of issues closed
17.4/30PR acceptance — 139/240 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs139
open_issues6
closed_issues9
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.6
closed_unmerged_prs101
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
30/30Ownership backing — organization-owned
20/20Verified domain
8.2/25Owner reach — 13 followers of synatic
21.8/25Track record — 21 public repos, account ~7 yr old
Inputs used
followers13
owner_typeOrganization
is_verifiedyes
owner_loginsynatic
public_repos21
account_age_days2,652

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 40 days ago
20/20Version history — 72 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@synatic/noql
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://noql.synatic.dev/
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsmongodb, postgres, sql, javascript, query
has_wikiyes
homepagehttps://noql.synatic.dev/
docs_sitehttps://noql.synatic.dev/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 9 out of 9 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
7.5/7.5Code-Review — all changesets reviewed
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 — 19 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
5/5SAST — SAST tool is run on all commits
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
14.4/25Indirect dependencies free of known advisories — 1 affected: sprintf-js 1.1.3 (moderate 5.3)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages38
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages0
Matched the npm:@synatic/noql@6.0.18 runtime dependency closure — what installing the published package pulls in — 38 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.

58Moderate · 4% of overall
How it's scored
45/45Agent instructions — .cursorrules
0/15Machine-readable docs (llms.txt)
31.5/40Legible commit history — 59 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.59
agent_instruction_files.cursorrules
agent_instruction_max_bytes1,425
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — jsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsjsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (jsconfig.json)
51.1/55Manageable file sizes — 7/99 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes3,065,980
source_files_sampled99
oversized_source_files7

Key facts

55GitHub stars
10contributors
106commits, last 12 months
38days since last push
100releases
1bus factor
6open 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 ★ / 14 ⇿
0Stars
14Forks
100Releases

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.

03581013151412022-032024-062026-10
Major 2Minor 0Patch 28

Each point covers 5 days.

OpenSSF Scorecard 6.9 / 10
6.9aggregate

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-19 12:05 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained19 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
npm@synatic/json-magic^2.0.2package.json
npm@synatic/schema-magic^3.0.0package.json
npm@synatic/type-magic^2.0.1package.json
npmbson7.2.0package.json
npmcheck-types11.2.3package.json
npmclone-deep4.0.1package.json
npmdayjs1.11.20package.json
npmdeepmerge4.3.1package.json
npmlodash4.18.1package.json
npmnode-sql-parser5.3.3package.json
npmobject-hash3.0.0package.json
All dependencies 38

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

RegistryPackageVersionRelation
npm@synatic/json-magic^2.0.2direct
npm@synatic/schema-magic^3.0.0direct
npm@synatic/type-magic^2.0.1direct
npmbson7.2.0direct
npmcheck-types11.2.3direct
npmclone-deep4.0.1direct
npmdayjs1.11.20direct
npmdeepmerge4.3.1direct
npmlodash4.18.1direct
npmnode-sql-parser5.3.3direct
npmobject-hash3.0.0direct
npm@synatic/eslint-config-synatic-node2.0.0indirect
npm@types/mocha10.0.10indirect
npmasync3.2.6indirect
npmclean-webpack-plugin4.0.0indirect
npmdeep-equal2.2.3indirect
npmeslint8.57.1indirect
npmeslint-config-google0.14.0indirect
npmeslint-config-prettier9.1.2indirect
npmeslint-plugin-import2.32.0indirect
npmeslint-plugin-jsdoc48.11.0indirect
npmeslint-plugin-node11.1.0indirect
npmeslint-plugin-prettier5.5.5indirect
npmeslint-plugin-promise6.6.0indirect
npmeslint-plugin-security1.7.1indirect
npmeslint-plugin-sonarjs0.25.1indirect
npmjson-schema0.4.0indirect
npmmocha12.0.0-beta-9.4indirect
npmmoment2.30.1indirect
npmmongodb7.2.0indirect
npmmongodb-language-model2.3.0indirect
npmnyc17.1.0indirect
npmpg8.21.0indirect
npmprettier3.8.3indirect
npmunderscore.string3.3.6indirect
npmwebpack5.107.2indirect
npmwebpack-bundle-analyzer4.10.2indirect
npmwebpack-cli5.1.4indirect
Dependency advisories 1

Installing npm:@synatic/noql@6.0.18 pulls in 38 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
sprintf-js1.1.3indirectmoderate1—

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.