io.github.dockersamples/mcp-docker-release-information
version 0.3.0
- scanned 2026-10-16
- source github.com/dockersamples/mcp-docker-release-information
- commit 42644818e7f8
- transport stdio
- files read 2
- methodology 0.2.0
- ruleset 0.1.1
100
100
28
21measured on 65% of this axis
18
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
no committed credential found, and no environment variable with a credential-shaped name is read anywhere in the source
- authorization_granularity
2 tool registration(s) detected — at or below `03` §4's threshold of 3, so there is no multi-tool surface to segregate
Dependency Health
- package-lock.jsonproxy-addr 2.0.7 — GHSA-jqcg-44mw-7w3h
transitive, CVSS 9.1, fixed in 2.0.8
https://osv.dev/vulnerability/GHSA-jqcg-44mw-7w3h - package-lock.json@modelcontextprotocol/sdk 1.17.5 — GHSA-8r9q-7v3j-jr4g
direct, CVSS 8.7, fixed in 1.25.2
https://osv.dev/vulnerability/GHSA-8r9q-7v3j-jr4g - package-lock.json@modelcontextprotocol/sdk 1.17.5 — GHSA-w48q-cv73-mx4w
direct, CVSS 7.6, fixed in 1.24.0
https://osv.dev/vulnerability/GHSA-w48q-cv73-mx4w - package-lock.json@modelcontextprotocol/sdk 1.17.5 — GHSA-6qxp-vccf-f47h
direct, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.json@modelcontextprotocol/sdk 1.17.5 — GHSA-345p-7cg4-v4c7
direct, CVSS 7.1, fixed in 1.26.0
https://osv.dev/vulnerability/GHSA-345p-7cg4-v4c7 - package-lock.jsonbraces 3.0.3 — GHSA-vfj7-8cjw-p6xm
transitive, CVSS 8.7
https://osv.dev/vulnerability/GHSA-vfj7-8cjw-p6xm - package-lock.jsonminimatch 3.1.2 — GHSA-3ppc-4f35-3m26
transitive, CVSS 8.7, fixed in 3.1.3
https://osv.dev/vulnerability/GHSA-3ppc-4f35-3m26 - package-lock.jsonbrace-expansion 1.1.12 — GHSA-3jxr-9vmj-r5cp
transitive, CVSS 7.7, fixed in 1.1.16
https://osv.dev/vulnerability/GHSA-3jxr-9vmj-r5cp - package-lock.jsonbrace-expansion 1.1.12 — GHSA-6j4f-fj2g-mc7p
transitive, CVSS 7.5, fixed in 1.1.19
https://osv.dev/vulnerability/GHSA-6j4f-fj2g-mc7p - package-lock.jsonbrace-expansion 1.1.12 — GHSA-mh99-v99m-4gvg
transitive, CVSS 7.5, fixed in 1.1.17
https://osv.dev/vulnerability/GHSA-mh99-v99m-4gvg - package-lock.jsonbrace-expansion 1.1.12 — GHSA-qhr7-859c-m2p7
transitive, CVSS 7.5, fixed in 1.1.20
https://osv.dev/vulnerability/GHSA-qhr7-859c-m2p7 - package-lock.jsonbrace-expansion 1.1.12 — GHSA-rgw5-rvv9-x895
transitive, CVSS 7.5, fixed in 1.1.18
https://osv.dev/vulnerability/GHSA-rgw5-rvv9-x895 - package-lock.jsonminimatch 3.1.2 — GHSA-23c5-xmqv-rm74
transitive, CVSS 7.5, fixed in 3.1.4
https://osv.dev/vulnerability/GHSA-23c5-xmqv-rm74 - package-lock.jsonminimatch 3.1.2 — GHSA-7r86-cg39-jmmj
transitive, CVSS 7.5, fixed in 3.1.3
https://osv.dev/vulnerability/GHSA-7r86-cg39-jmmj - package-lock.jsonpath-to-regexp 8.3.0 — GHSA-j3q9-mxjg-w52f
transitive, CVSS 7.5, fixed in 8.4.0
https://osv.dev/vulnerability/GHSA-j3q9-mxjg-w52f - package-lock.jsonpicomatch 2.3.1 — GHSA-c2c7-rcm5-vvqj
transitive, CVSS 7.5, fixed in 2.3.2
https://osv.dev/vulnerability/GHSA-c2c7-rcm5-vvqj - package-lock.jsonbrace-expansion 1.1.12 — GHSA-f886-m6hf-6m8v
transitive, CVSS 6.5, fixed in 1.1.13
https://osv.dev/vulnerability/GHSA-f886-m6hf-6m8v - package-lock.jsonqs 6.14.0 — GHSA-4mjr-xmp4-gh2g
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-4mjr-xmp4-gh2g - package-lock.jsonqs 6.14.0 — GHSA-6rw7-vpxm-498p
transitive, CVSS 6.3, fixed in 6.14.1
https://osv.dev/vulnerability/GHSA-6rw7-vpxm-498p - package-lock.jsonqs 6.14.0 — GHSA-q8mj-m7cp-5q26
transitive, CVSS 6.3, fixed in 6.15.2
https://osv.dev/vulnerability/GHSA-q8mj-m7cp-5q26 - package-lock.jsonpath-to-regexp 8.3.0 — GHSA-27v5-c462-wpq7
transitive, CVSS 5.9, fixed in 8.4.0
https://osv.dev/vulnerability/GHSA-27v5-c462-wpq7 - package-lock.jsonajv 6.12.6 — GHSA-2g4f-4pwh-qvx6
transitive, CVSS 5.5, fixed in 6.14.0
https://osv.dev/vulnerability/GHSA-2g4f-4pwh-qvx6 - package-lock.jsonbody-parser 2.2.0 — GHSA-wqch-xfxh-vrr4
transitive, CVSS 5.5, fixed in 2.2.1
https://osv.dev/vulnerability/GHSA-wqch-xfxh-vrr4 - package-lock.jsonbrace-expansion 1.1.12 — GHSA-q2hr-2g5m-vwhr
transitive, CVSS 5.3, fixed in 1.1.21
https://osv.dev/vulnerability/GHSA-q2hr-2g5m-vwhr - package-lock.jsonpicomatch 2.3.1 — GHSA-3v7f-55p6-f55p
transitive, CVSS 5.3, fixed in 2.3.2
https://osv.dev/vulnerability/GHSA-3v7f-55p6-f55p - package-lock.jsonbody-parser 2.2.0 — GHSA-v422-hmwv-36x6
transitive, CVSS 3.7, fixed in 2.3.0
https://osv.dev/vulnerability/GHSA-v422-hmwv-36x6 - package-lock.jsonqs 6.14.0 — GHSA-w7fw-mjwx-w883
transitive, CVSS 3.7, fixed in 6.14.2
https://osv.dev/vulnerability/GHSA-w7fw-mjwx-w883
Maintenance
- recency
last commit 206 day(s) before 2026-10-16
- issue_responsiveness
this repository has no issues `03` §5's window covers. An unanswered issue scores 0 under §5, but a repository with no issues filed has not failed to answer one.
- release_cadence
no release in 401 days (by releases) — over a year
- bus_factor
no author reached `03` §5's 5-commit bar in the last 12 months (1 contributor(s) with fewer) — scored at §5's weakest described band, which the section defines for a quiet 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 'Apache-2.0' from its text
- readme_quality
README.md is under `03` §7's 500-byte floor, which scores 0 regardless of content
- 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.