ai.haymon/database
version 0.7.0
- scanned 2026-10-16
- source github.com/haymon-ai/database
- commit 54f40caed164
- transport streamable-http
- files read 21
- methodology 0.2.0
- ruleset 0.1.1
The registry lists this server with status deprecated (observed 2026-10-16). That is the publisher's own label, not a finding of ours, and no axis scores it. The scan below is current.
100
30measured on 40% of this axis
0measured on 84% of this axis
13 vulnerabilities could not be placed in `03` §6's table and are listed but not scored
86measured on 90% of this axis
91measured on 80% of this axis
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
network transport, and no authentication middleware, credential-header read, or inbound token verification appears anywhere in the source we fetched — `03` §4's "no authentication; HTTP transport" band
- transport_security
transport is streamable-http but the entry declares no endpoint URL to read a scheme from
- secret_handling
detect-secrets matched 4 credential-shaped string(s), every one from a keyword or entropy heuristic (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 .github/workflows/ci.yml:72; Secret Keyword at README.md:63; Secret Keyword at docs/content/docs/configuration.mdx:106; Secret Keyword at tests/compose.yml:10
- 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
Showing the 50 most severe of 85 findings on this axis. The score was computed over all of them — findings beyond the fourth of a severity still deduct at a tenth of their weight — so the remainder is omitted from this page, not from the arithmetic.
- docs/package-lock.jsonnext 16.2.1 — GHSA-2xp9-vwfh-vxw4
direct, CVSS 9.5, fixed in 16.3.3
https://osv.dev/vulnerability/GHSA-2xp9-vwfh-vxw4 - docs/package-lock.jsonnext 16.2.1 — GHSA-vcvr-r3jv-pc5j
direct, CVSS 9.5, fixed in 16.3.6
https://osv.dev/vulnerability/GHSA-vcvr-r3jv-pc5j - docs/package-lock.jsonnext 16.2.1 — GHSA-p293-qw3h-jr36
direct, CVSS 9.0, fixed in 16.3.3
https://osv.dev/vulnerability/GHSA-p293-qw3h-jr36 - docs/package-lock.jsonnext 16.2.1 — GHSA-c4j6-fc7j-m34r
direct, CVSS 8.6, fixed in 16.2.5
https://osv.dev/vulnerability/GHSA-c4j6-fc7j-m34r - docs/package-lock.jsonnext 16.2.1 — GHSA-6gpp-xcg3-4w24
direct, CVSS 8.3, fixed in 16.2.11
https://osv.dev/vulnerability/GHSA-6gpp-xcg3-4w24 - docs/package-lock.jsonnext 16.2.1 — GHSA-89xv-2m56-2m9x
direct, CVSS 8.3, fixed in 16.2.11
https://osv.dev/vulnerability/GHSA-89xv-2m56-2m9x - docs/package-lock.jsonnext 16.2.1 — GHSA-cjq9-62q9-8jv4
direct, CVSS 8.3, fixed in 16.3.8
https://osv.dev/vulnerability/GHSA-cjq9-62q9-8jv4 - docs/package-lock.jsonnext 16.2.1 — GHSA-p9j2-gv94-2wf4
direct, CVSS 8.3, fixed in 16.2.11
https://osv.dev/vulnerability/GHSA-p9j2-gv94-2wf4 - docs/package-lock.jsonnext 16.2.1 — GHSA-m99w-x7hq-7vfj
direct, CVSS 8.2, fixed in 16.2.11
https://osv.dev/vulnerability/GHSA-m99w-x7hq-7vfj - docs/package-lock.jsonnext 16.2.1 — GHSA-492v-c6pp-mqqv
direct, CVSS 8.1, fixed in 16.2.5
https://osv.dev/vulnerability/GHSA-492v-c6pp-mqqv - docs/package-lock.jsonnext 16.2.1 — GHSA-267c-6grr-h53f
direct, CVSS 7.5, fixed in 16.2.5
https://osv.dev/vulnerability/GHSA-267c-6grr-h53f - docs/package-lock.jsonnext 16.2.1 — GHSA-26hh-7cqf-hhc6
direct, CVSS 7.5, fixed in 16.2.6
https://osv.dev/vulnerability/GHSA-26hh-7cqf-hhc6 - docs/package-lock.jsonnext 16.2.1 — GHSA-36qx-fr4f-26g5
direct, CVSS 7.5, fixed in 16.2.5
https://osv.dev/vulnerability/GHSA-36qx-fr4f-26g5 - docs/package-lock.jsonnext 16.2.1 — GHSA-8h8q-6873-q5fj
direct, CVSS 7.5, fixed in 16.2.5
https://osv.dev/vulnerability/GHSA-8h8q-6873-q5fj - docs/package-lock.jsonnext 16.2.1 — GHSA-mg66-mrh9-m8jx
direct, CVSS 7.5, fixed in 16.2.5
https://osv.dev/vulnerability/GHSA-mg66-mrh9-m8jx - docs/package-lock.jsonnext 16.2.1 — GHSA-q4gf-8mx6-v5v3
direct, CVSS 7.5, fixed in 16.2.3
https://osv.dev/vulnerability/GHSA-q4gf-8mx6-v5v3 - docs/package-lock.jsonpostcss 8.4.31 — GHSA-6g55-p6wh-862q
direct, CVSS 7.5, fixed in 8.5.12
https://osv.dev/vulnerability/GHSA-6g55-p6wh-862q - docs/package-lock.jsonpostcss 8.5.8 — GHSA-6g55-p6wh-862q
direct, CVSS 7.5, fixed in 8.5.12
https://osv.dev/vulnerability/GHSA-6g55-p6wh-862q - docs/package-lock.jsonpostcss 8.4.31 — GHSA-r28c-9q8g-f849
direct, CVSS 7.5, fixed in 8.5.18
https://osv.dev/vulnerability/GHSA-r28c-9q8g-f849 - docs/package-lock.jsonpostcss 8.5.8 — GHSA-r28c-9q8g-f849
direct, CVSS 7.5, fixed in 8.5.18
https://osv.dev/vulnerability/GHSA-r28c-9q8g-f849 - docs/package-lock.jsonsharp 0.34.5 — GHSA-rgj7-g3m4-5g8c
transitive, CVSS 8.9, fixed in 0.35.4
https://osv.dev/vulnerability/GHSA-rgj7-g3m4-5g8c - docs/package-lock.jsonsharp 0.34.5 — GHSA-wq5f-xc86-pv6w
transitive, CVSS 8.9, fixed in 0.35.5
https://osv.dev/vulnerability/GHSA-wq5f-xc86-pv6w - docs/package-lock.jsonimage-size 2.0.2 — GHSA-5p2g-fcmc-qvqq
transitive, CVSS 8.7, fixed in 2.0.3
https://osv.dev/vulnerability/GHSA-5p2g-fcmc-qvqq - docs/package-lock.jsonimage-size 2.0.2 — GHSA-w3rx-r6r6-pgpr
transitive, CVSS 8.7, fixed in 2.0.3
https://osv.dev/vulnerability/GHSA-w3rx-r6r6-pgpr - docs/package-lock.jsonsource-map-js 1.2.1 — GHSA-68fv-2mgg-jv7q
transitive, CVSS 8.7, fixed in 1.2.2
https://osv.dev/vulnerability/GHSA-68fv-2mgg-jv7q - docs/package-lock.jsonnanoid 3.3.11 — GHSA-28wg-ghj8-5hjv
transitive, CVSS 8.2, fixed in 3.3.16
https://osv.dev/vulnerability/GHSA-28wg-ghj8-5hjv - docs/package-lock.jsonnanoid 3.3.11 — GHSA-2v37-7h3g-55p8
transitive, CVSS 8.2, fixed in 3.3.18
https://osv.dev/vulnerability/GHSA-2v37-7h3g-55p8 - docs/package-lock.jsonbrace-expansion 1.1.13 — GHSA-3jxr-9vmj-r5cp
transitive, CVSS 7.7, fixed in 1.1.16
https://osv.dev/vulnerability/GHSA-3jxr-9vmj-r5cp - docs/package-lock.jsonbrace-expansion 1.1.13 — GHSA-6j4f-fj2g-mc7p
transitive, CVSS 7.5, fixed in 1.1.19
https://osv.dev/vulnerability/GHSA-6j4f-fj2g-mc7p - docs/package-lock.jsonbrace-expansion 1.1.13 — GHSA-mh99-v99m-4gvg
transitive, CVSS 7.5, fixed in 1.1.17
https://osv.dev/vulnerability/GHSA-mh99-v99m-4gvg - docs/package-lock.jsonbrace-expansion 1.1.13 — GHSA-qhr7-859c-m2p7
transitive, CVSS 7.5, fixed in 1.1.20
https://osv.dev/vulnerability/GHSA-qhr7-859c-m2p7 - docs/package-lock.jsonbrace-expansion 1.1.13 — GHSA-rgw5-rvv9-x895
transitive, CVSS 7.5, fixed in 1.1.18
https://osv.dev/vulnerability/GHSA-rgw5-rvv9-x895 - docs/package-lock.jsoncompression 1.8.1 — GHSA-vc2v-76pw-4v95
transitive, CVSS 7.5, fixed in 1.8.2
https://osv.dev/vulnerability/GHSA-vc2v-76pw-4v95 - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-4c8g-83qw-93j6
transitive, CVSS 7.5, fixed in 3.1.3
https://osv.dev/vulnerability/GHSA-4c8g-83qw-93j6 - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-7p8r-x3mc-p8w7
transitive, CVSS 7.5, fixed in 3.1.5
https://osv.dev/vulnerability/GHSA-7p8r-x3mc-p8w7 - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-f65p-4m7j-42xc
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-f65p-4m7j-42xc - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-jqff-g426-hqxp
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-jqff-g426-hqxp - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-q3j6-qgpj-74h6
transitive, CVSS 7.5, fixed in 3.1.1
https://osv.dev/vulnerability/GHSA-q3j6-qgpj-74h6 - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-qw65-cvwx-89v3
transitive, CVSS 7.5, fixed in 3.1.7
https://osv.dev/vulnerability/GHSA-qw65-cvwx-89v3 - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-v2hh-gcrm-f6hx
transitive, CVSS 7.5, fixed in 3.1.4
https://osv.dev/vulnerability/GHSA-v2hh-gcrm-f6hx - docs/package-lock.jsonfast-uri 3.1.0 — GHSA-v39h-62p7-jpjc
transitive, CVSS 7.5, fixed in 3.1.2
https://osv.dev/vulnerability/GHSA-v39h-62p7-jpjc - docs/package-lock.jsonjs-yaml 4.1.1 — GHSA-2883-xcg3-v3hh
transitive, CVSS 7.5, fixed in 4.3.2
https://osv.dev/vulnerability/GHSA-2883-xcg3-v3hh - docs/package-lock.jsonjs-yaml 4.1.1 — GHSA-52cp-r559-cp3m
transitive, CVSS 7.5, fixed in 4.3.0
https://osv.dev/vulnerability/GHSA-52cp-r559-cp3m - docs/package-lock.jsonjs-yaml 4.1.1 — GHSA-5p4m-2wfm-xmqj
transitive, CVSS 7.5, fixed in 4.3.1
https://osv.dev/vulnerability/GHSA-5p4m-2wfm-xmqj - docs/package-lock.jsonnanoid 3.3.11 — GHSA-xwg4-73v4-xw9w
transitive, CVSS 7.4, fixed in 3.3.12
https://osv.dev/vulnerability/GHSA-xwg4-73v4-xw9w - docs/package-lock.jsonsharp 0.34.5 — GHSA-f88m-g3jw-g9cj
transitive, CVSS 7.0, fixed in 0.35.0
https://osv.dev/vulnerability/GHSA-f88m-g3jw-g9cj - Cargo.lockrmcp 1.5.0 — GHSA-33f5-2c5q-wgwj
direct or transitive unknown — no parseable manifest for this ecosystem, CVSS 8.2, fixed in 2.0.0
https://osv.dev/vulnerability/GHSA-33f5-2c5q-wgwj - Cargo.lockrmcp 1.5.0 — GHSA-9pj6-vhgr-3mwh
direct or transitive unknown — no parseable manifest for this ecosystem, CVSS 7.5, fixed in 2.0.0
https://osv.dev/vulnerability/GHSA-9pj6-vhgr-3mwh - Cargo.lockrustls-webpki 0.103.12 — RUSTSEC-2026-0104
direct or transitive unknown — no parseable manifest for this ecosystem, CVSS 7.5, fixed in 0.103.13
https://osv.dev/vulnerability/RUSTSEC-2026-0104 - docs/package-lock.jsonnext 16.2.1 — GHSA-4633-3j49-mh5q
direct, CVSS 6.3, fixed in 16.2.11
https://osv.dev/vulnerability/GHSA-4633-3j49-mh5q
Maintenance
- recency
last commit 28 day(s) before 2026-10-16
- issue_responsiveness
median over 4 issue(s) in the last 6 months: 3.5 day(s) to first maintainer comment
- release_cadence
median release gap 2 days (by releases), last release 140 day(s) ago
- bus_factor
sole maintainer
- 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: installation instructions (+25), configuration documented (+25), exposed tools or resources enumerated (+30), states what the server does in the first 200 words (+20)
- declared_scopes
specific scope or access documentation is present, but `03` §7's 100 and 60 bands both compare it against scopes INFERRED from static analysis, which is not built yet. Scoring 100 on an empty inference would be a vacuous truth — 'all ∅ inferred scopes are documented'.
- changelog
CHANGELOG.md present
- security_contact
SECURITY.md present
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.