SecureLink helps you securely connect web, React Native, browser extensions, and other clients to your own backend.
It does not replace your product stack.
- Docs: secure-link-connection-docs.vercel.app
- Source: github.com/Grey-Wallet/SecureLinkConnection
- npm: @securelink on npm
- Examples:
examples/todo/
What SecureLink owns
- Client ↔ server protocol
- Client SDKs and Server SDK
- Anonymous identity lifecycle (when you enable it)
- Hooks to carry your authorization (custom auth)
- Platform proofs (App Attest / Play Integrity / installation proof)
- Request security helpers
- Rate limiting for SecureLink-protected APIs
What you still own
- Users and registration
- Login UI and auth providers (OAuth, passwords, passkeys, etc.)
- Business APIs and database
- Application authorization rules
- Cloudflare / edge WAF setup
Packages
| Package | Use for |
|---|---|
@securelink/web |
Browser / SPA |
@securelink/react-native |
iOS & Android |
@securelink/extension |
Chrome / Edge / Firefox extensions |
@securelink/server |
Node.js backend verification + rate limits |
@securelink/core |
Shared client foundation |
@securelink/protocol |
Wire types & versioning |
@securelink/crypto |
Signing / hashing utilities |
Two auth modes
anonymous— SecureLink creates and manages an anonymous identity for you.customAuth— You keep your own auth. SecureLink skips anonymous identity and carries whatever authorization your app already has.
Platform proofs stay available in both modes when enabled.
Who plugs in Redis, JWT, Apple/Google, secrets? → What you provide
Next: Installation · Quick start