io.github.ErikEJ/SqlServer.Rules
version 1.0
- scanned 2026-10-16
- source github.com/ErikEJ/SqlServer.Rules
- commit ab012eb772c3
- transport stdio
- files read 2
- methodology 0.2.0
- ruleset 0.1.1
No tag matching version 1.0 was found in this repository, so the scan read the default branch instead. The findings below describe that code, not necessarily the released version.
100
100measured on 65% of this axis
63
97measured on 90% of this axis
30
The evidence
Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.
Auth Posture
- authentication_model
stdio transport: the client launches the server as a subprocess, so the OS process boundary is the auth boundary — `03` §4 does not penalise absent auth here
- transport_security
declared transport: stdio — launched as a subprocess by the client, so the security boundary is the client process, not a network port (`03` §4)
- secret_handling
detect-secrets matched 3 credential-shaped string(s), every one from a keyword or entropy heuristic (Base64 High Entropy String, Secret Keyword). Those flag placeholders, variable names and content hashes as readily as credentials, so they do not establish the committed credential `03` §4's 0 asserts, and this sub-check is not scored; Secret Keyword at docs/Design/SRD0075.md:39; Base64 High Entropy String at sqlprojects/AW/Tables/BillOfMaterials.sql:24; Secret Keyword at sqlprojects/TSQLSmellsTest/HardCodedCredentialsTest.sql:7
- authorization_granularity
no tool registration was recognised anywhere in the source. An MCP server registers tools by definition, so this is a gap in our detection rather than a server with none, and `03` §4's threshold cannot be applied to it.
Dependency Health
- vscode-extension/package-lock.jsonbraces 3.0.3 — GHSA-vfj7-8cjw-p6xm
transitive, CVSS 8.7
https://osv.dev/vulnerability/GHSA-vfj7-8cjw-p6xm - vscode-extension/package-lock.jsonbrace-expansion 5.0.9 — GHSA-6j4f-fj2g-mc7p
transitive, CVSS 7.5, fixed in 5.0.10
https://osv.dev/vulnerability/GHSA-6j4f-fj2g-mc7p - vscode-extension/package-lock.jsonbrace-expansion 5.0.9 — GHSA-qhr7-859c-m2p7
transitive, CVSS 7.5, fixed in 5.0.11
https://osv.dev/vulnerability/GHSA-qhr7-859c-m2p7 - vscode-extension/package-lock.jsonfast-uri 3.1.5 — GHSA-5jgf-p345-68v8
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-5jgf-p345-68v8 - vscode-extension/package-lock.jsonfast-uri 3.1.5 — GHSA-f65p-4m7j-42xc
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-f65p-4m7j-42xc - vscode-extension/package-lock.jsonfast-uri 3.1.5 — GHSA-fph4-wmhf-6fwf
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-fph4-wmhf-6fwf - vscode-extension/package-lock.jsonfast-uri 3.1.5 — GHSA-jqff-g426-hqxp
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-jqff-g426-hqxp - vscode-extension/package-lock.jsonfast-uri 3.1.5 — GHSA-qw65-cvwx-89v3
transitive, CVSS 7.5, fixed in 3.1.7
https://osv.dev/vulnerability/GHSA-qw65-cvwx-89v3 - vscode-extension/package-lock.jsonjs-yaml 4.3.1 — GHSA-2883-xcg3-v3hh
transitive, CVSS 7.5, fixed in 4.3.2
https://osv.dev/vulnerability/GHSA-2883-xcg3-v3hh - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-rfgv-xxqx-mfg5
transitive, CVSS 7.5, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-rfgv-xxqx-mfg5 - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-w293-vg96-wgc3
transitive, CVSS 7.4, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-w293-vg96-wgc3 - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-2jfj-6hjv-fm6j
transitive, CVSS 6.5, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-2jfj-6hjv-fm6j - vscode-extension/package-lock.jsonmarkdown-it 14.3.0 — GHSA-253c-mchw-3w2r
transitive, CVSS 6.3, fixed in 14.3.1
https://osv.dev/vulnerability/GHSA-253c-mchw-3w2r - vscode-extension/package-lock.jsonqs 6.15.3 — GHSA-4mjr-xmp4-gh2g
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-4mjr-xmp4-gh2g - vscode-extension/package-lock.jsonqs 6.15.3 — GHSA-x5fp-wj9c-mxmx
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-x5fp-wj9c-mxmx - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-3wwx-pv8p-q78v
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-3wwx-pv8p-q78v - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-3xpg-4rpp-hhhm
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-3xpg-4rpp-hhhm - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-pmjh-fq2x-6v4x
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-pmjh-fq2x-6v4x - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-rx4f-c7p8-82vq
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-rx4f-c7p8-82vq - vscode-extension/package-lock.jsonbrace-expansion 5.0.9 — GHSA-q2hr-2g5m-vwhr
transitive, CVSS 5.3, fixed in 5.0.12
https://osv.dev/vulnerability/GHSA-q2hr-2g5m-vwhr - vscode-extension/package-lock.jsonfast-uri 3.1.5 — GHSA-hrr3-gc8f-f4qj
transitive, CVSS 4.8, fixed in 3.1.8
https://osv.dev/vulnerability/GHSA-hrr3-gc8f-f4qj - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-2gqq-gqf2-x968
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-2gqq-gqf2-x968 - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-8436-99hf-9mmv
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-8436-99hf-9mmv - vscode-extension/package-lock.jsonundici 7.29.0 — GHSA-r53p-7pc4-xj5r
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-r53p-7pc4-xj5r
Maintenance
- recency
last commit 2 day(s) before 2026-10-16
- issue_responsiveness
median over 8 issue(s) in the last 6 months: 0.8 day(s) to first maintainer comment
- release_cadence
median release gap 37 days (by releases), last release 152 day(s) ago
- bus_factor
2 regular authors in the last 12 months
- repository_signals
`03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.
Transparency
- license
LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text
- readme_quality
README.md: exposed tools or resources enumerated (+30), states what the server does in the first 200 words (+20)
- declared_scopes
neither the README nor the MCP manifest documents what the server accesses or what side effects it has
- changelog
no CHANGELOG in the fetched source. `03` §7's partial credit for tagged releases carrying release notes is not applied here — that needs the forge API, which this check does not call
- security_contact
no SECURITY.md and no disclosure contact in the README, so a finder has no route to report a vulnerability privately
Contest a finding
Every number here comes from a rule reading published source, and rules get things wrong. If something on this page is incorrect — or correct but mitigated by a check the rule cannot see — open an issue and we answer it in writing. A finding we got wrong is removed and the rule is fixed; one that stands is answered on the record.
Anyone can file: the maintainer, a researcher who disagrees with the classification, or a user who tested the server and could not reproduce it. Name this server and the rule or advisory ID shown beside the finding above. We aim to reply within five business days and to resolve within ten.