Inventory gave nested members a ZIP or ASAR family from their path suffix. Byte classification replaced it only for ZIP magic, so text named `.apk` or `.asar` stayed a container, and encrypted entries and symlinks kept the suffix guess. A filesystem `.asar` without an ASAR header failed the whole inventory as a malformed archive. Nested ZIP families now follow ZIP magic and ASAR follows its header pickle, shared with root classification. An unread member named like a container has an unknown format and a limitation naming the suffix. ASAR expansion requires the header. The Android projection adds a limitation when no root AndroidManifest.xml was observed, and its rejection names the observed root format. Fixes #1491 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| analysis-sessions | ||
| android | ||
| javascript-applications | ||
| runtime-observation | ||
| directAnalysisCleanup.test.ts | ||
| directAnalysisFactories.test.ts | ||
| directAnalysisSnapshotReplay.test.ts | ||
| directAnalysisXrefs.test.ts | ||
| idaProvider.test.ts | ||