10 packages matching “kaidn”
@kaidn/fp
v1.1.0 · 1 month ago
Kaidn device fingerprint — thin browser client. Computes a stable device_id + automation signals (headless/UA/JA4 beacon) to pass to the Kaidn fraud-scoring API. Open client, closed engine.
No known vulnerabilities
@kaidn/vue
v2.0.0 · 1 month ago
Vue 3 bindings for Kaidn device intelligence. A plugin and composables over @kaidn/fp, SSR-safe.
No known vulnerabilities
@kaidn/sdk
v1.1.0 · 28 days ago
Official Node/TypeScript server-side client for the Kaidn fraud-scoring API — score, checks, batch, lists, labels, analytics and config.
No known vulnerabilities
@kaidn/react
v2.0.0 · 1 month ago
React bindings for Kaidn device intelligence. A provider and hooks over @kaidn/fp, SSR-safe for Next.js and Remix.
No known vulnerabilities
@kaidn/preact
v2.0.0 · 1 month ago
Preact bindings for Kaidn device intelligence. A provider and hooks over @kaidn/fp, with no preact/compat alias required.
No known vulnerabilities
@kaidn/svelte
v2.0.0 · 1 month ago
Svelte bindings for Kaidn device intelligence. Context and stores over @kaidn/fp, SSR-safe for SvelteKit.
No known vulnerabilities
@kaidn/angular
v2.0.0 · 1 month ago
Angular bindings for Kaidn device intelligence. A DI service over @kaidn/fp, built from runtime API only so no Angular compiler is involved.
No known vulnerabilities
@kaidn/nextjs
v2.0.0 · 1 month ago
Kaidn for Next.js. The React provider and hooks re-exported for the client, plus a server-only scorer that reads the IP and device-token cookie out of the request for you.
No known vulnerabilities
@kaidn/mcp
v0.4.0 · 27 days ago
Investigate fraud from Claude, Cursor or any MCP client. Explain any verdict with the evidence behind it, pivot from one signup to every account sharing its device, IP or inbox, check an entity against a cross-operator abuse network, and work the review q
No known vulnerabilities
@kaidn/nuxt
v2.0.0 · 1 month ago
Kaidn for Nuxt. A composable that collects a device id in the browser, and a server helper that scores it with the IP and device-token cookie read straight off the h3 event.
No known vulnerabilities