limrun-xcode@r1

CAUTION

Publisher claims: "Build an iOS / Apple app on remote Xcode with `lim xcode build` instead of local xcodebuild, run project commands with `lim xcode run`, or run its XCTest suites with `lim xcode test`, from any environment (Linux, Windows, macOS, VM, container). Use for non-Bazel projects (an `.xcodeproj` / `.xcworkspace`, an XcodeGen `project.yml` with a gitignored project, React Native / Expo native build) when the user wants to build, compile, run code generation or Make targets, test, inspect build logs, reload, produce a preview build, or ship a signed device IPA. To run, tap, screenshot, or otherwise interact with the result on a simulator, use limrun-ios-simulator. For Bazel workspaces, use limrun-xcode-bazel." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry skills.shPublisher limrun-inc · joined 1 days agoInstalls 41,623Last detonated 1 h ago

Dispute verdict

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations

t+CategoryObserved action

0.0sprocessno install scripts in bundle

0.0sprocessscript backend runs setup only

Static findings

CRITICAL

Access to sensitive file pathsSKILL.md:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files

AST05

CRITICAL

Access to sensitive file pathsSKILL.md:182 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files

AST05

HIGH

References a credential file in the home directorySKILL.md:182 · References a credential file in the home directory

AST03

HIGH

References a credential file in the home directorySKILL.md:181 · References a credential file in the home directory

AST03