{
  "fixes": {
    "slug": "google-secret-manager",
    "name": "Google Cloud Secret Manager",
    "listing": "https://www.anchorterminal.com/tools/google-secret-manager",
    "markdown": "# Fix list: Google Cloud Secret Manager\n\nFrom Anchor Terminal's listing at https://www.anchorterminal.com/tools/google-secret-manager, the October 2026 research run, assessed 1 October 2026. Grade BB, 76.6 out of 100.\n\nThis 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.\n\nFor a coding agent working on Google Cloud Secret Manager: 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.\n\n## 1. Payments \u0026 pricing, 20 out of 100, up to 10 more on the total\n\nWhy it scored 20: No x402, MPP or L402 (0). Per-unit prices public, $0.000082192 an hour per active version (about $0.06 a month), $0.03 per 10,000 accesses and $0.05 per rotation notification (20). Always free each month for 6 active versions, 10,000 accesses and 3 rotation notifications, plus $300 trial credit, but a billing account takes a card per the listing's 30 September check (0). A person creates the Google Cloud account and billing account (0).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):\n\nThe published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).\n\n- 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.\n- 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.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).\n\nPayment 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.\n\nOpen-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.\n\n## 2. Agent ergonomics, 82 out of 100, up to 2.9 more on the total\n\nWhy it scored 82: accessSecretVersion returns one payload with a CRC32C checksum, and list calls return metadata only (20 of 25). pageSize, pageToken and a filter expression on secrets and versions (20). Errors use google.rpc status codes with a message, and the per-method reference lists the IAM permission each call needs (15 of 20). Versions are immutable and updates take an etag, but AddSecretVersion has no request ID, so a retried write can add a second version (12 of 20). Client libraries in every Google-supported language, application default credentials, and a latest alias so a read needs only the secret name (15). There's no Secret Manager MCP server; the general gcloud MCP server can run gcloud secrets commands behind allow and deny lists.\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):\n\n- 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).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.\n\nModels 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.\n\n## 3. Schema \u0026 documentation, 83 out of 100, up to 2.8 more on the total\n\nWhy it scored 83: A REST discovery document and the protobuf definitions in googleapis, with field behaviours marking required members (25). No llms.txt at docs.cloud.google.com or under /secret-manager/docs (both 404) (0). The reference describes each method, and the guides say to pin a version rather than rely on latest in production (16 of 20). Proto types, enums for version state and replication, required fields, and no free-form blobs besides the payload (15). Code samples in several languages on each how-to page and the standard google.rpc error model (12 of 15). v1 is stable and the release notes are dated, the newest on 14 September 2026 (15).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):\n\nAPIs and MCP servers.\n\n- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 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.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.\n\nModels 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.\n\n## 4. Reliability, 87 out of 100, up to 2.6 more on the total\n\nWhy it scored 87: Google Cloud status dashboard with incident history (20). The incidents.json we read had nothing tagged Secret Manager; the three incidents since 1 July 2026 were a europe-west4 cooling failure (15 July), a us-west1 outage (20 August) and us-central1 network degradation (1 September), none listing Secret Manager, so we count it clean with a doubt about regional secrets (25 of 30). Quotas published, 90,000 access requests a minute per project, 600 management reads and 600 writes, 2 version writes a second on a global secret and 80 on a regional one (15). The quotas page gives no 429 or backoff guidance and says some limits are soft-enforced; updates carry etags for safe concurrent writes (7 of 15). SLA with a 99.95% monthly uptime objective and 10, 25 and 50 per cent credits, last modified 24 May 2021 (10). Generally available; regional Cloud SQL rotation is the preview part (10).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):\n\nHosted APIs, MCP servers, models and platforms.\n\n- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 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.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.\n\nLocal packages, SDKs, frameworks and stdio MCP servers.\n\n- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.\n\nProtocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.\n\n## 5. Security \u0026 auth, 85 out of 100, up to 2.6 more on the total\n\nWhy it scored 85: OAuth 2.0 bearer tokens from service accounts or workload identity on GKE, Cloud Run and GCE, with API keys refused (30). roles/secretmanager.secretAccessor on one secret, IAM conditions for expiry or a version, and version_destroy_ttl to delay destruction; nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). AccessSecretVersion is a Data Access audit log, which the audit logging page sends you to enable separately; Admin Activity logs cover management calls (12 of 15). security.txt valid to 2030-04-01 per the 30 September check; we didn't re-read certifications or the reward programme this run (15 of 20).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-security):\n\n- 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.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 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.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.\n\nModels 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.\n\n## 6. Transparency \u0026 trust, 85 out of 100, up to 1.3 more on the total\n\nMade of editorial 69, provenance 100.\n\nWhy it scored 85: Closed service under the Google Cloud terms, clear terms (15 of 30). Privacy policy, the Cloud Data Processing Addendum, regional secrets that keep data in one location, CMEK, and a subprocessor list modified 20 August 2026 that agree with each other; retention of access metadata isn't stated on the pages we read (24 of 30). No dated deprecation notices for Secret Manager in the release notes since May 2026, and we didn't read a deprecation policy (10 of 20). Subprocessors listed with locations, about 50 third parties (20).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):\n\n- 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.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).\n\nThe other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.\n\n## 7. Maintenance \u0026 community, 87 out of 100, up to 1.1 more on the total\n\nWhy it scored 87: Newest release note on 14 September 2026, a Parameter Manager change; the newest Secret Manager feature was regional Cloud SQL rotation in preview on 27 July (30). Five dated entries between 12 July and 14 September 2026 (20). Dated public release notes and Google Cloud support, which we didn't test (12 of 15). Client libraries current, Python 2.30.0 on 16 July 2026 with 2.31.0 tagged on 2 October (15). Generated libraries released from the googleapis monorepo with CI (10).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):\n\n- 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.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 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.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.\n\nModels are read for deprecation notice periods and model churn rather than release counts.\n\n## What we couldn't check\n\nWhat 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.\n\n- The listing said every access lands in Cloud Audit Logs; reads are Data Access logs that must be enabled, corrected in summary and notable.\n- The listing's free tier missed the 10,000 free accesses and 3 free rotation notifications a month, corrected in pricingNotes.\n- unchecked: whether a Google Cloud billing account still needs a card, relied on from the 30 September check's card-required tag.\n- Whether the incidents.json we read was complete; the summary we got listed only three incidents since 1 July 2026.\n\n## Weaknesses\n\n- Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle\n- Secret reads are Data Access audit logs, which you have to enable\n- Global secrets accept only 2 version writes a second, and AddSecretVersion has no request ID for safe retries\n- No llms.txt and no Secret Manager MCP server\n- Off Google Cloud you need a service account key or workload identity federation, and a billing account with a card\n\n## What costs an agent a turn today\n\nThe notes we give agents before they call it. Each one is a workaround an agent shouldn't need.\n\n- Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version\n- Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent\n- Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read\n- Read once per run and cache; accesses past 10,000 a month are metered\n- Use a regional secret (projects/*/locations/*/secrets/*) when the data must stay in one place, and note the higher write quota there\n\n## What the review panel asked for\n\n- onboarding without a card\n- Request IDs on version writes\n- A Secret Manager MCP server\n- State audit log cost\n- Add llms.txt\n- Backoff guidance on the quotas page\n- llms.txt\n- backoff guidance\n- Request ID on writes\n- Publish backoff guidance\n- a stated deprecation policy\n- read logging on by default\n\n## When it's done\n\nSend 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.\n",
    "grade": "BB",
    "score": 76.6,
    "assessed": "2026-10-01",
    "run": "October 2026 research run",
    "categories": [
      {
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "score": 20,
        "maxGain": 10,
        "reason": "No x402, MPP or L402 (0). Per-unit prices public, $0.000082192 an hour per active version (about $0.06 a month), $0.03 per 10,000 accesses and $0.05 per rotation notification (20). Always free each month for 6 active versions, 10,000 accesses and 3 rotation notifications, plus $300 trial credit, but a billing account takes a card per the listing's 30 September check (0). A person creates the Google Cloud account and billing account (0).",
        "checklist": [
          "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.\n- 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.\n- 20, a free tier or trial that doesn't need a card.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-payments"
      },
      {
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "score": 82,
        "maxGain": 2.9,
        "reason": "accessSecretVersion returns one payload with a CRC32C checksum, and list calls return metadata only (20 of 25). pageSize, pageToken and a filter expression on secrets and versions (20). Errors use google.rpc status codes with a message, and the per-method reference lists the IAM permission each call needs (15 of 20). Versions are immutable and updates take an etag, but AddSecretVersion has no request ID, so a retried write can add a second version (12 of 20). Client libraries in every Google-supported language, application default credentials, and a latest alias so a read needs only the secret name (15). There's no Secret Manager MCP server; the general gcloud MCP server can run gcloud secrets commands behind allow and deny lists.",
        "checklist": [
          "- 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).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-ergonomics"
      },
      {
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "score": 83,
        "maxGain": 2.8,
        "reason": "A REST discovery document and the protobuf definitions in googleapis, with field behaviours marking required members (25). No llms.txt at docs.cloud.google.com or under /secret-manager/docs (both 404) (0). The reference describes each method, and the guides say to pin a version rather than rely on latest in production (16 of 20). Proto types, enums for version state and replication, required fields, and no free-form blobs besides the payload (15). Code samples in several languages on each how-to page and the standard google.rpc error model (12 of 15). v1 is stable and the release notes are dated, the newest on 14 September 2026 (15).",
        "checklist": [
          "APIs and MCP servers.",
          "- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 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.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-schema"
      },
      {
        "key": "reliability",
        "name": "Reliability",
        "score": 87,
        "maxGain": 2.6,
        "reason": "Google Cloud status dashboard with incident history (20). The incidents.json we read had nothing tagged Secret Manager; the three incidents since 1 July 2026 were a europe-west4 cooling failure (15 July), a us-west1 outage (20 August) and us-central1 network degradation (1 September), none listing Secret Manager, so we count it clean with a doubt about regional secrets (25 of 30). Quotas published, 90,000 access requests a minute per project, 600 management reads and 600 writes, 2 version writes a second on a global secret and 80 on a regional one (15). The quotas page gives no 429 or backoff guidance and says some limits are soft-enforced; updates carry etags for safe concurrent writes (7 of 15). SLA with a 99.95% monthly uptime objective and 10, 25 and 50 per cent credits, last modified 24 May 2021 (10). Generally available; regional Cloud SQL rotation is the preview part (10).",
        "checklist": [
          "Hosted APIs, MCP servers, models and platforms.",
          "- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 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.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 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.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-reliability"
      },
      {
        "key": "security",
        "name": "Security \u0026 auth",
        "score": 85,
        "maxGain": 2.6,
        "reason": "OAuth 2.0 bearer tokens from service accounts or workload identity on GKE, Cloud Run and GCE, with API keys refused (30). roles/secretmanager.secretAccessor on one secret, IAM conditions for expiry or a version, and version_destroy_ttl to delay destruction; nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). AccessSecretVersion is a Data Access audit log, which the audit logging page sends you to enable separately; Admin Activity logs cover management calls (12 of 15). security.txt valid to 2030-04-01 per the 30 September check; we didn't re-read certifications or the reward programme this run (15 of 20).",
        "checklist": [
          "- 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.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 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.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-security"
      },
      {
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "score": 85,
        "maxGain": 1.3,
        "reason": "Closed service under the Google Cloud terms, clear terms (15 of 30). Privacy policy, the Cloud Data Processing Addendum, regional secrets that keep data in one location, CMEK, and a subprocessor list modified 20 August 2026 that agree with each other; retention of access metadata isn't stated on the pages we read (24 of 30). No dated deprecation notices for Secret Manager in the release notes since May 2026, and we didn't read a deprecation policy (10 of 20). Subprocessors listed with locations, about 50 third parties (20).",
        "blend": "editorial 69, provenance 100",
        "checklist": [
          "- 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.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-transparency"
      },
      {
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "score": 87,
        "maxGain": 1.1,
        "reason": "Newest release note on 14 September 2026, a Parameter Manager change; the newest Secret Manager feature was regional Cloud SQL rotation in preview on 27 July (30). Five dated entries between 12 July and 14 September 2026 (20). Dated public release notes and Google Cloud support, which we didn't test (12 of 15). Client libraries current, Python 2.30.0 on 16 July 2026 with 2.31.0 tagged on 2 October (15). Generated libraries released from the googleapis monorepo with CI (10).",
        "checklist": [
          "- 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.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 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.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.",
          "Models are read for deprecation notice periods and model churn rather than release counts."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-maintenance"
      }
    ],
    "unchecked": [
      "The listing said every access lands in Cloud Audit Logs; reads are Data Access logs that must be enabled, corrected in summary and notable.",
      "The listing's free tier missed the 10,000 free accesses and 3 free rotation notifications a month, corrected in pricingNotes.",
      "unchecked: whether a Google Cloud billing account still needs a card, relied on from the 30 September check's card-required tag.",
      "Whether the incidents.json we read was complete; the summary we got listed only three incidents since 1 July 2026."
    ],
    "weaknesses": [
      "Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle",
      "Secret reads are Data Access audit logs, which you have to enable",
      "Global secrets accept only 2 version writes a second, and AddSecretVersion has no request ID for safe retries",
      "No llms.txt and no Secret Manager MCP server",
      "Off Google Cloud you need a service account key or workload identity federation, and a billing account with a card"
    ],
    "agentNotes": [
      "Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version",
      "Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent",
      "Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read",
      "Read once per run and cache; accesses past 10,000 a month are metered",
      "Use a regional secret (projects/*/locations/*/secrets/*) when the data must stay in one place, and note the higher write quota there"
    ],
    "requests": [
      {
        "text": "onboarding without a card",
        "reviews": 1
      },
      {
        "text": "Request IDs on version writes",
        "reviews": 1
      },
      {
        "text": "A Secret Manager MCP server",
        "reviews": 1
      },
      {
        "text": "State audit log cost",
        "reviews": 1
      },
      {
        "text": "Add llms.txt",
        "reviews": 1
      },
      {
        "text": "Backoff guidance on the quotas page",
        "reviews": 1
      },
      {
        "text": "llms.txt",
        "reviews": 1
      },
      {
        "text": "backoff guidance",
        "reviews": 1
      },
      {
        "text": "Request ID on writes",
        "reviews": 1
      },
      {
        "text": "Publish backoff guidance",
        "reviews": 1
      },
      {
        "text": "a stated deprecation policy",
        "reviews": 1
      },
      {
        "text": "read logging on by default",
        "reviews": 1
      }
    ],
    "recheck": "https://www.anchorterminal.com/builders/#disputes"
  },
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-04",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.3",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  }
}