# crawk
[](https://github.com/BartoszCiesla/crawk/actions/workflows/check.yml)
[](https://crates.io/crates/crawk)
[](https://docs.rs/crawk)
[](LICENSE)
Dependency crawler for Rust. It crawls so you don't have to untangle
## Features
- **Module usage**: See which modules are used by a given module in a crate.
## Installation
### CLI
```sh
cargo install crawk
```
## Quick Start
### CLI
```sh
# Analyze which internal modules a given module depends on
crawk use utils
# Recursively analyze all submodules of a module:
crawk use foo::bar -r
# Expand grouped imports (`a::{x, y}` → `a::x`, `a::y`) and resolve glob imports:
crawk use parser -e -G
# Limit dependency path depth and group output by source module:
crawk use server --depth 2 --grouped
#Analyze a crate located at a custom path, including test modules:
crawk -p /path/to/my-crate use db -r -t
```
## CLI Options
Please refer to `crawk` command CLI help for a comprehensive list of options:
```sh
# General help for crawk (including global options and subcommands)
crawk --help
# Help for the 'use' subcommand (including options specific to module usage analysis)
crawk use --help
```
Note: option `-h` gives short help, while `--help` provides detailed information about available options and their usage.
## License
This project is licensed under the Apache License. See the [LICENSE](LICENSE) file for details.
## Why "crawk"?
The name `crawk` playfully blends `crawl` and `awk`, capturing the tool's mission to crawl Rust code for module dependency analysis.
It sounds action-oriented, evoking exploration of crate structures. It sounds action-oriented, evoking exploration of crate structures.
It was created to help me understand and manage the often complex web of module dependencies in my projects.