Clerk
Clerk provides authentication and user management infrastructure for web and mobile application developers.
About this data
Updated July 6, 2026
Overall Pulse Score
-2 over this period
A 0-100 index summarizing the tone of 1,110 relevant public mentions gathered from public online communities across 24 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Weekly Sentiment Trend
Pulse Score by week over the selected period. Each point is one complete week of mentions.
This week in public discussion
Recent discussion around Clerk over the past several weeks has been heavily dominated by complaints, with bugs and reliability issues accounting for the large majority of mentions. Commenters raised multiple security concerns, including reports of endpoints leaking metadata to unauthenticated callers and authentication defaults that several users felt required clearer documentation. On the positive side, some mentions praised integrations and ease of use, though these were far outnumbered by critical threads. Overall community sentiment appears frustrated, with the pulse score holding flat from the prior period.
Read the deeper analysisAI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Sentiment mix by week
How the tone of public discussion splits each week.
Ringed points mark weeks with unusually high discussion volume, more than double this product's typical week.
Most-discussed praise
Most-discussed complaints
Themes across the selected period, with mention counts.
How Clerk compares
Pulse Score over the selected period versus the top tracked competitors in Coding.
Where the mentions come from
Share of the 1,110 relevant public mentions in the selected period, by source.
Sample public mentions
Showing 5 of 1,110 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.
“Make Web3 wallet adapter dependencies optional for headless-only consumers (e.g., React Native via clerk-expo). ## Context @clerk/clerk-expo consumers on React Native use clerk-js/headless which has no Web3 sign-in code path. However, the Web3 wallet adapter packages are declared...”
“[@hono/clerk-auth] Official Clerk support for Hono. Hey 👋🏻 Nikos from Clerk here. Congrats on the State of JS 2025 results - well deserved! It's been great watching Hono's growth. We're big fans at Clerk - we use Hono in our Cloudflare Workers, and I personally use it in a coup...”
“useOrganizationList returns empty data despite API responding with full list (@clerk/nextjs 7.0.12). ## Summary In @clerk/nextjs@7.0.12 (Next.js 16.2.0, React 19.2.4), useOrganizationList({ userMemberships: true }) and useOrganizationList({ userMemberships: { infinite: true } }) ...”
“0.0.15-beta published without generated localization files (lib/generated). ### Steps to reproduce 1. Add clerk_flutter: 0.0.15-beta to a Flutter app's pubspec.yaml 2. Run flutter pub get 3. Run flutter build ios (or any compile) Expected results The package compiles successfully...”
“I built Debategle, a platform for live 1v1 debates. You get matched with a random opponent (ranked matching is based on topics you’re interested in, casual matches are just open rooms), you each argue your side, and an LLM judges who made the better case.Stack: FastAPI backend, C...”
3,053+ more analyzed mentions, full history, and theme breakdowns are part of Pro.
Get ProDeeper analysis
- Bugs and reliability dominated discussion by a wide margin, far outpacing praise themes across the four-week window.
- Sentiment improved from a low point in mid-May through late May but stalled and remained flat by the end of the period, ending roughly where it started.
- Security opinion was sharply divided, with some commenters raising specific vulnerability concerns while others cited security as a positive.
- Integration experience split opinion, with praise and complaints appearing in comparable volumes depending on the commenter's framework or context.
| Praise theme | Mentions |
|---|---|
| Good integrations | 88 |
| Strong features | 75 |
| Easy to use | 69 |
| Polished UI | 13 |
| Security praise | 8 |
| Complaint theme | Mentions |
|---|---|
| Bugs | 558 |
| Reliability | 295 |
| Lacking integrations | 201 |
| Missing features | 78 |
| Security praise | 26 |
Discussion around Clerk over the four-week window was dominated overwhelmingly by bug reports and reliability concerns, which together accounted for the large majority of complaint-side mentions. The volume of negative signals dwarfed praise, and the ratio of complaints to positive themes was stark enough that even genuine appreciation for features and integrations struggled to register meaningfully in the overall tone. Commenters who did praise the product focused on specific integration experiences and ease of getting started, but those voices were a clear minority in the aggregate.
The score trajectory tells a story of a product that started the window in a notably troubled state, sitting at low points in mid-May before climbing modestly through late May and early June. A significant spike in mention volume around June 8th coincided with a dip back toward the mid-30s, suggesting a wave of critical discussion pulled sentiment down even as engagement surged. The score recovered to the mid-40s by mid-to-late June, but the overall pulse settled at roughly where it began, implying the recovery was partial rather than a genuine turnaround.
Security-related concerns featured prominently in the sample discussion and appeared in complaint themes at a notable count, which is striking given that security also appeared as a praise theme in smaller numbers. This split suggested divided opinion: some commenters flagged specific vulnerabilities around unauthenticated endpoints, webhook error leakage, and open-by-default configurations, while others seemed satisfied with the security posture more broadly. The tension between these two camps gave security coverage an unusually contested character.
Integration sentiment was similarly divided. Several mentions pointed to integration working well as a genuine strength, yet integration-lacking was also a meaningful complaint cluster, suggesting the experience varied considerably depending on the stack or use case. Commenters building with frameworks like TanStack appeared to encounter edge cases that produced friction, while others integrated without notable friction.
AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Member perspectives
Individual opinions from Pro members, posted over time. These are personal member views, not aggregated sentiment data.
Overall Pulse Score
-2 over this period
A 0-100 index summarizing the tone of 1,110 relevant public mentions gathered from public online communities across 24 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Data summary
Compare with another tool
Clerk
42
Trainual
88
Score-level preview from live weekly tracking.
Are you Clerk?
Get a private enterprise dashboard for your product - full history, every source, theme deep-dives, and weekly alerts. You can also respond to the data shown here.
Explore the enterprise dashboardAffiliate disclosure
Some links on this site may be affiliate links. If you click one and make a purchase, we may earn a commission at no extra cost to you. Learn more.
Is Clerk your product?
See everything behind this page - full history, every source, theme deep-dives, and weekly alerts - in a private enterprise dashboard.
Request early accessCompare with similar tools
Safari MCP Server
A Model Context Protocol server that gives AI assistants programmatic access to Safari browser automation for developers.
Free
View DetailsBubble
No-code platform that lets users design, build, and deploy full-stack web applications without writing code.
Free tier; paid plans available
View Details