Google Authenticator vs Bitwarden

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden serves a live llms.txt at bitwarden.com/llms.txt (HTTP 200) with structured content, and help pages ship real per-page markdown mirrors (e.g., cli.md) confirming genuine agent-oriented documentation rather than a stub. This is directly confirmed by runtime probes, not just claims. Missing for 10: no independent third-party corroboration of an agent actually consuming these docs end-to-end in a workflow.

   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bitwarden.com serves a live llms.txt ('# Bitwarden — The most trusted open source password manager...')…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden ships an official CLI with API-key authentication explicitly documented as suitable for automated workflows/CI, plus a Public API for org automation and a headless 'bw serve' mode confirmed at runtime. missing for 10: no CI-specific tutorial/example pipeline (e.g., GitHub Actions) in evidence, and one community report notes CLI 'bw list' unexpectedly dumping plaintext secrets, a minor safety caveat for automation use.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden ships a first-party, GPL-3.0 MCP server (bitwarden/mcp-server) published to npm, and a runtime probe confirms it completes a full stdio handshake, showing it works as documented rather than just being an announcement. Missing for 10: independent third-party review of the MCP server's tool set/security beyond the vendor probe.

   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden ships a documented, fully-featured official CLI (bw) with vault management, API key auth for automated workflows, and a runtime-verified 'bw serve' mode exposing a local REST API well-suited to agentic/AI use. missing for 10: independent third-party benchmarking of agent integration quality beyond one community anecdote about plaintext output behavior.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “official CLI documented at https://bitwarden.com/help/cli/”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden documents a Public API for organization management (bitwarden-docs-8), a personal API key for automated/programmatic access (bitwarden-docs-9), and a full-featured CLI (bitwarden-docs-7, bitwarden-probe-4) with a documented `bw serve` REST mode enabling agent-driven vault access (bitwarden-probe-rt-1); this constitutes a documented public API surface an AI-native user could drive. missing for 10: a public OpenAPI/swagger spec resolves 404 on probed endpoints (bitwarden-probe-2), and one community report flags a CLI safety/UX issue (bitwarden-comm-13) showing rough edges in automation ergonomics.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialprobed4/10

   Bitwarden documents a personal API key for CLI/automated workflows and a Public API/CLI (including `bw serve` and an official MCP server) that an agent could use, but there's no evidence of fine-grained, least-privilege scoping (e.g., read-only, per-item, or per-collection API keys) — the personal API key and CLI access appear to grant broad vault access rather than scoped permissions, and a hands-on report shows `bw list` dumping full plaintext secrets rather than a restricted subset. missing for 10: documented scoped/restricted API key types, per-agent permission grants, or evidence that MCP/CLI access can be limited to specific vault items rather than the whole vault.

   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialprobed4/10

   Evidence shows Bitwarden exposes a Public API, CLI, personal API keys for automation, and an official MCP server (all of which an AI-native builder could integrate against), but there is no evidence of a dedicated, language-specific 'official SDK' (e.g., a bitwarden/sdk repo) and the OpenAPI/swagger spec probes all returned 404, suggesting no machine-readable API contract is published. missing for 10: explicit official SDK repositories/language bindings, published OpenAPI spec, independent developer corroboration of SDK usage.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”
   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   Bitwarden offers CLI/API/MCP server access that agents could use, but there is no evidence of a mechanism for setting up autonomous, scheduled, or background-running automations (e.g., triggers, workflows, cron-like jobs) — it only provides interfaces for on-demand vault access. missing for 10: any documented scheduling/trigger/workflow automation feature, evidence of background/autonomous execution, or vendor claims of persistent automation setup.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

2. ai-native userOperate the product with natural-language commands

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden ships an official MCP server (bitwarden/mcp-server) that completed a live stdio handshake, letting AI agents/assistants issue natural-language commands to manage the vault, backed by a full-featured CLI and llms.txt for AI-friendly docs. Missing for 10: no independent hands-on demonstration of a natural-language command actually retrieving/creating vault items via the MCP server, and community feedback flags CLI output risks (e.g., plaintext dumps) that complicate safe agentic use.

   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

Api quality

1. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   Bitwarden documents a Public API and CLI/personal API key access, but there is no evidence of API versioning scheme or a documented deprecation policy; probes for an OpenAPI spec (bitwarden-probe-2) all returned 404s, and no docs mention version headers, breaking-change policy, or sunset timelines.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialcommunity6/10

   The CLI (bw list/create/edit/delete) and Public API expose scriptable, item-level access that can be chained for bulk operations, and import/export functions handle whole-vault bulk transfers of many items at once; community evidence (bw list dumping the entire vault) confirms bulk read actually works. However, there is no first-party documentation of a dedicated bulk-edit/bulk-tag/bulk-delete command or batch endpoint — bulk operations require the user to script them themselves rather than a built-in bulk API. Missing for 10: documented native bulk-update/bulk-delete commands, batch API endpoints for many items, and independent hands-on confirmation of large-scale automated edits succeeding.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialprobed6/10

   Bitwarden ships a fully-featured CLI and a Vault Management API (`bw serve`) covering item/vault CRUD, TOTP retrieval, and org management via a Public API and personal API key for automated workflows, giving strong but not fully documented parity with the UI. There's no explicit vendor claim or evidence that every UI feature (e.g., passkey autofill, browser-context auto-fill, vault health reports) is exposed via API/CLI, and a hands-on report shows the CLI's `bw list` behaves differently than expected (dumping all secrets) rather than mirroring UI workflows cleanly. missing for 10: explicit API/CLI equivalents for passkey autofill and browser-based auto-fill, API access to vault health reports, and a documented feature-parity statement.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Bitwarden
   Google Authenticator!disputedcontradicted3/10

   Docs show a QR-code based transfer/export feature for moving codes between devices (docs-3, docs-11, comm-9, comm-18), but this is a proprietary re-import-only format tied to Google Authenticator itself, not an open, portable format usable elsewhere. Community evidence explicitly contradicts any 'open format export' claim: users report Google 'makes it stupendously difficult to just get a simple text export to a file' and that 'Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted,' with data tied to a Google Account that can vanish if banned. Missing for 10: any documented open/standard export format (e.g., plain TOTP URI list, CSV, encrypted portable file), and evidence of true account-independent data portability.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted. So due to Google Authenticator, losi…”
   • [community] “Google Authenticator already has a QR-Code based very easy export procedure, I just backup my GAuth to my spare phone and tablet. It feels s…”
   • [community] “Google Authenticator has a feature to allow export of all saved codes into one QR code for re-import into Google Authenticator running on an…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   Bitwarden✓fullclaimed9/10

   Bitwarden's docs explicitly support exporting full vault data (logins, notes) for backup or transfer, plus separate authenticator/TOTP export in open formats (JSON), and CLI/API access for automated bulk export. This directly satisfies the 'export all data in open formats and leave' story with strong first-party documentation. Missing for 10: no independent/hands-on confirmation of export format fidelity or completeness verification by a third party.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Bitwarden
   Google Authenticator~partialclaimed4/10

   The official GitHub repo (google/google-authenticator) publicly hosts source for HOTP/TOTP implementations across platforms and a PAM module, suggesting some source is open, but the evidence never states an explicit open-source license nor confirms the current mobile app's source is included/maintained there. missing for 10: explicit license text (e.g., Apache 2.0) confirmation, evidence the current Android/iOS app source (not just legacy PAM/CLI code) is published, and any independent corroboration of license terms.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”
   • [github] “Pluggable Authentication Module, aka PAM.”

   proof ↗⚑ flag

   Bitwarden~partialprobed6/10

   Community evidence and the MCP server repo confirm Bitwarden ships components under open licenses (e.g., bitwarden/mcp-server is GPL-3.0) and is broadly known/marketed as 'the most trusted open source password manager,' and users cite valuing its open client source. However, the same evidence documents a real controversy where Bitwarden relicensed its SDK away from a fully open license, only reversing course after backlash — a concrete counter-example to unconditional openness. missing for 10: explicit license file/repo evidence for the core vault clients, resolution details confirming all components are now uniformly open-licensed, independent audit confirming no remaining non-open components.

   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “Props for them to step in the right direction, it wasn’t obvious at all for a few days what they would do (re: SDK relicensing controversy).”
   • [community] “Thank you to Bitwarden for relicensing back to Free/Open License... I no longer recommend Bitwarden for normal people because the built-in p…”
   • [community] “I’m relieved... I hope they realized that being FOSS is their moat... I’m still not sure how I feel about them now. Trust in the company has…”
   • [community] “I use BitWarden because I'd never trust a password manager with closed source clients... Needless to say I move to the next ethical e2ee pas…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Bitwarden
   Google Authenticator—none0/10

   Google Authenticator's core mobile app is closed-source and tied to Google account infrastructure for sync (docs-1, docs-4); the only open-source artifacts on GitHub are OTP-generator libraries and a PAM module, not the actual app users run, and there's no documented way to self-host the core product. Community threads reinforce this, complaining about lack of control over codes and dependency on Google's cloud (comm-6, comm-7, comm-12).

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “Pluggable Authentication Module, aka PAM.”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden provides official, well-documented on-premise/self-hosting instructions for Linux servers, and it is open-source, aligning strongly with an AI-native user's openness needs. missing for 10: independent hands-on verification of self-hosted deployment specifically (evidence is docs-only, not community confirmation of self-hosting success).

   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”

   proof ↗⚑ flag

Storage

1. everyday userThe app stores passkeys and signs me into websites and apps with them, not just TOTP codes

   weight 3 · round to Bitwarden
   Google Authenticator—none0/10

   All evidence describes Google Authenticator solely as a TOTP/HOTP code generator with cloud sync of codes; there is no mention of passkey storage or passkey-based sign-in anywhere in the docs, GitHub description, or community discussion.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”

   proof ↗⚑ flag

   Bitwarden✓fullclaimed8/10

   Bitwarden documents storing passkeys in the vault and using the browser extension or mobile apps to autofill/sign in with them across websites and apps, going beyond TOTP-only support (bitwarden-docs-4), which aligns directly with the story's requirement of passkey-based sign-in, not just TOTP codes. Missing for 10: independent/hands-on user reports specifically confirming passkey sign-in reliability (community evidence only discusses TOTP/autofill issues, not passkeys) and detail on cross-platform (desktop app) passkey support beyond browser/mobile.

   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”

   proof ↗⚑ flag

Sync

1. power userMy passkeys sync across ecosystems — iOS, Android, Windows, Linux, browsers — instead of being locked to one platform vendor

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialclaimed6/10

   Bitwarden explicitly stores passkeys in the vault and lets the browser extension and mobile apps autofill them across apps and sites, which is the platform-agnostic model (unlike Apple/Google's device-locked passkey sync) [bitwarden-docs-4]. However, the docs only call out browser extension and mobile apps, not desktop apps on Windows/Linux specifically, and there's no independent hands-on confirmation of passkey sync working seamlessly across all five named platforms. Missing for 10: explicit desktop (Windows/Linux) passkey autofill documentation, and independent/community verification of cross-platform passkey sync reliability.

   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”

   proof ↗⚑ flag

Export

1. power userExport all my TOTP secrets in an open, readable format and leave for another app whenever I choose — no lock-in

   weight 3 · round to Bitwarden
   Google Authenticator!disputedcontradicted3/10

   Docs and community posts confirm a QR-code 'export' exists, but it is a proprietary migration QR built for transferring to another Google Authenticator instance, not an open/readable text format, and users explicitly report Google 'makes it stupendously difficult to just get a simple text export to a file' and that codes cannot be included in backups. This directly contradicts the story's requirement of an open, readable, portable export for switching apps freely. Missing for 10: an official plain-text/otpauth-URI export, documented compatibility with third-party apps, and confirmation the QR format is standardized/open rather than proprietary.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “Google Authenticator already has a QR-Code based very easy export procedure, I just backup my GAuth to my spare phone and tablet. It feels s…”
   • [community] “Google Authenticator has a feature to allow export of all saved codes into one QR code for re-import into Google Authenticator running on an…”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted. So due to Google Authenticator, losi…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed4/10

   Bitwarden documents a general vault export (JSON/CSV) for 'logins and notes' and back-up/transfer purposes, but the evidence never explicitly confirms that TOTP secrets are included in that export or specifies an open, human-readable format for them — only import paths for other authenticators (Google Authenticator QR, LastPass JSON, 2FAS) are detailed, which is the opposite direction (lock-in mitigation on entry, not exit). Missing for 10: explicit confirmation that TOTP seeds are present in the standard export file, documentation of the exact readable TOTP export format, and any independent/hands-on verification that exported TOTP secrets can be reimported elsewhere.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

Import

1. power userImport tokens in bulk from other authenticator apps instead of re-enrolling every account by hand

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   Evidence only covers transferring/syncing Google Authenticator codes between devices running Google Authenticator itself (QR export/import, Google Account sync), not bulk import of tokens originating in other authenticator apps (e.g., Authy, Microsoft Authenticator). No documentation or community report describes cross-app bulk import.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “Google Authenticator has a feature to allow export of all saved codes into one QR code for re-import into Google Authenticator running on an…”

   proof ↗⚑ flag

   Bitwarden✓fullclaimed8/10

   Bitwarden's official docs explicitly support bulk import of TOTP/authenticator tokens from Google Authenticator (QR), LastPass Authenticator (JSON), and 2FAS (.2fas) backups, directly enabling power users to migrate accounts without re-enrolling each one by hand. This is a first-party, documented dedicated import flow, not a workaround. missing for 10: independent hands-on confirmation of the bulk import UX working smoothly, and coverage of additional popular authenticator export formats (e.g., Authy, Microsoft Authenticator).

   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

Migration

1. everyday userMoving to a new phone transfers all my tokens in one guided step

   weight 2 · round to Bitwarden
   Google Authenticator!disputedcontradicted4/10

   Google's own docs describe a guided one-step transfer via signing into a Google Account (auto-sync) or scanning a QR export code between old/new devices, which matches the story closely. However, multiple hands-on community reports concretely contradict this working reliably in practice—users report app upgrades wiping all tokens, phone replacements losing TOTP keys despite expecting sync/backup, and account bans erasing synced codes entirely. missing for 10: independent verification that the guided transfer works consistently without data loss, and resolution of documented upgrade/sync failures.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [community] “I recently had a broken phone replaced and had depended on a backup to have my TOTP keys on my new phone. It was not a part of the phone bac…”
   • [community] “Don't upgrade! I just had this unpleasant experience and warned everyone... Warning: Google Authenticator upgrade loses all accounts.”
   • [community] “Every time I upgraded to a new iOS 7 beta, it wiped my Google Authenticator account tokens... I can't log in to my CampBX account anymore.”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   Bitwarden~partialcommunity6/10

   Bitwarden's cloud vault syncs logins, passkeys, and TOTP codes across devices automatically (docs-1, docs-2, docs-4), so logging into a new phone with the same account would pull in tokens without manual export/import — effectively delivering the outcome. However, no evidence describes a dedicated 'guided' new-device setup wizard, and one community report (bitwarden-comm-9) describes lost generated data tied to connectivity issues, raising reliability caveats for a seamless one-step transfer. Missing for 10: documented guided device-migration flow/wizard, and independent hands-on confirmation that TOTP/passkeys transfer flawlessly to a new phone.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   No evidence pack item mentions data residency, region selection, or self-hosting for regional compliance beyond a generic on-premise Linux install guide, which does not address choosing a storage region. Missing for 10: any documentation of region/data-residency selection (e.g., EU vs US data centers), enterprise residency options, or explicit control over where vault data is stored.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   The evidence pack contains no documentation, policy statement, or setting from Bitwarden addressing whether vault data or user data is used to train AI models, nor any opt-out mechanism for such use. This is a fair privacy-posture question for a SaaS handling sensitive personal data, but nothing in the pack confirms or denies a stance, so it cannot be credited as delivered.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Google Authenticator
   Google Authenticator~partialcommunity4/10

   Google Authenticator lets users delete individual codes (swipe to delete), edit/reassign codes, and use the app without a Google account (avoiding cloud retention entirely), giving some control over what data is stored and removed. However, there is no documented account-level 'delete all my data' or data-export-to-file control, and community reports describe difficulty exporting/backing up codes and total data loss if a Google account is banned or deleted, undermining full user control over retention. missing for 10: explicit data export/portability controls, account-wide deletion/retention settings, and confirmation that deleting codes removes them from Google's backend, not just the local view.

   • [claimed-docs] “To delete an Authenticator code on Android, swipe right on any code to show the delete option.”
   • [claimed-docs] “When you first open the app, tap Use without an account.”
   • [claimed-docs] “For additional protection, you can turn on Privacy Screen in Google Authenticator. This requires a verification from your device, like a PIN…”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted. So due to Google Authenticator, losi…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   Bitwarden~partialcommunity3/10

   Bitwarden docs show users can export their vault data (for backup or account transfer) and community evidence indicates an account-deletion path exists (export → delete account → recreate), but there is no dedicated, first-party documentation on data retention policies, granular deletion controls, or how these apply to AI/agent access (e.g., MCP server or CLI-served vault data). Missing for 10: explicit retention policy documentation, dedicated account/vault deletion docs, and clarity on data lifecycle when accessed via CLI/MCP for AI agents.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [community] “BitWarden has lost the trust. There was a blocker bug on iOS, they went radio silent on follow-ups, and their fix suggestion was 'export dat…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   The evidence pack contains no documentation, settings, or community reports describing a telemetry/usage-tracking opt-out control in Bitwarden clients, CLI, or self-hosted server. While the axis is fair to ask of any privacy-focused product, nothing here confirms such a toggle exists or how it works.

   ⚑ flag

App lock

1. everyday userThe app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes

   weight 2 · round to Google Authenticator
   Google Authenticator✓fullclaimed8/10

   Google's own docs describe a 'Privacy Screen' feature requiring PIN, pattern, or biometric verification before the app can be used, directly matching the story. No community evidence contradicts this specific lock-screen feature (complaints focus on sync/backup, not app-lock). Missing for 10: independent hands-on confirmation of the Privacy Screen feature working reliably across devices.

   • [claimed-docs] “For additional protection, you can turn on Privacy Screen in Google Authenticator. This requires a verification from your device, like a PIN…”

   proof ↗⚑ flag

   Bitwarden~partialcommunity3/10

   No official documentation in the evidence pack describes a PIN/biometric app-lock feature; the only signal is an indirect community comment implying fingerprint unlock already exists on some platforms but is missing on Linux, which weakly corroborates the capability without detailing scope or coverage. Missing for 10: first-party docs on biometric/PIN unlock, mobile-specific confirmation, and independent hands-on validation of the lock behavior.

   • [community] “Yeah it's nice and all but I wish they brought fingerprint auth to Linux already.”

   proof ↗⚑ flag

Audits

1. security engineerThe vendor publishes independent security audits of the app and its sync protocol

   weight 2 · round drawn
   Google Authenticator—none0/10

   No evidence of any independent security audit of the app or its cloud sync protocol; a notable 2023 independent security researcher analysis found the sync data was unencrypted, but no formal published audit exists in the evidence pack, only community complaints about sync/backup reliability and trust concerns.

   ⚑ flag

   Bitwarden—none0/10

   No evidence pack items reference independent third-party security audits, penetration tests, or cryptographic/protocol reviews of Bitwarden's app or sync protocol; the pack only covers docs on features (TOTP, autofill, CLI, import/export) and community sentiment/complaints unrelated to audits. Missing for 10: published audit reports (e.g., Cure53), audit scope/dates, sync protocol review findings, remediation disclosures.

   ⚑ flag

Monitoring

1. power userThe app warns me when a service I use is breached or a stored credential is weak, reused, or exposed

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialclaimed5/10

   Bitwarden's Vault Health Reports (docs-11/17) explicitly check for reused and weak passwords locally on the client, covering part of the story, but no evidence in the pack documents breach monitoring (e.g., known data-breach alerts) or an 'exposed passwords' check against breach databases. Missing for 10: evidence of breach/exposure alerts for compromised services, and any exposed-credential detection feature.

   • [claimed-docs] “Vault health reports can help you evaluate the security of your Bitwarden individual or organization vault... Reports... are run locally on …”
   • [claimed-docs] “Vault health reports can help you evaluate the security of your Bitwarden individual or organization vault. Reports, such as the Reused Pass…”

   proof ↗⚑ flag

Push

1. it adminPush-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies

   weight 2 · round drawn
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Server

1. it adminSelf-host the sync server on my own infrastructure and keep every secret inside my perimeter

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullclaimed8/10

   Bitwarden provides official documentation for installing and deploying the self-hosted server on a Linux server, keeping vault data on the admin's own infrastructure — the core of this story. Missing for 10: independent hands-on verification of a real-world self-hosted deployment and details on ongoing maintenance/upgrade complexity for self-hosted instances.

   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”

   proof ↗⚑ flag

Source

1. security engineerThe client apps are open source, so the code handling my seeds can be inspected and community-reviewed

   weight 2 · round to Bitwarden
   Google Authenticator~partialclaimed4/10

   The GitHub repo (google/google-authenticator) documents open-source implementations of HOTP/TOTP and a PAM module, giving some basis for code review, but the evidence pack has no confirmation that the current shipped Android/iOS apps (which now handle cloud sync of seeds) actually correspond to this repo or receive active community review. missing for 10: evidence that the live mobile app source matches the published repo, evidence of active maintenance/community audits of the seed-handling code, and independent confirmation of code correctness.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”
   • [github] “Pluggable Authentication Module, aka PAM.”

   proof ↗⚑ flag

   Bitwarden~partialprobed6/10

   Bitwarden markets itself as 'the most trusted open source password manager' and community members explicitly cite open-source clients as the reason they trust it with secrets (bitwarden-probe-1, bitwarden-comm-15). However, the evidence also documents a real controversy where SDK code (used by clients) was briefly relicensed away from a fully open license before being reverted after community pressure, which shows scrutiny worked but also that openness has not always been airtight (bitwarden-comm-1, bitwarden-comm-3, bitwarden-comm-4). Missing for 10: direct links to client-app GitHub repos, explicit confirmation that seed/TOTP-handling code specifically is open and audited, and independent third-party code audits corroborating the open-source claim.

   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [community] “I use BitWarden because I'd never trust a password manager with closed source clients... Needless to say I move to the next ethical e2ee pas…”
   • [community] “Props for them to step in the right direction, it wasn’t obvious at all for a few days what they would do (re: SDK relicensing controversy).”
   • [community] “Thank you to Bitwarden for relicensing back to Free/Open License... I no longer recommend Bitwarden for normal people because the built-in p…”
   • [community] “I’m relieved... I hope they realized that being FOSS is their moat... I’m still not sure how I feel about them now. Trust in the company has…”

   proof ↗⚑ flag

Automation

1. ai-native userAn agent can fetch a current TOTP code programmatically — via CLI or API — to complete a 2FA login inside an automated workflow

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   Google Authenticator is a mobile/PAM app with no documented CLI or API for programmatic TOTP retrieval; evidence only covers manual app UI actions (sync, QR export, editing codes) and community complaints about backup/sync issues, none of which show agent-accessible code fetching.

   ⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden's integrated authenticator generates TOTP codes (bitwarden-docs-1) and the CLI is documented as a full vault-management tool suitable for automated workflows via personal API key (bitwarden-docs-7, bitwarden-docs-9); runtime probes confirm 'bw serve' exposes a local REST Vault Management API and an official MCP server completes a full handshake, both surfaces an agent could use to fetch TOTP codes programmatically (bitwarden-probe-rt-1, bitwarden-probe-rt-2). Hands-on community evidence independently corroborates that 'bw list' actually returns current TOTP codes in plaintext, confirming the CLI does return live TOTP data (bitwarden-comm-13). Missing for 10: explicit documentation naming a dedicated 'get totp' command/API endpoint and a clean (non-complaint) hands-on workflow example.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

2. ai-native userExpose the vault through a local programmatic endpoint an agent can query for codes and secrets without screen-scraping the app

   weight 1 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden's CLI supports a documented `bw serve` mode exposing the vault as a local RESTful API, and Bitwarden ships an official MCP server (bitwarden/mcp-server) that completed a live stdio handshake, both giving agents programmatic access to vault items and TOTP codes without screen-scraping. missing for 10: no independent hands-on validation of `bw serve` specifically for TOTP retrieval by an agent, and no broader third-party corroboration beyond the vendor-run probes.

   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”

   proof ↗⚑ flag

Browser

1. everyday userA browser extension autofills my TOTP codes and passkeys during login instead of making me retype them

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullcommunity8/10

   Docs confirm browser extension autofills matching credentials on login pages (docs-12), autofills stored passkeys across apps/websites (docs-4), and generates/syncs TOTP codes (docs-1, docs-2) which are surfaced during autofill in the extension. One community mention notes TOTP setup friction, but no concrete evidence contradicts the core autofill-of-TOTP/passkeys capability. Missing for 10: independent hands-on confirmation specifically that TOTP codes (not just passwords/passkeys) are auto-filled into login forms without manual copy-paste.

   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”

   proof ↗⚑ flag

Desktop

1. power userA first-class desktop app gives me codes and vault access on my computer, not just on mobile

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   No evidence of a desktop application; Google Authenticator is documented and discussed only as a mobile app with QR-based transfer/sync between phones, not a desktop client or vault.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”

   proof ↗⚑ flag

   Bitwarden~partialprobed5/10

   Evidence confirms TOTP codes sync across 'Bitwarden apps' and vault access is available via browser extension and CLI on a computer, implying desktop-class access, but no citation explicitly documents a native desktop application (GUI) separate from the browser extension/CLI. Missing for 10: explicit desktop app documentation, screenshots/feature parity claims, and independent confirmation that a first-class desktop GUI (not just extension/CLI) exists and works well.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”

   proof ↗⚑ flag

Watch

1. everyday userRead my codes from my smartwatch without pulling out my phone

   weight 1 · round drawn
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   The evidence pack covers TOTP generation, syncing, browser extension, CLI, and API features, but contains no mention of a smartwatch app, Wear OS/watchOS companion, or any glanceable code display for wearables. This is a fair capability question for a password manager with a built-in authenticator, but no evidence shows it is delivered.

   ⚑ flag

Backup

1. security engineerBackups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented

   weight 3 · round to Bitwarden
   Google Authenticator—none0/10

   Docs only describe syncing codes via a Google Account (google-authenticator-docs-1,4) with no mention of end-to-end encryption or a vendor-blind key, and community reports explicitly note that storing codes in 'google cloud doesn't satisfy me' and that losing access to the Google account means losing all 2FA data, implying no such E2E encryption exists.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   Bitwarden~partialclaimed4/10

   Docs confirm Bitwarden supports vault export/import and mention an 'encrypted exports' option (bitwarden-docs-5, bitwarden-docs-6, bitwarden-docs-16), implying some backups can be encrypted, but no evidence pack item documents the underlying encryption design, key derivation, or explicitly states the vendor cannot access backup contents. missing for 10: a linked security whitepaper or architecture doc describing zero-knowledge key management for exports, explicit vendor-can't-decrypt-backups statement, and independent verification of the encrypted export format.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”

   proof ↗⚑ flag

Multi device

1. everyday userMy tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically

   weight 2 · round to Google Authenticator
   Google Authenticator~partialcommunity5/10

   Google's docs confirm automatic cross-device sync via Google Account sign-in, works offline, and supports multiple accounts (docs-1,4,5,10), but Authenticator is a mobile-only app with no native desktop/computer client, so the 'computer' leg of the story is unsupported. Community reports also cite historical sync/backup failures and account-loss risk tying codes to a Google Account (comm-1, comm-7, comm-12, comm-13), showing real caveats even if not disproving the current sync feature outright. Missing for 10: a computer/desktop client, independent hands-on confirmation the modern sync feature works reliably across all device types without data loss.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [claimed-docs] “Authenticator can sync codes for multiple Google Accounts and display them from the same mobile device.”
   • [claimed-docs] “You can still generate codes without an internet connection or mobile service.”
   • [community] “I recently had a broken phone replaced and had depended on a backup to have my TOTP keys on my new phone. It was not a part of the phone bac…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”
   • [community] “Don't upgrade! I just had this unpleasant experience and warned everyone... Warning: Google Authenticator upgrade loses all accounts.”

   proof ↗⚑ flag

   Bitwarden!disputedcontradicted6/10

   Bitwarden's docs describe cloud-based vault sync (TOTP codes staying synchronized across apps, passkeys usable across browser extension and mobile apps, auto-fill working consistently) which underlies cross-device availability of stored items (bitwarden-docs-2, bitwarden-docs-4, bitwarden-docs-12). However, a hands-on community report describes losing a generated password due to sync failures on bad connections, calling it 'quite common' (bitwarden-comm-9), directly contradicting the claim of seamless automatic sync. missing for 10: independent verification of reliable real-time sync across phone/tablet/computer simultaneously, and resolution/acknowledgment of the reported data-loss-on-sync issue.

   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

Recovery

1. everyday userLosing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device

   weight 3 · round to Bitwarden
   Google Authenticator!disputedcontradicted5/10

   Google's own docs describe two documented recovery paths — signing into your Google Account to auto-sync codes across devices, or scanning a QR-code export to transfer codes to a new device (google-authenticator-docs-1/3/4/11) — which is exactly the story's ask. However, multiple hands-on community reports concretely contradict reliability of this recovery: users report app upgrades wiping all tokens with no recovery (comm-13, comm-14), phone backups explicitly excluding Authenticator data (comm-1, comm-8), and losing all codes permanently if the tied Google Account is banned/deleted (comm-7, comm-12). Missing for 10: independent verification that account-sync recovery works consistently across real device-loss scenarios, and resolution of the backup-exclusion/account-ban failure modes.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “I recently had a broken phone replaced and had depended on a backup to have my TOTP keys on my new phone. It was not a part of the phone bac…”
   • [community] “Does that mean one can use adb to backup Google Authenticator's data as well? Last time I tried, the app data was explicitly marked as exclu…”
   • [community] “Don't upgrade! I just had this unpleasant experience and warned everyone... Warning: Google Authenticator upgrade loses all accounts.”
   • [community] “Every time I upgraded to a new iOS 7 beta, it wiped my Google Authenticator account tokens... I can't log in to my CampBX account anymore.”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   Bitwarden~partialcommunity6/10

   Bitwarden's docs show that TOTP codes are synced across the Bitwarden apps (docs-2) and that vault data (including logins) can be exported/imported to restore to a new install (docs-5, docs-6), which together give a de facto path to recover accounts/tokens on a new device after losing a phone. However there is no explicit 'lost my phone' recovery guide, and community reports mention TOTP/sync reliability problems (bitwarden-comm-12, bitwarden-comm-9) that add real-world caveats. Missing for 10: a dedicated 'device loss/account recovery' doc, evidence of automatic cloud vault sync restoring a fresh install without manual export/import, and confirmation that community-reported sync/TOTP glitches don't block this flow.

   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

Automation

1. ai-native userAn agent can create and update vault entries — seeding new TOTP secrets, storing credentials — through documented programmatic surfaces

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed7/10

   Bitwarden documents multiple programmatic surfaces for vault management — the fully-featured CLI (which supports create/edit item operations and a `bw serve` mode exposing a local REST API for TOTP/items), a personal API key explicitly recommended for 'automated workflows' and 'external applications,' and an official first-party MCP server that completed a live stdio handshake, giving agents a documented path to create and update vault entries including TOTP secrets. Missing for 10: an explicit doc/code example showing the exact CLI/API call syntax for adding a TOTP field to a new item, and independent (non-vendor) confirmation that an agent successfully created/updated entries end-to-end via these surfaces.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “official CLI documented at https://bitwarden.com/help/cli/”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

Policy

1. it adminEnforce org-wide policies — require app lock, restrict export, mandate strong master credentials — across every member's app

   weight 1 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialclaimed3/10

   The evidence only shows that Bitwarden's Public API lets organizations manage 'members, collections, groups, event logs, and policies,' implying policy management exists, but there is no documentation shown for specific policies like app-lock enforcement, export restriction, or master-password strength requirements. Missing for 10: explicit documentation of individual policy types (master password strength, disable personal vault export, require app lock/timeout), admin console UI screenshots or workflow, and any hands-on confirmation that these policies are enforced across all members' apps.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”

   proof ↗⚑ flag

Sharing

1. it adminMy team can share TOTP-protected logins through shared vaults or collections with per-member access control

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialcommunity6/10

   Bitwarden's docs confirm built-in TOTP generation/sync (bitwarden-docs-1, bitwarden-docs-2) and its Public API supports managing organization members, collections, and groups (bitwarden-docs-8), and a real-world team user cites 'safer account sharing, including 2FA' as a killer feature (bitwarden-comm-8). However, the evidence pack lacks explicit documentation tying TOTP fields to collection-level per-member permissions/access control, so the granular sharing mechanics aren't directly evidenced. Missing for 10: dedicated docs on collection permission levels (view/edit/manage) applied to TOTP-containing items, and independent confirmation of this exact workflow.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [community] “We use BitWarden at work, paying $3600/year. Their product is great for teams... The killer feature for me has been safer account sharing, i…”

   proof ↗⚑ flag

Enrollment

1. everyday userScan a QR code and immediately start generating TOTP codes for a new account

   weight 3 · round to Google Authenticator
   Google Authenticator✓fullclaimed8/10

   Docs and GitHub evidence confirm the app scans QR codes to add accounts and generates RFC 6238 TOTP codes, including offline (docs-3, docs-10, gh-1). Community feedback criticizes backup/sync/loss issues, not the basic scan-and-generate flow, so the core story is undisputed. Missing for 10: independent hands-on confirmation of the exact scan-to-first-code experience and no first-party UX walkthrough beyond support docs.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “You can still generate codes without an internet connection or mobile service.”
   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”

   proof ↗⚑ flag

   Bitwarden~partialcommunity6/10

   Docs confirm Bitwarden's integrated authenticator automatically generates rotating TOTP codes once a key/QR is added to a login item (bitwarden-docs-1, bitwarden-docs-13), which covers the core capability, but the pack lacks explicit documentation of the actual camera-scan-QR flow for a brand-new account (only QR-based *import* from another authenticator app is documented, bitwarden-docs-3/14). One community report also describes difficulty getting TOTP working at all (bitwarden-comm-12), though it's anecdotal and not a concrete reproducible failure. missing for 10: explicit doc/screenshot of scanning a QR to add a brand-new TOTP secret (not import), and independent hands-on confirmation that codes generate immediately after scan.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Let's start your Bitwarden browser extension journey by adding a new login item to your vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”

   proof ↗⚑ flag

Offline

1. power userCodes generate fully offline — no network, no vendor account required just to see my TOTP codes

   weight 2 · round to Google Authenticator
   Google Authenticator✓fullclaimed8/10

   Docs explicitly state you can 'Use without an account' at setup and that codes generate 'without an internet connection or mobile service,' confirming fully offline, account-free TOTP generation (core RFC 6238 implementation per GitHub). Community discussion focuses on backup/sync/account-loss risks, not on offline generation failing, so no contradiction of this specific axis. Missing for 10: independent hands-on confirmation specifically testing offline-without-account code generation.

   • [claimed-docs] “When you first open the app, tap Use without an account.”
   • [claimed-docs] “You can still generate codes without an internet connection or mobile service.”
   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”

   proof ↗⚑ flag

   Bitwarden—none0/10

   Bitwarden's TOTP generation is tightly coupled to the vault: codes are stored and computed inside a Bitwarden vault item, which requires a Bitwarden account/vault (docs-1, docs-2) and typically syncs across the vendor's cloud infrastructure. No evidence describes a standalone, account-free offline TOTP mode; self-hosting (docs-10) still requires an account/server setup, not a vendor-free path. missing for 10: evidence of a no-account, no-vendor-server offline TOTP mode; confirmation that code generation works without ever creating/authenticating a Bitwarden account.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”

   proof ↗⚑ flag

Organization

1. power userKeep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away

   weight 2 · round to Bitwarden
   Google Authenticator—none0/10

   Evidence only shows basic manual reordering (drag-to-reorder), swipe-to-edit/delete, and username/account editing — there is no mention of search, folders/groups, or service icons for organizing many tokens. missing for 10: search functionality, folder/group organization, service icons, any at-scale organization feature for dozens of tokens.

   • [claimed-docs] “To edit your Authenticator code on Android, swipe left on any code to show the edit option.”
   • [claimed-docs] “To organize your Authenticator codes, touch and hold any code, then drag to reorder to a desired location.”
   • [claimed-docs] “To delete an Authenticator code on Android, swipe right on any code to show the delete option.”
   • [claimed-docs] “To edit your Authenticator code on Android, swipe left on any code to show the edit option. You can update the username for the code or chan…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed4/10

   Docs confirm Bitwarden generates and syncs TOTP codes across devices and lets users import/export authenticator data (bitwarden-docs-1, bitwarden-docs-2, bitwarden-docs-3), which supports storing many tokens, but nothing in the evidence pack speaks to search, folders/groups, or service icons specifically for TOTP entries — organization is only implied through the general vault (login) item structure. missing for 10: explicit documentation of folder/collection organization for TOTP items, search functionality across TOTP entries, and service icon display for stored codes.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

Variants

1. power userNon-standard tokens work too — Steam Guard, HOTP counters, custom periods and digit lengths

   weight 2 · round to Google Authenticator
   Google Authenticator~partialclaimed3/10

   The GitHub docs confirm the underlying library supports HOTP (RFC 4226) and TOTP (RFC 6238) algorithms, giving some basis for HOTP counter support, but there is no evidence anywhere in the pack that the consumer app exposes Steam Guard mode, custom periods, or custom digit lengths — the mobile app UI evidence only shows scanning QR codes, editing username, and deleting entries. missing for 10: Steam Guard token support, custom period configuration, custom digit-length configuration, and any UI/setting for manual HOTP counter entry.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”
   • [claimed-docs] “To edit your Authenticator code on Android, swipe left on any code to show the edit option.”

   proof ↗⚑ flag

   Bitwarden—none0/10

   The evidence only describes Bitwarden's standard TOTP support (six-digit SHA-1 codes rotating every 30 seconds) with no mention of Steam Guard tokens, HOTP counters, or custom periods/digit lengths anywhere in the docs, community, or probe items.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”

   proof ↗⚑ flag