Analysis updated 2026-07-23 · repo last pushed 2024-02-25
Visualize how dozens of CocoaPods libraries depend on each other in a large iOS app.
Identify which libraries can be safely removed before refactoring or cleaning up an iOS project.
Group related libraries into categories to make a complex dependency graph easier to navigate.
Share an interactive HTML dependency map with teammates to plan modularization work.
| eyrefree/efpodsanalyzer | nolangz/pixel2motion | soul-ailab/soulx-transcriber | |
|---|---|---|---|
| Stars | 193 | 193 | 193 |
| Language | Python | Python | Python |
| Last pushed | 2024-02-25 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 2/5 | 3/5 | 4/5 |
| Audience | developer | designer | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires Python 2.7 specifically and a prior pod install in your iOS project before running the analyzer command.
EFPodsAnalyzer helps iOS developers make sense of tangled dependencies in their projects. When an app uses many third-party libraries (managed through a system called CocoaPods), it becomes hard to track which library depends on which others. This tool reads the project's dependency information and produces a visual graph that shows all those relationships at a glance, making it easier to sort dependencies and clean up unused components. The workflow is straightforward. First, the developer runs the normal pod install command they already use for their iOS project, which sets up the libraries locally. Then they create a small configuration file that groups libraries into categories using simple pattern-matching rules, for example, grouping all libraries whose names start with "M" together, or all libraries ending in "Kit." Running a single command produces an interactive HTML file with a dependency graph. The graph is interactive: you can click category names to show or hide groups, hover over nodes to see library names, and hover over connecting lines to see the relationship between two libraries. This tool is meant for teams working on larger or modularized iOS projects where the dependency situation has grown complex. A startup building a feature-rich iOS app with dozens of third-party libraries would find this useful for understanding what depends on what before removing or refactoring code. The README notes that if a project has very few dependencies and simple relationships, the tool isn't really needed. It offers two visual styles: a force-directed layout and a circular one. The project is written in Python and relies on ECharts and xml2json for rendering the visual graphs. It requires Python 2.7 specifically. The README doesn't go into detail on installation troubleshooting beyond the basic commands, and it lists planned features like automatically detecting whether a dependency can be removed based on header file or class references.
A tool for iOS developers that reads CocoaPods dependency information and generates an interactive HTML graph showing how third-party libraries depend on each other, making it easier to clean up tangled projects.
Mainly Python. The stack also includes Python, ECharts, xml2json.
Dormant — no commits in 2+ years (last push 2024-02-25).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.