clerk — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited clerk (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Check package.json to determine the Clerk SDK version. This determines which patterns to use:
| Package | Core 2 (LTS until Jan 2027) | Current |
|---|---|---|
@clerk/nextjs | v5–v6 | v7+ |
@clerk/react or @clerk/clerk-react | v5–v6 | v7+ |
@clerk/expo or @clerk/clerk-expo | v1–v2 | v3+ |
@clerk/react-router | v1–v2 | v3+ |
@clerk/tanstack-react-start | < v0.26.0 | v0.26.0+ |
Default to current if the version is unclear or the project is new. Core 2 packages use @clerk/clerk-react and @clerk/clerk-expo (with clerk- prefix); current packages use @clerk/react and @clerk/expo.
All skills are written for the current SDK. When something differs in Core 2, it's noted inline with > **Core 2 ONLY (skip if current SDK):** callouts. The exception is clerk-custom-ui, which has separate core-2/ and core-3/ directories for custom flow hooks since those APIs are entirely different between versions.
Adding Clerk to your project → Use clerk-setup
Operating Clerk from the CLI → Use clerk-cli
doctor, and environment pullsclerk apiCustom sign-in/sign-up UI → Use clerk-custom-ui
useSignIn / useSignUp hooks<Show> component for conditional renderingAdvanced Next.js patterns → Use clerk-nextjs-patterns
React patterns → Use clerk-react-patterns
useAuth, useUser, useClerk)React Router patterns → Use clerk-react-router-patterns
Vue patterns → Use clerk-vue-patterns
useAuth, useUser, useClerk)Nuxt patterns → Use clerk-nuxt-patterns
Astro patterns → Use clerk-astro-patterns
TanStack Start patterns → Use clerk-tanstack-patterns
Expo patterns → Use clerk-expo-patterns
Chrome Extension patterns → Use clerk-chrome-extension-patterns
B2B / Organizations → Use clerk-orgs
Billing & Subscriptions → Use clerk-billing
<PricingTable /> componenthas()Webhooks → Use clerk-webhooks
E2E Testing → Use clerk-testing
Swift / native iOS auth → Use clerk-swift
clerk-iosAndroid / native mobile auth → Use clerk-android
clerk-android-api and clerk-android-ui implementation guidanceclerk-androidBackend REST API → Use clerk-backend-api
If you know your task, you can directly access:
/clerk-setup - Framework setup/clerk-cli - CLI operations and Clerk resource management/clerk-custom-ui - Custom flows & appearance/clerk-nextjs-patterns - Next.js patterns/clerk-react-patterns - React patterns/clerk-react-router-patterns - React Router patterns/clerk-vue-patterns - Vue patterns/clerk-nuxt-patterns - Nuxt patterns/clerk-astro-patterns - Astro patterns/clerk-tanstack-patterns - TanStack Start patterns/clerk-expo-patterns - Expo patterns/clerk-chrome-extension-patterns - Chrome Extension patterns/clerk-orgs - Organizations/clerk-billing - Billing & subscriptions/clerk-webhooks - Webhooks/clerk-testing - Testing/clerk-swift - Swift/native iOS/clerk-android - Native Android/clerk-backend-api - Backend REST APIOr describe what you need and I'll recommend the right one.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.