# Fix list: Vendure From Anchor Terminal's listing at https://www.anchorterminal.com/tools/vendure, the October 2026 research run, assessed 1 October 2026. Grade BB, 71.4 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on Vendure: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Payments & pricing, 45 out of 100, up to 6.9 more on the total Why it scored 45: No x402, MPP or L402 (0). Core is free, but Platform is quoted per project and Cloud has no public price (5). Core is free under GPLv3 with no card (20). An agent can scaffold a store with `npx @vendure/create` or query the public read-only demo Shop API without an account (20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 2. Security & auth, 65 out of 100, up to 6.1 more on the total Why it scored 65: API keys since 3.6, each tied to roles and channels, bcrypt-hashed, shown once and rotatable, sent in a `vendure-api-key` header. No OAuth in the released core (28). Roles and permissions per channel, and the harden plugin caps query complexity, but no confirmation step for destructive mutations (14). Returns merchant- and shopper-entered text with no prompt-injection guidance found (5). Order and customer history entries exist, but no audit log of API calls in the released versions (5). SECURITY.md takes private reports through GitHub, supports only the latest 3.x minor, and 3.7.3 published 11 Vendure advisories at once. No security.txt, bounty or certification found (13). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 3. Agent ergonomics, 68 out of 100, up to 5.2 more on the total Why it scored 68: GraphQL field selection sizes every response, and no MCP tools are shipped yet to weigh (23). List queries take `take`, `skip`, `filter` and `sort` (20). ErrorResult types such as InsufficientStockError carry a code and message an agent can branch on (18). No idempotency keys or retry guidance found, and repeating addItemToOrder adds the quantity again (0). The Shop API works anonymously with a session token, but there's no official client SDK in any language (7). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 4. Transparency & trust, 72 out of 100, up to 2.5 more on the total Made of editorial 78, provenance 65. Why it scored 72: GPL-3.0-or-later, with a commercial licence sold through Platform (30). Privacy policy dated 31 July 2026 names Elevantiq GmbH, lists processors (Twenty, Loops, WorkOS, Google Workspace, Vercel, Northflank, Sentry, Dealfront) and keeps docs search and MCP records up to 90 days, but there's no DPA and no terms of service page (18). SECURITY.md says only the latest 3.x minor gets fixes, and deprecations appear in the changelog without dated end-of-life notices (10). No usage telemetry found in the core, CLI or create packages. The telemetry plugin is opt-in OpenTelemetry that reports to the operator's own collector (20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Domain age: vendure.io, no registry record we could read (0 of 15) - Status page: not found (0 of 10) - security.txt: not found (0 of 10) ## 5. Reliability, 89 out of 100, up to 2.2 more on the total Why it scored 89: Graded with the self-hosted package checklist, since there's no generally available hosted API (Vendure Cloud is in partial availability). @vendure/core on npm with Node 20, 22 and 24 stated as tested (20). Build and test workflow on master, latest run passing in about 18 minutes, 599 runs listed (25). 170 open issues, with recent bugs including a search index job crash on Postgres (13 September) and order totals saved from a stale surcharge snapshot (9 September) (17). Dated CHANGELOG per release, but 3.7.3 changed behaviour in a patch release to close security holes, documented in its own section (12). Version 3.x (15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 6. Schema & documentation, 91 out of 100, up to 1.5 more on the total Why it scored 91: Typed GraphQL Shop and Admin APIs with introspection, and schema-shop.json and schema-admin.json committed to the repo (25). llms.txt at docs.vendure.io per the 30 September check (10). Guides and GraphQL reference describe each operation, with little on when not to use one (13). Strict GraphQL input types with enums and required markers (14). Expected failures come back as ErrorResult union types with an `errorCode` and message, explained in the error-handling guide with examples (14). Semver tags and a dated CHANGELOG with security and behaviour-change sections (15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 7. Maintenance & community, 85 out of 100, up to 1.3 more on the total Why it scored 85: v3.7.3 tagged on 2 September 2026 (30). v3.7.1 on 14 July, v3.7.2 on 3 August and v3.7.3 on 2 September (20). 170 open issues, many filed by maintainers themselves, with bugs from early September already labelled (17). No official client SDK, and the MCP plugin is merged to the minor branch but not on npm (8). CI passing on master, with floating-dependency and dependency-impact checks (10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## Deductions Each comes off the total. A fixed and documented problem counts for less at the next check. - 3.7.3 on 2 September 2026 fixed an unauthenticated takeover of SSO customer accounts through registerCustomerAccount (GHSA-wr5h-x3x6-4h23), a cross-channel IDOR in order payment, refund and fulfilment operations (GHSA-7qvr-c5vf-xxfh), and session tokens returned in Admin API job data (GHSA-32jm-mf7r-7qw5). All are fixed and disclosed, but the changelog warns that tokens may remain in historical job records (https://github.com/vendurehq/vendure/blob/master/CHANGELOG.md). ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - When @vendure/mcp-plugin (42 tools, OAuth 2.1 and a tool-call log on the minor branch) will reach npm in 3.8 - `LICENSE.md` says Copyright Vendure GmbH, while the legal notice names Elevantiq GmbH (FN 506751 y). We didn't establish whether these are the same company - When Vendure Cloud becomes generally available and what it will cost ## Weaknesses - No vendor-hosted API. Vendure Cloud is only partly available - The MCP plugin with 42 tools sits on the minor branch and isn't on npm - Eleven advisories fixed in 3.7.3, including unauthenticated SSO account takeover and a cross-channel IDOR - No official client SDK and no idempotency support for order mutations - No terms of service page, status page or security.txt ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Keep the session token from the first Shop API response and send it on every call. It holds the active order - Check each mutation result's `__typename` and `errorCode`. Expected failures return 200 with an ErrorResult - Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again - For server-side work, enable `api-key` in authOptions.tokenMethod and give the key one role in one channel - Run 3.7.3 or later, and purge old job records, which may still hold session tokens ## What the review panel asked for - Ship @vendure/mcp-plugin - Idempotency on order mutations - purge old job records - confirmation on destructive mutations ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.