io.github.tsviz/actions-pulse
version 2.3.0
- scanned 2026-10-16
- source github.com/tsviz/github-mcp-server-devops
- commit 216028e6362e
- transport stdio
- files read 19
- methodology 0.2.0
- ruleset 0.1.1
87
100measured on 80% of this axis
0
52measured on 65% of this axis
58
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.
Code Safety
- src/github/org-client.ts:190mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
result.permissions = {}; for (const scope of result.scopes) { result.permissions[scope] = { granted: true, description: (PAT_SCOPES as any)[scope] || 'Unknown scope', - src/github/org-client.ts:1118mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
// Initialize repo stats if (!byRepository[repoName]) { byRepository[repoName] = { runs: 0, minutes: 0, success: 0, failure: 0 }; } - src/github/org-client.ts:1299mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
// Initialize repo stats if (!byRepository[repoName]) { byRepository[repoName] = { runs: 0, durations: [], queueTimes: [], failures: 0 }; } - src/config/config-loader.ts:373mcp-js-path-join-unvalidated (medium/low)
A filesystem path is assembled from a non-literal and read or written without confinement. path.join does not resolve away `..`, and path.resolve discards the base entirely on an absolute second component.
if (file.includes(policyType) && (file.endsWith('.yaml') || file.endsWith('.yml') || file.endsWith('.json'))) { try { const content = await fs.readFile(path.join(policyPath, file), 'utf-8'); const policy = this.parseConfig<T>(content, file); policies.push(policy); - src/config/config-loader.ts:494mcp-js-path-join-unvalidated (medium/low)
A filesystem path is assembled from a non-literal and read or written without confinement. path.join does not resolve away `..`, and path.resolve discards the base entirely on an absolute second component.
if (file.endsWith('.yaml') || file.endsWith('.yml') || file.endsWith('.json')) { try { const content = await fs.readFile(path.join(dashboardPath, file), 'utf-8'); const dashboard = this.parseConfig<DashboardConfig>(content, file); dashboards.push(dashboard);
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 4 credential-shaped string(s), every one from a keyword or entropy heuristic (Base64 High Entropy String). 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; Base64 High Entropy String at README.md:347; Base64 High Entropy String at docs/CONFIGURATION.md:89; Base64 High Entropy String at docs/QUICKSTART.md:47; Base64 High Entropy String at examples/mcp-docker.json:9
- authorization_granularity
33 tool registrations with conditional access logic present in the same source
Dependency Health
Showing the 50 most severe of 106 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.
- package-lock.jsonbasic-ftp 5.1.0 — GHSA-5rq4-664w-9x2c
transitive, CVSS 9.1, fixed in 5.2.0
https://osv.dev/vulnerability/GHSA-5rq4-664w-9x2c - 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.25.3 — 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.25.3 — GHSA-345p-7cg4-v4c7
direct, CVSS 7.1, fixed in 1.26.0
https://osv.dev/vulnerability/GHSA-345p-7cg4-v4c7 - package-lock.jsonflatted 3.3.3 — GHSA-rf6f-7fwh-wjgh
transitive, CVSS 8.9, fixed in 3.4.2
https://osv.dev/vulnerability/GHSA-rf6f-7fwh-wjgh - 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.jsonextract-zip 2.0.1 — GHSA-jmr9-qjv8-65gv
transitive, CVSS 8.6
https://osv.dev/vulnerability/GHSA-jmr9-qjv8-65gv - package-lock.jsonbasic-ftp 5.1.0 — GHSA-6v7q-wjvx-w8wg
transitive, CVSS 8.2, fixed in 5.2.2
https://osv.dev/vulnerability/GHSA-6v7q-wjvx-w8wg - package-lock.jsonbasic-ftp 5.1.0 — GHSA-c475-qrg2-pj4r
transitive, CVSS 8.2, fixed in 6.2.1
https://osv.dev/vulnerability/GHSA-c475-qrg2-pj4r - package-lock.jsonextract-zip 2.0.1 — GHSA-7pqw-9j4j-h8q3
transitive, CVSS 8.1
https://osv.dev/vulnerability/GHSA-7pqw-9j4j-h8q3 - 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.jsonip-address 10.1.0 — GHSA-mwp4-54f8-5fhr
transitive, CVSS 7.7, fixed in 10.3.1
https://osv.dev/vulnerability/GHSA-mwp4-54f8-5fhr - package-lock.json@hono/node-server 1.19.9 — GHSA-wc8c-qw6v-h7f6
transitive, CVSS 7.5, fixed in 1.19.10
https://osv.dev/vulnerability/GHSA-wc8c-qw6v-h7f6 - package-lock.jsonbasic-ftp 5.1.0 — GHSA-rp42-5vxx-qpwr
transitive, CVSS 7.5, fixed in 5.3.0
https://osv.dev/vulnerability/GHSA-rp42-5vxx-qpwr - package-lock.jsonbasic-ftp 5.1.0 — GHSA-rpmf-866q-6p89
transitive, CVSS 7.5, fixed in 5.3.1
https://osv.dev/vulnerability/GHSA-rpmf-866q-6p89 - 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.jsonbrowserslist 4.28.1 — GHSA-73wf-gq98-2v4g
transitive, CVSS 7.5, fixed in 4.28.7
https://osv.dev/vulnerability/GHSA-73wf-gq98-2v4g - package-lock.jsonbrowserslist 4.28.1 — GHSA-c83g-rgw3-j3cx
transitive, CVSS 7.5, fixed in 4.28.7
https://osv.dev/vulnerability/GHSA-c83g-rgw3-j3cx - 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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 - package-lock.jsonflatted 3.3.3 — GHSA-25h7-pfq9-p65f
transitive, CVSS 7.5, fixed in 3.4.0
https://osv.dev/vulnerability/GHSA-25h7-pfq9-p65f - package-lock.jsonhono 4.11.5 — GHSA-q5qw-h33p-qvwr
transitive, CVSS 7.5, fixed in 4.12.4
https://osv.dev/vulnerability/GHSA-q5qw-h33p-qvwr - package-lock.jsonjs-yaml 3.14.2 — GHSA-2883-xcg3-v3hh
transitive, CVSS 7.5, fixed in 3.15.2
https://osv.dev/vulnerability/GHSA-2883-xcg3-v3hh - 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 - package-lock.jsonjs-yaml 3.14.2 — GHSA-52cp-r559-cp3m
transitive, CVSS 7.5, fixed in 3.15.0
https://osv.dev/vulnerability/GHSA-52cp-r559-cp3m - 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 - package-lock.jsonjs-yaml 3.14.2 — GHSA-5p4m-2wfm-xmqj
transitive, CVSS 7.5, fixed in 3.15.1
https://osv.dev/vulnerability/GHSA-5p4m-2wfm-xmqj - 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 - 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 0.1.12 — GHSA-37ch-88jc-xwx2
transitive, CVSS 7.5, fixed in 0.1.13
https://osv.dev/vulnerability/GHSA-37ch-88jc-xwx2 - 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.jsonws 8.19.0 — GHSA-96hv-2xvq-fx4p
transitive, CVSS 7.5, fixed in 8.21.0
https://osv.dev/vulnerability/GHSA-96hv-2xvq-fx4p - package-lock.jsonhono 4.11.5 — GHSA-88fw-hqm2-52qc
transitive, CVSS 7.1, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-88fw-hqm2-52qc - package-lock.jsonyaml 2.8.2 — GHSA-48c2-rrv3-qjmp
direct, CVSS 4.3, fixed in 2.8.3
https://osv.dev/vulnerability/GHSA-48c2-rrv3-qjmp - package-lock.jsonsprintf-js 1.0.3 — GHSA-hp3w-g68c-fv3c
transitive, CVSS 6.9
https://osv.dev/vulnerability/GHSA-hp3w-g68c-fv3c - package-lock.jsonbaseline-browser-mapping 2.9.18 — GHSA-w5vr-8v7q-w6rv
transitive, CVSS 6.6, fixed in 2.11.0
https://osv.dev/vulnerability/GHSA-w5vr-8v7q-w6rv - 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.jsonhono 4.11.5 — GHSA-9vqf-7f2p-gf9v
transitive, CVSS 6.5, fixed in 4.12.16
https://osv.dev/vulnerability/GHSA-9vqf-7f2p-gf9v
Maintenance
- recency
last commit 250 day(s) before 2026-10-16
- issue_responsiveness
every issue read was filed by the project itself (13 by its maintainers or bots), so none is someone outside waiting for an answer, and `03` §5's question — will anyone read an issue I file? — has nothing to measure.
- release_cadence
median release gap 1 days (by releases), last release 250 day(s) ago
- bus_factor
sole maintainer, and no commit in over 90 days
- 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
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, but README.md documents a disclosure route — `03` §7 accepts either
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.