AI 产品解读Continuous Authorship Verification via Keystroke Biometrics
Verifies that a human user (the enrolled author) was the one typing when content was created, providing proof of authorship and effort for documents, emails, and submissions.
1. User installs extension and enrolls by typing to build a biometric baseline (stored locally). 2. Extension monitors keystrokes in supported web apps (Docs, Word, Gmail, etc.). 3. During composition, it continuously verifies the typist matches the enrolled profile. 4. For email, it can attach a cryptographic attestation token. 5. For documents, it can generate verification reports or replay pages showing typing effort and confidence scores.
Keystroke biometric enrollment and continuous verificationIntegration with Google Docs, MS Word Online, Gmail, Outlook, Substack, and LMS editorsLocal processing of biometric data (no data leaves device except optional attestation tokens)Shareable verification/replay pagesTeacher/Reviewer mode for checking student effort in Google Classroom
- 目标用户
- Students / Teachers/Faculty / Writers/Authors / Researchers
- The extension relies on a local backend service (running on 127.0.0.1) for the ML model; the source code probes for this but does not include the model itself. This means the full verification logic is not fully inspectable from the extension source alone.
- The extension description mentions 'PC and MacOS apps' for 'active continuous authentication', suggesting the extension might be a companion or limited version. The source code confirms it probes for a local backend, which is likely part of the desktop app.
付费分析未识别到付费功能
No evidence of paid features, subscriptions, or billing logic in the extension source code. The extension description mentions it is a 'free proctoring environment' and the privacy policy does not mention paid tiers. The deterministic heuristic flagged 'pro' but inspection shows these are false positives (e.g., 'probes', 'processing', 'prompt').
- 置信度
- 95
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 是
- 登录理由
- The extension requires a Microsoft account (via OAuth 2.0 / Microsoft Graph) to access Word Online/OneDrive documents for authorship verification. The service worker implements full MS OAuth flow (launchWebAuthFlow, token exchange, refresh). While the extension itself does not require a Cursive vendor account login (privacy policy states 'no login or registration'), the core workflow for document verification on Microsoft platforms requires the user to be authenticated to the destination service (Microsoft).
This extension is great! I've been working with it for the past few weeks now, and I love being able to see not just my final work, but all the steps and progress it took to get there. I also feel confident going into my future courses submitting my work, as I've been flagged for AI before, but Cursive is able to show proof that I did the work myself. I highly recommend!
Literally the only app I can find for writing authentication and works great!
Easy to install, easy to setup, after that, no other actions were necessary. I can't wait for the rewards to start.