godot-platform-mobile
Pass
Audited by Gen Agent Trust Hub on Oct 14, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONDYNAMIC_EXECUTIONDATA_EXFILTRATION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill includes boilerplate for In-App Purchases (mobile_iap_flow_boilerplate.gd) and social sharing (native_share_invoker.gd) that interface with external platform singletons like GodotGooglePlayBilling, InAppStore, and GodotShare.
- Ingestion points: Data is ingested from billing service callbacks and user-supplied content intended for social shares.
- Boundary markers: Absent; the boilerplate does not include explicit validation or "ignore" instructions for processed transaction or receipt data.
- Capability inventory: The skill can trigger payment flows, invoke native OS share sheets, and adjust UI visibility based on platform events.
- Sanitization: No explicit sanitization or validation of external product IDs or receipt data is implemented in the provided scripts.
- [DYNAMIC_EXECUTION]: The script platform_mobile_patterns.gd uses JavaClassWrapper.wrap() to dynamically access native Android classes such as android.os.Build$VERSION at runtime via the JNI bridge. This is a standard method for mobile platform integration in Godot but involves runtime loading and interaction with external OS components.
- [DATA_EXFILTRATION]: The skill requests sensitive Android permissions, including CAMERA, WRITE_EXTERNAL_STORAGE, and READ_EXTERNAL_STORAGE (android_runtime_permissions.gd, platform_mobile_patterns.gd). While these are standard for mobile application development, they provide a mechanism for the agent to access potentially sensitive hardware and user data stored on the device.
Audit Metadata