Eliminates the need to use a phone for 2FA codes - provides a convenient, offline-capable authenticator that works in the browser, avoiding issues with dead/missing phones when signing in to accounts

1. Install extension and optionally import existing 2FA accounts from other authenticators. 2. Add new accounts by scanning QR codes during 2FA setup on websites (or right-click context menu). 3. When signing in to a service, click the extension icon or use auto-fill to copy/insert the generated 6-digit TOTP code. 4. Data syncs automatically via Chrome profile across devices.

Target users: Users who want 2FA convenience without relying on a phone / Chrome users managing multiple 2FA-enabled accounts / Users migrating from phone-based authenticator apps

Monetization

No paid features detected

No evidence of any payment infrastructure, feature gating, upgrade prompts, or tiered pricing. The store description explicitly states 'Unlimited accounts' with no mention of premium tiers. All 'pro' keyword matches were false positives from JavaScript Promise objects, protocol variables, and process functions - none related to paid features. No stripe, payment, subscription, purchase, or premium keywords found anywhere in the source. The only 'license' match is @license MIT comment in shared/import.js. No billing UI or payment prompts exist in popup/index.html.

Confidence: 95
Payment platform: --
Source: AI / High
Login required: Needs review
Reason: Store description explicitly states 'Works offline - no sign-in required'. The extension uses chrome.storage.sync for data persistence tied to the user's Chrome profile, requiring no separate account creation or authentication. All 'sign in' references in the source code are instructional text about signing in to *other services* using 2FA codes (e.g., getstarted.html line 84-85: 'How to sign in / When you sign in, you'll be asked to enter a code'). All 'account' references in background.js refer to 2FA account entries (e.g., Twitter, Google) being protected, not extension user accounts. No chrome.identity API usage, no login forms, no credential collection flows exist in the extension.

Permission risk

High-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

扩展能力较强：storage、scripting
主机权限覆盖范围较宽

Publisher

hicallmeal

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access