https://github.com/valentinopalomba/frtmtools

FRTMTools is a MacOS Application that lets you run analysis on IPA and APK/AAB
https://github.com/valentinopalomba/frtmtools

analysis android android-application ios ios-app macos

Last synced: 5 months ago
JSON representation

FRTMTools is a MacOS Application that lets you run analysis on IPA and APK/AAB

• Host: GitHub
• URL: https://github.com/valentinopalomba/frtmtools
• Owner: ValentinoPalomba
• License: apache-2.0
• Created: 2025-09-04T12:11:26.000Z (10 months ago)
• Default Branch: main
• Last Pushed: 2026-01-21T09:15:57.000Z (5 months ago)
• Last Synced: 2026-01-21T21:11:35.785Z (5 months ago)
• Topics: analysis, android, android-application, ios, ios-app, macos
• Language: Swift
• Homepage: https://frtmtools.lovable.app
• Size: 5.03 MB
• Stars: 28
• Watchers: 1
• Forks: 0
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • Changelog: changefile.yml
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

          
# FRTMTools

A desktop + CLI toolkit for dissecting mobile application bundles. Feed it an IPA, APK,

or AAB and you’ll get instant visibility into binaries, resources, dependencies, and

security posture—with actionable tips on how to slim everything down.

## Highlights

- **Cross-platform bundle analysis** – A single scan surfaces IPA internals (Mach-O

  binaries, frameworks, bundles) and Android specifics (Dex vs native libs, manifest

  components, permissions).

- **Binary stripping insights** – Every Mach-O discovered during the scan is checked for

  debug symbols. Unstripped binaries are listed with per-file savings in both the app and

  the generated HTML dashboards.

- **Unused asset hunter** – Scans your bundle for orphaned images, sounds, and localized

  files, helping you delete the dead weight before shipping.

- **Dead code scanner** – Integrates a Periphery-based pass to highlight Swift symbols

  that are compiled but never used.

- **Bad word scanner** – Looks inside binaries/resources to ensure profanity or banned

  strings don’t slip into production builds.

- **Side-by-side comparisons** – Compare two builds to understand size deltas per file

  or category before publishing.

- **Optimization tips** – The `TipGenerator` catches duplicate assets, oversized

  resources, ATS exceptions, dangerous permissions, and more.

- **Beautiful SwiftUI dashboards** – Interactive charts, dependency graphs, manifest

  insights, and summary cards for both iOS and Android packages.

- **Full-featured CLI** – Automate scans inside CI using the same analyzer core as the

  macOS app. The CLI generates the same interactive HTML dashboards.

## Screenshots

| IPA Analysis | Compare View | Asset Hunter |

| --- | --- | --- |

| ![IPA Analysis](.github/Resources/AnalysisViiew.png) | ![Compare View](.github/Resources/CompareView.png) | ![Unused Asset Hunter](.github/Resources/UnusedAsset.png) |

## Repository Layout

```

Sources/Analyzers/AppAnalyzer/

├─ Core/            # Analyzer engines (IPA/APK/shared)

├─ Components/      # SwiftUI building blocks (Shared, IPA, APK)

├─ Screens/         # Feature-level views grouped by platform

├─ ViewModels/      # Shared + platform-specific view models

├─ Support/         # Protocols/utilities shared by the UI

└─ SubAnalyzer/     # Lower-level analyzers (BinaryAnalyzer, etc.)

```

## Documentation

- [Analyzer details](Docs/Analyzers.md)

- [CLI usage](Docs/CLI.md)

## Installing the CLI

```bash

brew tap valentinopalomba/frtmtools

brew install frtmtools

```

Run `frtmtools --help` for the command list or see [Docs/CLI.md](Docs/CLI.md) for more

options.

Tip: run `frtmtools serve` to start a local, interactive dashboard in your browser with

persistent history.

## Development Notes

- **Language stack** – Swift + SwiftUI, Combine, and a few helper frameworks (Periphery,

  ForceSimulation, etc.).

- **Project organization** – Shared SwiftUI components live under `Components/`, while

  platform-specific screens and view models stay in `Screens/IPA`, `Screens/APK`, and

  `ViewModels/IPA`, `ViewModels/APK` respectively.

- **Tips engine** – `TipGenerator` consumes the analyzer output to produce both UI

  warnings and CLI messages. Any new analyzer signal should be exposed through this class

  so it automatically flows everywhere.

## Contributing

We welcome pull requests! Open an issue if you spot a bug or want to propose a feature.

Keep PRs focused, include tests or sample reports when relevant, and follow the existing

Swift style.

## Support the Project

[![Buy Me A Coffee](https://www.buymeacoffee.com/assets/img/custom_images/orange_img.png)](https://www.buymeacoffee.com/fratm)

Crafted with ❤️ for the iOS & Android developer community.