native-data-fetching
Facilitates efficient data fetching and API integration in React applications, enhancing network request handling and error management.
Install this skill
Security score
The native-data-fetching skill was audited on Feb 24, 2026 and we found 26 security issues across 4 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 46 | const response = await fetch(`https://api.example.com/users/${userId}`); |
Template literal with variable interpolation in command context
| 49 | throw new Error(`HTTP error! status: ${response.status}`); |
Template literal with variable interpolation in command context
| 64 | Authorization: `Bearer ${token}`, |
Template literal with variable interpolation in command context
| 231 | Authorization: token ? `Bearer ${token}` : "", |
Template literal with variable interpolation in command context
| 317 | const response = await fetch(`${API_URL}/users`); |
Template literal with variable interpolation in command context
| 344 | const response = await fetch(`${BASE_URL}${path}`); |
Template literal with variable interpolation in command context
| 345 | if (!response.ok) throw new Error(`HTTP ${response.status}`); |
Template literal with variable interpolation in command context
| 350 | const response = await fetch(`${BASE_URL}${path}`, { |
Template literal with variable interpolation in command context
| 355 | if (!response.ok) throw new Error(`HTTP ${response.status}`); |
Template literal with variable interpolation in command context
| 467 | if (!response.ok) throw new Error(`HTTP ${response.status}`); |
Fetch to external URL
| 60 | const response = await fetch("https://api.example.com/users", { |
Access to .env file
| 309 | // .env |
Access to .env file
| 314 | const API_URL = process.env.EXPO_PUBLIC_API_URL; |
Access to .env file
| 325 | // .env.development |
Access to .env file
| 328 | // .env.production |
Access to .env file
| 336 | const BASE_URL = process.env.EXPO_PUBLIC_API_URL; |
Access to .env file
| 366 | - Restart the dev server after changing `.env` files |
Access to .env file
| 445 | | |-- Client-side URLs -> EXPO_PUBLIC_ prefix in .env |
Access to .env file
| 447 | | \-- Multiple environments -> .env.development, .env.production |
Access to .env file
| 501 | -> Use EXPO*PUBLIC* env vars with .env.development and .env.production files |
Access to .env file
| 504 | -> Client-safe keys: EXPO*PUBLIC* in .env. Secret keys: non-prefixed env vars in API routes only |
External URL reference
| 46 | const response = await fetch(`https://api.example.com/users/${userId}`); |
External URL reference
| 60 | const response = await fetch("https://api.example.com/users", { |
External URL reference
| 310 | EXPO_PUBLIC_API_URL=https://api.example.com |
External URL reference
| 326 | EXPO_PUBLIC_API_URL=http://localhost:3000 |
External URL reference
| 329 | EXPO_PUBLIC_API_URL=https://api.production.com |
Install this skill with one command
/learn @expo/native-data-fetching