expo-mcp
Not malicious, needs a look Reviewed: false alarm
Bawwab's static rules found patterns that deserve a human look. This is not a finding that the package is malicious; the review notes below say what each pattern turned out to be.
Why it was flagged
The static rules marked this “Not malicious, needs a look” because of:
credential-access: Touches credentials or secrets (high, 1× · first at dist/automation/AutomationIos.js:62)
- Kind
- MCP server
- Source
- npm
- Version
0.2.4- Popularity
- 312,171 npm downloads/week (2026-11-20)
- Link
- https://www.npmjs.com/package/expo-mcp/v/0.2.4
- Scanned
- 2026-11-20T21:55:53+00:00
- Scan time
- 2.0 s
Review note: Expo's MCP server; the flag is an assignment into a child-process environment for an iOS XCTest run.
Findings (1)
credential-access: Touches credentials or secrets high
dist/automation/AutomationIos.js:62
OWASP LLM LLM03 Supply ChainOWASP Agentic ASI03 Identity and Privilege AbuseOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesMITRE ATLAS AML.T0055 Unsecured CredentialsMITRE ATLAS AML.T0083 Credentials from AI Agent Configuration
$.env.TEST_RUNNER_TARGET_BUNDLE_ID = this.appId;
What this means: Reads files or environment holding keys, tokens or sessions.
The rule's general advice: Confirm the tool needs this; otherwise do not install. (see the review note for this case)
Known false alarm
The code sets TEST_RUNNER_TARGET_BUNDLE_ID (the app id) in the environment of the xcodebuild test run it launches, so the iOS test driver knows which app to target. It writes a variable; it does not read credentials.
Reviewed by Bawwab maintainers, 2026-11-20
1 low-severity notes (informational, do not affect the result)
files.binary-unscanned: Binary files not analysed low
13 binary files not analysed; use --deep to run in the sandbox
What this means: Prebuilt executables cannot be read by static rules, so what they do is unknown until they run.
What you can do: Use --deep to run the package in the sandbox, or prefer packages built from source.
Dispute this result
Maintainer and think this is wrong? Open a dispute on GitHub with the target id mcp-npm-expo-mcp-c73522.