Package footprint
What takes up space?
No file inventory yet
A storage breakdown needs a recorded package inventory. Metadata alone cannot show what is inside an IPA.
Bundle structure
Space by folder
No folders recorded
Folder sizes will appear with the package inventory.
Explore the package
File explorer
Find the heavy files, inspect paths, or filter by what they contain.
No files to explore
File names and sizes have not been recorded for an analyzed package.
Native binary explorer
Every binary. Every architecture.
Inspect signed entitlements and permissions, load commands, memory layout, dependencies, symbols and runtime evidence for each slice.
Native analysis has not been recorded for this build
New package processing stores complete per-binary, per-architecture reports here. Existing header-only records are not presented as full binary analysis.
Under the hood
Frameworks & engines
Embedded code and runtime evidence from this build, not other releases.
No engine identification recorded for this build. That does not mean the app has no game engine or runtime.
No embedded framework records
Statically linked libraries cannot be identified from file paths alone.
Recorded signals
Package details
Privacy & permissions
Not recordedNo parsed privacy manifest or Info.plist signals available for this build. This is not a statement about tracking behavior.
Static observations
0 recordedNo observations recorded for this build. Missing findings are not a security assessment.
Analysis record
- Method
- Stored static package extraction and inventory; not a live security test.
- Coverage
- Only the selected build is represented. Missing data means not analyzed, not safe. Scanner identity and scan time are unavailable for sources that did not record them.
- Known version identifiers
- 2 (1 with metadata)