Public recordGood
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 20:04 UTC
Synapsor / Synapsor-Runner
Let AI agents query and update Postgres/MySQL without raw SQL, unrestricted schema access, or database credentials in the model; writes stay reviewed.
Synapsor/Synapsor-Runner holds a health index of 77 out of 100, placing it in the Good band. It scores highest on AI Readiness (85/100) and lowest on Community & Adoption (48/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.
77
overall / 100Software 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.
77
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)
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 66 is calibrated to 77 on the published index scale (record calibration 2026-08-02).
Ownership
SynapsorOrganization
0 followers1 public reposince Jul 2026
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | @synapsor/runner | 1.7.11 | 2,960 | 57 | 1 day ago | mcppostgresmysqlai-agentssql-safetydatabase-safetyopenai-agentsclaudecursorwritebackreplaymodel-context-protocoltext-to-sqlhuman-in-the-loopexecute-sqlprompt-injectiontenant-isolationdatabase-securityrls |
| npm | @synapsor/dsl | 1.10.0 | 1,325 | 20 | 2 days ago | synapsordslai-agentsmcpdatabase-safety |
| npm | @synapsor/spec | 1.10.0 | 1,505 | 16 | 2 days ago | synapsorai-agentsmcpdatabase-safetycontracts |
| npm | @synapsor/cli | 0.1.0-beta.1 | 32 | 1 | 36 days ago | — |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
68
Development activity
65Good
How it's scored
| 36/36 | Push recency — last push 1 days ago |
| 4.8/36 | Commit cadence — 7/52 weeks with commits |
| 18/18 | Commit volume — 173 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — no data |
Inputs used
| commits_last_year | 173 |
| human_commit_share | 1 |
| days_since_last_push | 1 |
| active_weeks_last_year | 7 |
Release discipline
72Good
How it's scored
| 16.2/27 | Ships releases — 1 version tags (no GitHub releases) |
| 36/36 | Release recency — latest release 41 days ago |
| 12.6/27 | Release cadence — cadence unknown (single release) |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 1 |
| latest_release_tag | v1.0.0 |
| releases_from_tags | yes |
| days_since_latest_release | 41 |
| mean_days_between_releases | — |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
48
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 2 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 2 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
92Excellent
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 3 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | github.com, shields.io |
| has_pull_request_template | yes |
Ecosystem adoption (downloads)
63Moderate
How it's scored
| 50.2/80 | Monthly downloads — 5,822 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | @synapsor/runner, @synapsor/dsl, @synapsor/spec, @synapsor/cli |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 5,822 |
| 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?
52
Maintainer resilience (bus factor)
12Critical
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0/22.5 | Commit distribution — top contributor authored 100% of commits |
| 1.4/13.5 | Contributor breadth — 1 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — no data |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 1 |
| top_contributor_share | 1 |
Issue & PR responsiveness
80Excellent
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 24.1/30 | PR acceptance — 49/61 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — no data |
Inputs used
| merged_prs | 49 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | 5 |
| prs_decided_7d | 5 |
| prs_merged_30d | 20 |
| prs_decided_30d | 20 |
| issue_closed_ratio | — |
| closed_unmerged_prs | 12 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
32At Risk
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 0/25 | Owner reach — 0 followers of Synapsor |
| 2.4/25 | Track record — 1 public repos, account ~0 yr old |
Inputs used
| followers | 0 |
| owner_type | Organization |
| is_verified | no |
| owner_login | Synapsor |
| public_repos | 1 |
| account_age_days | 47 |
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 4 package(s) on npm |
| 35/35 | Publish recency — latest publish 1 days ago |
| 20/20 | Version history — 57 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | @synapsor/runner, @synapsor/dsl, @synapsor/spec, @synapsor/cli |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 1 |
Engineering Quality
Are baseline engineering and documentation practices in place?
76
Engineering practices
60Moderate
How it's scored
| 24/24 | CI workflows — 5 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
100Exceptional
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://synapsor.ai/ |
| 10/10 | Repository description |
| 10/10 | Topics — 17 topics |
| 10/10 | Wiki |
Inputs used
| topics | agent-security, ai-agents, database-security, llm, mcp, model-context-protocol, mysql, open-source, postgresql, typescript, human-in-the-loop, llm-security, postgres, prompt-injection, rls, tenant-isolation, text-to-sql |
| has_wiki | yes |
| homepage | https://synapsor.ai/ |
| docs_site | https://synapsor.ai/ |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
84
Security posture
80Excellent
How it's scored
| 30/30 | Security policy (SECURITY.md) |
| 25/25 | Dependabot config |
| 25/25 | Dependency lockfiles — pnpm-lock.yaml |
| 0/20 | CodeQL workflow |
Inputs used
| source | file_signals |
| lockfiles | pnpm-lock.yaml |
| manifests | package.json |
| has_codeql_workflow | no |
| has_security_policy | yes |
| has_dependabot_config | yes |
Dependency advisories
100Exceptional
How it's scored
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
Inputs used
| source | osv |
| advisories | 0 |
| affected_packages | 0 |
| assessed_packages | 131 |
| unassessed_packages | 0 |
| affected_by_severity | none |
| direct_affected_packages | 0 |
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@synapsor/runner@1.7.11 runtime dependency closure — what installing the published package pulls in — 131 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.
85
Agent context & guidance
81Excellent
How it's scored
| 45/45 | Agent instructions — .cursor/rules/synapsor.mdc, .github/copilot-instructions.md, AGENTS.md, CLAUDE.md |
| 15/15 | Machine-readable docs (llms.txt) — llms.txt present |
| 21.3/40 | Legible commit history — 40 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | yes |
| llms_txt_url | — |
| legible_history_share | 0.4 |
| agent_instruction_files | .cursor/rules/synapsor.mdc, .github/copilot-instructions.md, AGENTS.md, CLAUDE.md |
| agent_instruction_max_bytes | 4,025 |
How it's scored
| 18/18 | One-command bootstrap — examples/claude-desktop-postgres/Makefile, examples/cursor-postgres/Makefile, examples/mysql-refund-agent/Makefile, examples/openai-agents-http/Makefile, examples/openai-agents-stdio/Makefile, examples/raw-sql-vs-synapsor/Makefile, examples/support-billing-agent/Makefile |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — apps/cloud-cli/tsconfig.json, apps/runner/tsconfig.json, packages/config/tsconfig.json, packages/control-plane-client/tsconfig.json, packages/dsl/tsconfig.json, packages/handler/tsconfig.json, packages/mcp-server/tsconfig.json, packages/mysql/tsconfig.json, packages/postgres/tsconfig.json, packages/proposal-store/tsconfig.json, packages/protocol/tsconfig.json, packages/schema-inspector/tsconfig.json, packages/spec/tsconfig.json, packages/worker-core/tsconfig.json, tsconfig.json |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 4/10 | Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited |
| 5/8 | Automated maintenance — dependency automation configured, none observed in the sampled commits |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | pnpm-lock.yaml |
| has_dockerfile | yes |
| typed_language | yes |
| bootstrap_files | examples/claude-desktop-postgres/Makefile, examples/cursor-postgres/Makefile, examples/mysql-refund-agent/Makefile, examples/openai-agents-http/Makefile, examples/openai-agents-stdio/Makefile, examples/raw-sql-vs-synapsor/Makefile, examples/support-billing-agent/Makefile |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | apps/cloud-cli/tsconfig.json, apps/runner/tsconfig.json, packages/config/tsconfig.json, packages/control-plane-client/tsconfig.json, packages/dsl/tsconfig.json, packages/handler/tsconfig.json, packages/mcp-server/tsconfig.json, packages/mysql/tsconfig.json, packages/postgres/tsconfig.json, packages/proposal-store/tsconfig.json, packages/protocol/tsconfig.json, packages/schema-inspector/tsconfig.json, packages/spec/tsconfig.json, packages/worker-core/tsconfig.json, tsconfig.json |
| agent_commit_share | 0.02 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
94Exceptional
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 48.7/55 | Manageable file sizes — 48/421 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 540,369 |
| source_files_sampled | 421 |
| oversized_source_files | 48 |
Machine-readable interfaces
100Exceptional
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — fixtures/generators/openapi/openapi.yaml |
| 20/20 | MCP server |
| 40/40 | Runnable examples — examples, recipes |
Inputs used
| example_dirs | examples, recipes |
| has_mcp_signal | yes |
| api_schema_files | fixtures/generators/openapi/openapi.yaml |
| interfaces_expected_of | — |
Key facts
2GitHub stars
1contributors
173commits, last 12 months
1days since last push
1releases
1bus factor
0open issues
npmpackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Could not fetch npm package '@synapsor-runner/mysql' from its registry
- Could not fetch npm package '@synapsor-runner/config' from its registry
- Could not fetch npm package '@synapsor/handler' from its registry
- Could not fetch npm package '@synapsor-runner/postgres' from its registry
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
- OpenSSF Scorecard did not return a usable result (Skipping github.com/Synapsor/Synapsor-Runner: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/Synapsor/Synapsor-Runner/legacy.tar.gz/refs/heads/main": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup codeload.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks
More detail
Direct dependencies 45
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | @modelcontextprotocol/sdk | 1.29.0 | apps/runner/package.json |
| npm | @synapsor/spec | workspace:^1.10.0 | apps/runner/package.json |
| npm | jose | 6.2.3 | apps/runner/package.json |
| npm | jsonc-parser | 3.3.1 | apps/runner/package.json |
| npm | mysql2 | ^3.11.0 | apps/runner/package.json |
| npm | pdf-lib | 1.17.1 | apps/runner/package.json |
| npm | pg | ^8.13.0 | apps/runner/package.json |
| npm | typescript | 5.9.3 | apps/runner/package.json |
| npm | vscode-languageserver | 9.0.1 | apps/runner/package.json |
| npm | vscode-languageserver-textdocument | 1.0.12 | apps/runner/package.json |
| npm | yaml | 2.8.3 | apps/runner/package.json |
| npm | zod | ^3.25.0 | apps/runner/package.json |
| npm | @synapsor/spec | workspace:* | packages/config/package.json |
| npm | @synapsor-runner/protocol | workspace:* | packages/control-plane-client/package.json |
| npm | @synapsor/spec | workspace:^1.10.0 | packages/dsl/package.json |
| npm | pg | ^8.13.0 | packages/handler/package.json |
| npm | zod | ^3.25.0 | packages/handler/package.json |
| npm | @modelcontextprotocol/ext-apps | 1.7.4 | packages/mcp-server/package.json |
| npm | @modelcontextprotocol/sdk | 1.29.0 | packages/mcp-server/package.json |
| npm | @synapsor-runner/config | workspace:* | packages/mcp-server/package.json |
| npm | @synapsor-runner/control-plane-client | workspace:* | packages/mcp-server/package.json |
| npm | @synapsor-runner/postgres | workspace:* | packages/mcp-server/package.json |
| npm | @synapsor-runner/proposal-store | workspace:* | packages/mcp-server/package.json |
| npm | @synapsor-runner/protocol | workspace:* | packages/mcp-server/package.json |
| npm | @synapsor-runner/schema-inspector | workspace:* | packages/mcp-server/package.json |
| npm | @synapsor/spec | workspace:* | packages/mcp-server/package.json |
| npm | jose | 6.2.3 | packages/mcp-server/package.json |
| npm | mysql2 | ^3.11.0 | packages/mcp-server/package.json |
| npm | pg | ^8.13.0 | packages/mcp-server/package.json |
| npm | zod | ^3.25.0 | packages/mcp-server/package.json |
| npm | zod-to-json-schema | 3.25.2 | packages/mcp-server/package.json |
| npm | @synapsor-runner/protocol | workspace:* | packages/mysql/package.json |
| npm | @synapsor-runner/worker-core | workspace:* | packages/mysql/package.json |
| npm | mysql2 | ^3.11.0 | packages/mysql/package.json |
| npm | @synapsor-runner/protocol | workspace:* | packages/postgres/package.json |
| npm | @synapsor-runner/worker-core | workspace:* | packages/postgres/package.json |
| npm | pg | ^8.13.0 | packages/postgres/package.json |
| npm | @synapsor-runner/protocol | workspace:* | packages/proposal-store/package.json |
| npm | zod | ^3.25.0 | packages/protocol/package.json |
| npm | @synapsor/runner | workspace:1.7.11 | packages/runner-alias/package.json |
| npm | @synapsor-runner/protocol | workspace:* | packages/schema-inspector/package.json |
| npm | mysql2 | ^3.11.0 | packages/schema-inspector/package.json |
| npm | pg | ^8.13.0 | packages/schema-inspector/package.json |
| npm | @synapsor-runner/control-plane-client | workspace:* | packages/worker-core/package.json |
| npm | @synapsor-runner/protocol | workspace:* | packages/worker-core/package.json |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
Dependency advisories 0
Installing npm:@synapsor/runner@1.7.11 pulls in 131 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.
No known advisories affect the assessed dependencies.
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.
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.