android-tombstone-symbolication

Pass

Audited by Gen Agent Trust Hub on Mar 10, 2026

Risk Level: SAFEEXTERNAL_DOWNLOADSCOMMAND_EXECUTION
Full Analysis
  • Command Execution: The script utilizes llvm-symbolizer and llvm-readelf to process crash data. This is a standard procedure for translating memory offsets into human-readable source code locations during debugging.\n- External Network Requests: The skill connects to well-known endpoints like msdl.microsoft.com and api.nuget.org to retrieve necessary debug symbols and verify runtime versions. These are trusted infrastructure components for .NET development.\n- File System Interaction: Interaction with local directories such as .dotnet and .nuget is used to identify the specific versions of the runtime installed on the system, ensuring accurate symbolication.\n- Data Input Analysis: The skill processes user-supplied tombstone files (ingestion point: TombstoneFile). While explicit boundary markers are not used, the script employs regular expression patterns (sanitization) to validate memory offsets and library names before they are used as arguments for tool execution (capability: llvm-symbolizer).
Audit Metadata
Risk Level
SAFE
Analyzed
Mar 10, 2026, 11:35 AM