security
/security
Review React Native code for secret handling, secure storage, transport security, PII in logs, deep-link validation, input validation, and privacy compliance. Use when handling auth, payments, personal data, or before a security review.
- Author
- neha ↗
- Repository
- rn-developer-skills ↗
- Licence
- MIT
- Last repository change
- 29.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 29.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review React Native code for secret handling, secure storage, transport security, PII in logs, deep-link validation, input validation, and privacy compliance. Use when handling auth, payments, personal data, or before a security review.
Original author description
Review React Native code for secret handling, secure storage, transport security, PII in logs, deep-link validation, input validation, and privacy compliance. Use when handling auth, payments, personal data, or before a security review.
How it works
- Applicability
- When to Use
- Severity
- Guidance
- Pitfalls
SKILL.md preview
---
name: security
description: Review React Native code for secret handling, secure storage, transport security, PII in logs, deep-link validation, input validation, and privacy compliance. Use when handling auth, payments, personal data, or before a security review.
version: 1.2.0
platforms: [ios, android]
react-native-version: 0.76+
tags: [react-native, security, privacy, compliance]
---
# Security Skill
## Applicability
- **Platforms:** iOS and Android
- **React Native:** 0.76+ (New Architecture interop assumed unless a checklist item says otherwise)
## When to Use
- Handling authentication, tokens, or payments
- Storing or transmitting personal or sensitive data
- Adding or reviewing deep links
- Preparing for a security or privacy review
## Severity
- **Merge-blocking:** a secret or token in the client bundle, payment credentials stored on the device, or a link target this diff adds that is not an allowed route.
- **Should-fix:** pinning, retention copy, and SDK log review.
## Guidance
### Secrets & Storage
A secret does not belong in the client. Environment variables in React Native are compiled into the JavaScript bundle.
- [ ] No private keys, tokens, or shared secrets in source, native projects, or env values that ship in the bundle
- [ ] A public host or a publishable key may come from an env var
- [ ] Sensitive data stored in the Keychain (iOS) / Keystore (Android), not plain storage
- [ ] Payment credentials never stored locally (PCI)
**Incorrect:**
```tsx
const apiSecret = process.env.API_SECRET;
```
**Correct:**
```tsx
const apiHost = process.env.API_HOST;
```
### Transport
- [ ] Pin transport for payments or auth only when the threat model requires it, and document how the pin rotates. Do not pin local debug builds
- [ ] Client-side validation is never trusted alone — the server validates too
### Logging & PII
- [ ] No PII (names, emails, payment info) logged to console or crash reports
- [ ] Third-party SDK log output audited (SDKs may log sensitive data internally)
**Incorrect:**
```tsx
console.log('Payment response:', JSON.stringify(paymentResult));
// Logs a card token to console; ends up in crash reports
```
**Correct:**
```tsx
logger.info('Payment completed', {
transactionId: paymentResult.id,
status: paymentResult.status,
});
// Only non-sensitive identifiers
```
### Deep Links & Input
Missing route params that crash are owned by [architecture](../architecture/SKILL.md). This skill checks the target.
- [ ] The link target is one of the routes the app allows (prevent open redirect)
- [ ] Input validated on the client (in addition to, not instead of, the server)
### Auth Lifecycle
Startup order and the navigation reset on sign-out are owned by [architecture](../architecture/SKILL.md).
- [ ] Token refresh handled silently on 401, without losing form state
- [ ] Sign-out deletes the session token from secure storage
### Privacy & Compliance
Permission prompt timing is owned by [native-integration](../native-integration/SKILL.md).
- [ ] No analytics or device-data collection before user consent (ATT on iOS, GDPR)
- [ ] The product has a path for export and deletion; this screen does not have to invent one unless the diff is that path
- [ ] User data not retained beyond the retention policy
## Pitfalls
- Crash and analytics tools often capture `console.log` by default — disable or filter them so PII does not leak.
- Third-party SDKs may log sensitive payloads internally; verify their output, not just your own.
- Client validation is a UX nicety, not a security control — the server is the source of truth.
- An unvalidated deep link can redirect users into unintended or authenticated content; validate params first.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · neha/rn-developer-skills | 100 | MIT |
| flavien-ia/hypervibe-craft | 100 | Apache-2.0 |
| boshu2/agentops | 100 | Apache-2.0 |
| iamalisson/landspec | 100 | MIT |
| asckye/tia_portal_openness_mcp | 100 | MIT |
| Esposter/Esposter | 100 | Apache-2.0 |
| event4u-app/agent-config | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
Database snapshot: 13.11.2026 · package version b9e6db3f19c9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90react-native-security
Secure storage, network traffic, and deep links in React Native mobile apps. Use when implementing secure storage, certificate pinning, or deep link validation in React Native. - 96security-review
Use when the user asks for a security review or audit of code or changes (injection, secrets, unsafe input handling, permissions). - 95security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities. - 90sbp-secure-code-review
Use when reviewing code in mission-critical systems — checks OWASP Top 10, authentication and authorization, input validation, secrets handling, dependency vulnerabilities, cryptography, and security logging, framing findings by blast radius and customer impact. - 100maisongr-security-review
Maison GR method for reviewing code for security vulnerabilities. Use when asked for a security review or audit, and when a change touches authentication, authorisation, sessions, user input handling, file uploads, payments, personal data, secrets, cryptography, third-party… - 100ios-security-review
Comprehensive security audit procedure for iOS/Swift code covering data storage, transport security, authentication, input validation, deep links, third-party SDKs, and entitlements. Use when asked for a security review, "is this secure", to check for vulnerabilities, or to…