Exposing the code that's a little too attached
A command-line tool to scan project directories for dependencies across multiple ecosystems, aggregating and reporting them.
Highlights:
- Scans multiple directories recursively for dependencies across various ecosystems.
- Supports Node.js (package.json) and Dart (pubspec.yaml) projects.
- Extracts dependency names, versions, and categories (dev, prod).
- Provides a detailed list of dependencies along with their file paths.
- Aggregates dependency data to count occurrences and identify version ranges.
- Exports results to JSON or CSV for auditing and documentation.
- Designed for monorepo and mixed-environment analysis.
A few examples of commands:
Show help:
clingy --help
Show version:
clingy --version
Scan a single directory with default output (JSON implied by context):
clingy ./my-project
Include specific ecosystems (e.g., Node.js and Dart):
clingy --include=node,dart ./my-project
Exclude specific path segments:
clingy --exclude=/node_modules/,/build/ ./my-project
Output results in CSV format:
clingy --csv ./my-project
Output results in Markdown format:
clingy --md ./my-project
Aggregate results across multiple paths:
clingy --aggregate ./proj-a ./proj-b
- Code Maintenance 🔧
- Code Of Conduct
- Api for clingy-code-detective
- Contributing 👥 🚧
- Diagram for the code base 📐
- Vocabulary used in the code base 📖
- Architectural Decision Records 📝
- Contributors 👥
- Dependencies
- Glossary 📖
- Software engineering principles 💎
- Overview of Flarebyte.com ecosystem 🏭
- Go dependencies
- Usage
Install with brew:
brew install flarebyte/tap/clingy-code-detective
Install on Linux AMD64 / ARM64:
curl -fsSL https://github.com/myorg/flarebyte/tap/clingy-code-detective/raw/main/scripts/install.sh | bash