dev.veritap/locker
version 0.3.1
- scanned 2026-10-16
- source github.com/veritap-dev/veritap-locker
- commit 36c6fbbbe528
- transport streamable-http
- files read 32
- methodology 0.2.0
- ruleset 0.1.1
No tag matching version 0.3.1 was found in this repository, so the scan read the default branch instead. The findings below describe that code, not necessarily the released version.
87
2 vendored or minified paths were excluded before scanning; machine-generated bundles are not the server's own code
80measured on 25% of this axis
0
70measured on 45% of this axis
30measured 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.
Code Safety
- client/index.ts:192mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
}); if (res.status !== 200) return res; const up = await fetch(res.body.upload_url, { method: "PUT", body: bytes as unknown as BodyInit, - client/index.ts:215mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
}); if (res.status !== 200 || !res.body.body_url) return null; const blob = await fetch(res.body.body_url); if (!blob.ok) return null; return { bytes: new Uint8Array(await blob.arrayBuffer()), version: res.body.version ?? 0 }; - client/index.ts:249mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
if (env.body_b64) return unb64(env.body_b64); if (env.body_url) { const res = await fetch(env.body_url); if (!res.ok) return null; return new Uint8Array(await res.arrayBuffer()); - scripts/smoke-buy-echo.mjs:31mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
// 1. Get the 402 + PaymentRequired (header is authoritative in v2). const r1 = await fetch(url, { method: "POST", headers: { "Content-Type": "application/json" }, body }); if (r1.status !== 402) throw new Error(`expected 402, got ${r1.status}`); const paymentRequired = JSON.parse(Buffer.from(r1.headers.get("payment-required"), "base64").toString()); - scripts/smoke-buy-echo.mjs:43mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
// 4. Pay. const r2 = await fetch(url, { method: "POST", headers: { - src/sanctions.ts:31mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
const rpc = env.BASE_RPC_URL ?? "https://mainnet.base.org"; const data = SELECTOR + address.toLowerCase().replace(/^0x/, "").padStart(64, "0"); const res = await fetch(rpc, { method: "POST", headers: { "Content-Type": "application/json" },
Auth Posture
- authentication_model
no authentication appears in the source we fetched, but this server's network endpoint is a hosted remote, whose authentication can be enforced in front of its code — and no credential header is declared. An undeclared header is not an absent one, so `03` §4's "no authentication" band is not established.
- transport_security
declared endpoint(s) are HTTPS: https://locker.veritap.dev/mcp; scored 80, not 100: `03` §4 reserves 100 for HTTPS *with HSTS*, and an HSTS header can only be seen by connecting, which `04` §9 does not do. This is an unverifiable band, not an observed absence.
- secret_handling
detect-secrets matched 8 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; Base64 High Entropy String at .well-known/glimind-verification.txt:1; Secret Keyword at client/index.ts:89; Base64 High Entropy String at src/brand-assets.ts:6; Base64 High Entropy String at src/brand-assets.ts:7; Base64 High Entropy String at src/brand-assets.ts:8; Base64 High Entropy String at src/cli-bundle.ts:2; Secret Keyword at test/unit/stripe.test.ts:14; Secret Keyword at wrangler.toml:47
- authorization_granularity
12 tool registrations and no conditional access logic found — `03` §4 calls this case 'needs human review' and assigns it no score band, so it is not scored here
Dependency Health
Showing the 50 most severe of 96 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.jsontinypool 1.1.1 — GHSA-5gmw-xhrv-c9v3
transitive, CVSS 9.5, fixed in 2.1.1
https://osv.dev/vulnerability/GHSA-5gmw-xhrv-c9v3 - package-lock.jsontinypool 1.1.1 — GHSA-85c8-ppgw-ccpr
transitive, CVSS 9.5, fixed in 2.1.2
https://osv.dev/vulnerability/GHSA-85c8-ppgw-ccpr - 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.jsonwrangler 4.44.0 — GHSA-36p8-mvp6-cv38
direct, CVSS 7.7, fixed in 4.59.1
https://osv.dev/vulnerability/GHSA-36p8-mvp6-cv38 - package-lock.jsonsharp 0.33.5 — GHSA-rgj7-g3m4-5g8c
transitive, CVSS 8.9, fixed in 0.35.4
https://osv.dev/vulnerability/GHSA-rgj7-g3m4-5g8c - package-lock.jsonsharp 0.35.2 — GHSA-rgj7-g3m4-5g8c
transitive, CVSS 8.9, fixed in 0.35.4
https://osv.dev/vulnerability/GHSA-rgj7-g3m4-5g8c - package-lock.jsonsharp 0.33.5 — GHSA-wq5f-xc86-pv6w
transitive, CVSS 8.9, fixed in 0.35.5
https://osv.dev/vulnerability/GHSA-wq5f-xc86-pv6w - package-lock.jsonsharp 0.35.2 — GHSA-wq5f-xc86-pv6w
transitive, CVSS 8.9, fixed in 0.35.5
https://osv.dev/vulnerability/GHSA-wq5f-xc86-pv6w - 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 - package-lock.jsonaxios 1.16.0 — GHSA-gcfj-64vw-6mp9
transitive, CVSS 8.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-gcfj-64vw-6mp9 - package-lock.jsonaxios 1.16.0 — GHSA-x97p-jq2g-jp4f
transitive, CVSS 8.3, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-x97p-jq2g-jp4f - package-lock.jsonaxios 1.16.0 — GHSA-542g-h47m-68v8
transitive, CVSS 8.2, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-542g-h47m-68v8 - package-lock.jsonaxios 1.16.0 — GHSA-mghh-pgcx-3jjj
transitive, CVSS 8.2, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-mghh-pgcx-3jjj - package-lock.jsondevalue 5.9.0 — GHSA-mcm9-63f2-9j32
transitive, CVSS 8.2, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-mcm9-63f2-9j32 - package-lock.jsondevalue 5.9.0 — GHSA-r9w8-h9r3-54w4
transitive, CVSS 8.2, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-r9w8-h9r3-54w4 - package-lock.jsondevalue 5.9.0 — GHSA-x5rw-q4pp-hg5g
transitive, CVSS 8.2, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-x5rw-q4pp-hg5g - package-lock.jsonaxios 1.16.0 — GHSA-m8m8-qj5v-23w3
transitive, CVSS 7.6, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-m8m8-qj5v-23w3 - package-lock.json@modelcontextprotocol/client 2.0.0 — GHSA-6qxp-vccf-f47h
transitive, CVSS 7.5, fixed in 2.2.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.json@modelcontextprotocol/sdk 1.30.0 — GHSA-6qxp-vccf-f47h
transitive, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.jsondevalue 5.9.0 — GHSA-j22f-vq7h-c4qm
transitive, CVSS 7.5, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-j22f-vq7h-c4qm - 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 - 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 - 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 - 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 - 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 - package-lock.jsonundici 7.14.0 — GHSA-f269-vfmq-vjvj
transitive, CVSS 7.5, fixed in 7.24.0
https://osv.dev/vulnerability/GHSA-f269-vfmq-vjvj - package-lock.jsonundici 7.14.0 — GHSA-rfgv-xxqx-mfg5
transitive, CVSS 7.5, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-rfgv-xxqx-mfg5 - 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 - package-lock.jsonundici 7.14.0 — GHSA-v9p9-hfj2-hcw8
transitive, CVSS 7.5, fixed in 7.24.0
https://osv.dev/vulnerability/GHSA-v9p9-hfj2-hcw8 - package-lock.jsonundici 7.14.0 — GHSA-vrm6-8vpv-qv8q
transitive, CVSS 7.5, fixed in 7.24.0
https://osv.dev/vulnerability/GHSA-vrm6-8vpv-qv8q - package-lock.jsonundici 7.14.0 — GHSA-vxpw-j846-p89q
transitive, CVSS 7.5, fixed in 7.28.0
https://osv.dev/vulnerability/GHSA-vxpw-j846-p89q - package-lock.jsonuuid 8.3.2 — GHSA-w5hq-g745-h8pq
transitive, CVSS 7.5, fixed in 11.1.1
https://osv.dev/vulnerability/GHSA-w5hq-g745-h8pq - package-lock.jsonuuid 9.0.1 — GHSA-w5hq-g745-h8pq
transitive, CVSS 7.5, fixed in 11.1.1
https://osv.dev/vulnerability/GHSA-w5hq-g745-h8pq - package-lock.jsonws 8.18.0 — GHSA-96hv-2xvq-fx4p
transitive, CVSS 7.5, fixed in 8.21.0
https://osv.dev/vulnerability/GHSA-96hv-2xvq-fx4p - package-lock.jsonundici 7.14.0 — GHSA-4cwx-7wf7-3272
transitive, CVSS 7.4, fixed in 7.29.0
https://osv.dev/vulnerability/GHSA-4cwx-7wf7-3272 - 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 - package-lock.jsonaxios 1.16.0 — GHSA-3pq3-5fj3-cg6v
transitive, CVSS 7.0, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-3pq3-5fj3-cg6v - package-lock.jsonsharp 0.33.5 — GHSA-f88m-g3jw-g9cj
transitive, CVSS 7.0, fixed in 0.35.0
https://osv.dev/vulnerability/GHSA-f88m-g3jw-g9cj - package-lock.jsonhono 4.13.2 — GHSA-gqvv-2mrq-wpjv
direct, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv - package-lock.jsonhono 4.13.2 — GHSA-crvj-82cr-hjcx
direct, CVSS 5.9, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-crvj-82cr-hjcx - package-lock.jsonvitest 3.2.7 — GHSA-82fw-gwwq-j7x9
direct, CVSS 5.9, fixed in 4.1.11
https://osv.dev/vulnerability/GHSA-82fw-gwwq-j7x9 - package-lock.jsonhono 4.13.2 — GHSA-g6gw-c38x-mqfc
direct, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc - package-lock.jsonhono 4.13.2 — GHSA-hxh3-vqpv-xpqv
direct, CVSS 4.7, fixed in 4.13.7
https://osv.dev/vulnerability/GHSA-hxh3-vqpv-xpqv - package-lock.jsonaxios 1.16.0 — GHSA-44g4-m2mj-wpvx
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-44g4-m2mj-wpvx - package-lock.jsonaxios 1.16.0 — GHSA-4hqw-qxg8-jxx2
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-4hqw-qxg8-jxx2 - package-lock.jsonaxios 1.16.0 — GHSA-9fr6-4gfg-395g
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-9fr6-4gfg-395g - package-lock.jsonaxios 1.16.0 — GHSA-f4gw-2p7v-4548
transitive, CVSS 6.9, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-f4gw-2p7v-4548 - package-lock.jsonaxios 1.16.0 — GHSA-hcpx-6fm6-wx23
transitive, CVSS 6.9, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-hcpx-6fm6-wx23 - package-lock.jsonaxios 1.16.0 — GHSA-j8rh-479h-cp32
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-j8rh-479h-cp32 - package-lock.jsonaxios 1.16.0 — GHSA-vh66-26gq-q6x8
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-vh66-26gq-q6x8
Maintenance
- recency
last commit 48 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
this repository publishes neither releases nor version tags
- 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: configuration documented (+25)
- 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
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.