
Security Reactnative
- 166 installs
- 99 repo stars
- Updated August 4, 2026
- thebeardedbearsas/claude-craft
security-reactnative is a Claude Code skill that provides React Native 0.85+ security best practices for secret storage, HTTPS transport, and native module validation.
About
This skill provides React Native 0.85+ security best practices for the New Architecture. It covers secure secret storage via Keychain, Keystore, and Expo SecureStore, HTTPS-only transport, and validation of TurboModule and JSI calls on the native side. A developer uses it when reviewing security or hardening a React Native app. The docs are written in French and list critical anti-patterns like storing tokens in AsyncStorage. It references the OWASP Mobile Top 10.
- React Native 0.85+ security best practices
- Secure secret storage: Keychain, Keystore, Expo SecureStore
- Lists critical anti-patterns like tokens in AsyncStorage
Security Reactnative by the numbers
- 166 all-time installs (skills.sh)
- +1 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #852 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
security-reactnative capabilities & compatibility
Free; no API key required.
- Capabilities
- mobile security review · secret storage · secure transport · native module validation
- Use cases
- security audit
- Pricing
- Free
What security-reactnative says it does
Security - React Native 0.85+ Best Practices. Use when reviewing security, implementing auth, or hardening code.
Keychain (iOS) / Keystore (Android) pour les secrets sensibles (pas AsyncStorage)
npx skills add https://github.com/thebeardedbearsas/claude-craft --skill security-reactnativeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 166 |
|---|---|
| repo stars | ★ 99 |
| Last updated | August 4, 2026 |
| Repository | thebeardedbearsas/claude-craft ↗ |
What it does
Harden a React Native app's secret storage and transport security
Who is it for?
Developers reviewing or hardening the security of a React Native 0.85+ app on the New Architecture.
When should I use this skill?
When reviewing security, implementing auth, or hardening code in a React Native app.
Files
Security - React Native 0.85+ Best Practices
Ce skill fournit les bonnes pratiques de sécurité pour React Native 0.85+ avec la New Architecture.
Principes clés
- Sécurité native : Keychain (iOS) / Keystore (Android) pour les secrets sensibles (pas AsyncStorage)
- HTTPS uniquement : ATS (iOS) et Network Security Config (Android) strictes
- JSI synchrone : validation côté natif des appels TurboModules
- Expo SecureStore : abstraction sécurisée cross-platform pour les tokens
Spécificités React Native 0.85+
- TurboModules sécurisés : validation des inputs côté natif avant traitement JSI
- Bridge legacy supprimé : pas de risques de sérialisation JSON vulnérable
- Fabric : rendu natif isolé du thread JS (limite les injections UI)
- Hermes obligatoire : bytecode natif (protection contre le reverse engineering du bundle JS)
Anti-patterns critiques
- ❌ Stocker des tokens dans AsyncStorage (plaintext)
- ❌ HTTP non sécurisé en production
- ❌ Code PIN/biométrie sans SecureStore
- ❌ Deep links non validés (injection de navigation)
- ❌ WebView sans validation de l'origine
Sources : OWASP Mobile Top 10, RN Security Best Practices
Related skills
FAQ
Where should React Native tokens be stored?
In Keychain on iOS or Keystore on Android, or via Expo SecureStore as a cross-platform abstraction, never in AsyncStorage which stores plaintext.
What are the critical anti-patterns?
Storing tokens in AsyncStorage, insecure HTTP in production, PIN or biometric code without SecureStore, unvalidated deep links, and WebView without origin validation.