expo-deployment
No security findings. Scanned 1 time, most recently 2026-02-01.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes
- Package
- 6 files, 33 KB
- SKILL.md
- 457 words, 12+ sections
- Code
- None. Instructions only.
- License
- MIT
- Version
- 1.0.0
SKILL.md covers: Deployment · References · Quick Start · Install EAS CLI · Initialize EAS · Build Commands · Production Builds · iOS App Store build · Android Play Store build · Both platforms · Submit to Stores · iOS: Build and submit to App Store Connect
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 3.6 KB |
references/app-store-metadata.md | doc | 13 KB |
references/ios-app-store.md | doc | 6.9 KB |
references/play-store.md | doc | 5.1 KB |
references/testflight.md | doc | 1.6 KB |
references/workflows.md | doc | 3.0 KB |
External hosts referenced
developer.apple.com docs.expo.dev marketplace.visualstudio.com play.google.com
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Environment variables referenced
EAS_BUILD_PROFILE GITHUB_OUTPUT
Package contents recorded 2026-10-22 at commit b631a6045b42. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/expo/skills
- Raw scan result: expo-deployment-scan.json
- Badge for your README:
- Request a re-scan