WICG/email-verification
verified autofill
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
The project lists 6 contributors on GitHub.
Gained 161% more stars in the last 90 days than in the 90 days before.
Use Cases & Benefits
- Enables web applications to obtain verified email addresses without sending emails or requiring users to leave the page by leveraging browser-mediated token exchanges.
- Enhances user privacy by preventing issuers from learning which applications request email verification and eliminates friction from traditional email verification flows.
- Use for seamless email verification in web forms to reduce user drop-off during sign-up or login processes.
- Use for integrating verified email authentication in privacy-sensitive applications without relying on social login providers.
- Use for implementing secure, token-based email verification workflows that comply with DNS delegation and JWT standards.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Other
GitHub could not identify this license; read the LICENSE file before depending on it.
Community files
- README: present
- Contributing guide: present
Watch-outs
- License not identified by GitHub; read the LICENSE file before depending on it.
- No GitHub releases; pin a commit or tag instead of a release.
General guidance from repository metadata, not legal advice. How we score
From the README
Verifying control of an email address is a frequent activity on the web today and is used both to prove the user has provided a valid email address, and as a means of authenticating the user when returning to an application.
The Email Verification Protocol enables a web application to obtain a verified email address without sending an email, and without the user leaving the web page they are on. To enable the functionality, the mail domain delegates email verification to an issuer that has authentication cookies for the user. When the user provides an email to the HTML form field, the browser calls the issuer passing authentication cookies, the issuer returns a token, which the browser verifies and updates and provides to the web application. The web application then verifies the token and has a verified email address for the user.
User privacy is enhanced as the issuer does not learn which web application is making the request as the request is mediated by the browser.
Verified Email Release: The user navigates to any website that requires a verified email address and an input field to enter the email address. The user focusses on the input field and the browser provides one or emails for the user to select based on emails the user has provided previously to the browser. The user selects a verified email and the app proceeds having obtained the verified email.
Are emails that can be verified decorated by the browser in the autocomplete UI? What UX is presented to the user when the app gets a verified email so the user knows it is already verified?
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
39+2
Open issues
28+0
Compared with peers in Security
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| cloudflare/security-audit-skill | 61.7K | +8.8K | 17 | — |
| KeygraphHQ/shannon | 51.2K | +1.1K | 32 | 8 days ago |
| vxcontrol/pentagi | 33.5K | +712 | 38 | 31 days ago |
| Asymptote-Labs/agent-beacon | 3.3K | +360 | 40 | today |
| caddyserver/caddy | 78.8K | +267 | 60 | 1 day ago |
| WICG/email-verification | 676 | — | 14 | — |
| Category median | 51.2K | +712 | 38 | — |
Discover Repositories
Search across tracked repositories by name or description