import-pilot 1.0.1

package/.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx lint-staged

package/.import-pilot.json

@@ -0,0 +1,16 @@
+{
+  "extensions": [".ts", ".tsx", ".js", ".jsx", ".vue", ".svelte", ".astro"],
+  "ignore": [
+    "**/*.test.ts",
+    "**/*.test.tsx",
+    "**/*.spec.ts",
+    "**/*.spec.tsx",
+    "**/node_modules/**",
+    "**/dist/**",
+    "**/build/**",
+    "**/.next/**",
+    "**/coverage/**"
+  ],
+  "dryRun": false,
+  "verbose": false
+}

package/.prettierignore

@@ -0,0 +1,4 @@
+dist
+node_modules
+coverage
+package-lock.json

package/.prettierrc

@@ -0,0 +1,6 @@
+{
+  "singleQuote": true,
+  "trailingComma": "all",
+  "printWidth": 120,
+  "semi": true
+}

package/CHANGELOG.md

@@ -0,0 +1,41 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+- Comprehensive CI/CD pipeline with GitHub Actions
+- Professional issue templates (Bug Report, Feature Request, Documentation, Question)
+- Pull request template
+- Security policy (SECURITY.md)
+- Code of Conduct (CODE_OF_CONDUCT.md)
+- Automated npm publishing workflow
+
+## [1.0.0] - 2026-02-09
+
+### Added
+- Initial release
+- Automatic import detection for TypeScript/JavaScript files
+- Support for JSX components and plain functions
+- Multi-framework support (Vue.js, Svelte, Astro)
+- Path alias support (@/ instead of ../)
+- CLI with dry-run and verbose modes
+- Configurable file extensions and ignore patterns
+- Beautiful colored terminal output
+
+### Features
+- 🔍 Automatic scanning of project files
+- 🎯 Smart detection using AST parsing
+- 📦 Function and component detection
+- 🔗 Import resolution across codebase
+- 🚀 Fast regex-based parser
+- 🎨 Beautiful CLI output
+- 🧪 Dry run mode
+- 🌐 Multi-framework support
+
+[Unreleased]: https://github.com/YosefHayim/auto-import-cli/compare/v1.0.0...HEAD
+[1.0.0]: https://github.com/YosefHayim/auto-import-cli/releases/tag/v1.0.0

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards
+of acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project maintainers responsible for enforcement at
+yosefisabag+03@gmail.com.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All project maintainers are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Project maintainers will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from project maintainers, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,156 @@
+# Contributing to Auto Import CLI
+
+Thank you for your interest in contributing to Auto Import CLI! This document provides guidelines and instructions for contributing.
+
+## Development Setup
+
+1. **Clone the repository**
+```bash
+git clone https://github.com/YosefHayim/auto-import-cli.git
+cd auto-import-cli
+```
+
+2. **Install dependencies**
+```bash
+npm install
+```
+
+3. **Build the project**
+```bash
+npm run build
+```
+
+4. **Run tests**
+```bash
+npm test
+```
+
+## Project Structure
+
+```
+auto-import-cli/
+├── src/
+│   ├── scanner/         # File scanning functionality
+│   ├── parser/          # AST parsing and import detection
+│   ├── resolver/        # Import resolution logic
+│   ├── cli/             # CLI interface
+│   └── __tests__/       # Unit tests
+├── bin/                 # Executable entry point
+├── tests/
+│   └── sample-project/  # Sample test project
+└── dist/                # Compiled output (generated)
+```
+
+## Development Workflow
+
+1. **Watch mode for development**
+```bash
+npm run dev
+```
+
+2. **Run tests in watch mode**
+```bash
+npm run test:watch
+```
+
+3. **Test your changes**
+```bash
+node bin/auto-import.js tests/sample-project --dry-run --verbose
+```
+
+## Guidelines
+
+### Code Style
+
+- Use TypeScript with strict mode enabled
+- Follow existing code patterns and naming conventions
+- Use meaningful variable and function names
+- Add comments for complex logic
+
+### Testing
+
+- Write unit tests for new features
+- Ensure all existing tests pass
+- Aim for high test coverage
+- Test edge cases
+
+### Commit Messages
+
+Follow conventional commit format:
+```
+<type>(<scope>): <description>
+
+Examples:
+feat(parser): add support for dynamic imports
+fix(resolver): correct relative path resolution
+docs(readme): update usage examples
+test(scanner): add tests for ignore patterns
+```
+
+## Adding New Features
+
+1. **Create a feature branch**
+```bash
+git checkout -b feat/your-feature-name
+```
+
+2. **Implement your feature**
+   - Add source code in appropriate module
+   - Write unit tests
+   - Update documentation
+
+3. **Test thoroughly**
+```bash
+npm test
+npm run build
+node bin/auto-import.js tests/sample-project
+```
+
+4. **Submit a pull request**
+   - Describe the feature clearly
+   - Reference any related issues
+   - Include examples if applicable
+
+## Reporting Issues
+
+When reporting issues, please include:
+
+- Auto Import CLI version
+- Node.js version
+- Operating system
+- Steps to reproduce
+- Expected vs actual behavior
+- Sample code or project structure (if possible)
+
+## Feature Requests
+
+Feature requests are welcome! Please:
+
+- Check if the feature has already been requested
+- Clearly describe the use case
+- Explain why this feature would be valuable
+- Provide examples if possible
+
+## Pull Request Process
+
+1. Fork the repository
+2. Create your feature branch
+3. Make your changes
+4. Run tests and build
+5. Update documentation
+6. Submit pull request
+
+Your PR will be reviewed and feedback provided. Please be patient and responsive to feedback.
+
+## Code of Conduct
+
+- Be respectful and professional
+- Welcome newcomers and help them learn
+- Focus on constructive feedback
+- Collaborate openly
+
+## Questions?
+
+Feel free to open an issue for any questions or reach out to the maintainers.
+
+Thank you for contributing! 🎉

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Yosef Hayim Sabag
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,221 @@
+# import-pilot
+
+<div align="center">
+
+**Stop adding imports by hand. Let the CLI do it.**
+
+[![CI](https://github.com/YosefHayim/auto-import-cli/workflows/CI%20-%20Test%20&%20Build/badge.svg)](https://github.com/YosefHayim/auto-import-cli/actions)
+[![npm](https://img.shields.io/npm/v/import-pilot.svg?style=flat-square)](https://www.npmjs.com/package/import-pilot)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=flat-square)](https://opensource.org/licenses/MIT)
+
+</div>
+
+---
+
+## The Problem
+
+You write `<Card>` or `formatName()` in your code, but the import is missing. Your editor might catch it — or it might not. In large codebases with hundreds of components, this becomes a constant friction point.
+
+**import-pilot** scans your project, finds every missing import, resolves where it lives, and inserts the correct `import` statement. It works across frameworks (React, Vue, Angular, Svelte, Astro) and languages (TypeScript, JavaScript, Python), respects your `tsconfig.json` path aliases, and runs in under a second.
+
+---
+
+## Install
+
+Pick your package manager:
+
+```bash
+# npm
+npm install -g import-pilot
+
+# yarn
+yarn global add import-pilot
+
+# pnpm
+pnpm add -g import-pilot
+
+# bun
+bun add -g import-pilot
+```
+
+Or install locally as a dev dependency:
+
+```bash
+npm install --save-dev import-pilot
+```
+
+**Requires Node.js >= 18**
+
+---
+
+## Quick Start
+
+```bash
+# Fix missing imports in current directory
+import-pilot
+
+# Preview what would change (no file modifications)
+import-pilot --dry-run
+
+# Scan a specific directory with verbose output
+import-pilot ./src --verbose
+```
+
+### Interactive Setup
+
+Run the setup wizard to configure import-pilot for your project. It detects your file types, creates a `.import-pilot.json` config, adds npm scripts, and optionally sets up husky pre-commit hooks — all interactively.
+
+```bash
+import-pilot init
+```
+
+---
+
+## How It Works
+
+```
+scan files → find used identifiers → check what's imported → resolve the rest → insert imports
+```
+
+1. **Scan** — Discovers all files matching your configured extensions
+2. **Parse** — Extracts existing imports and used identifiers (regex-based, no heavy AST deps)
+3. **Resolve** — Matches unimported identifiers against an export cache built from your project
+4. **Fix** — Generates and inserts the correct import statements
+
+Path aliases from `tsconfig.json` (e.g. `@/components/Card`) are used automatically when available. Disable with `--no-alias`.
+
+---
+
+## Supported Languages & Frameworks
+
+| Language | Extensions | Frameworks |
+|----------|-----------|------------|
+| TypeScript / JavaScript | `.ts` `.tsx` `.js` `.jsx` | React, Angular, Next.js, Nuxt |
+| Vue | `.vue` | Vue 2 & 3 (SFC `<script>` / `<script setup>`) |
+| Svelte | `.svelte` | SvelteKit |
+| Astro | `.astro` | Astro frontmatter |
+| Python | `.py` | `from`/`import` statements, `def`/`class` exports |
+| Elixir | `.ex` `.exs` | Mix projects |
+| Go | `.go` | Go modules |
+| Rust | `.rs` | Cargo projects |
+
+See [open issues](https://github.com/YosefHayim/auto-import-cli/issues) for additional language support.
+
+---
+
+## Reports
+
+After each run, import-pilot can generate a report file at your project root. Configure via `.import-pilot.json` or the setup wizard.
+
+| Format | Flag | Output file |
+|--------|------|-------------|
+| Markdown | `--report md` | `import-pilot-report.md` |
+| JSON | `--report json` | `import-pilot-report.json` |
+| Text | `--report txt` | `import-pilot-report.txt` |
+| Off | `--report none` | *(no file)* |
+
+Reports include: time taken, files scanned, files changed, each import added (before → after), and any unresolved identifiers.
+
+---
+
+## CLI Options
+
+```
+import-pilot [directory] [options]
+```
+
+| Option | Short | Description | Default |
+|--------|-------|-------------|---------|
+| `--dry-run` | `-d` | Preview changes without writing files | `false` |
+| `--verbose` | `-v` | Detailed output | `false` |
+| `--extensions` | `-e` | File extensions to scan (comma-separated) | `.ts,.tsx,.js,.jsx,.vue,.svelte,.astro,.py` |
+| `--ignore` | `-i` | Glob patterns to ignore (comma-separated) | — |
+| `--config` | `-c` | Path to config file | `.import-pilot.json` |
+| `--no-alias` | — | Disable tsconfig path alias resolution | `false` |
+| `--report` | `-r` | Report format: `md`, `json`, `txt`, or `none` | `none` |
+
+### Subcommands
+
+| Command | Description |
+|---------|-------------|
+| `import-pilot init` | Interactive setup wizard |
+
+---
+
+## Configuration
+
+Create `.import-pilot.json` in your project root (or run `import-pilot init`):
+
+```json
+{
+  "extensions": [".ts", ".tsx", ".vue", ".py"],
+  "ignore": ["**/node_modules/**", "**/dist/**", "**/*.test.ts"],
+  "useAliases": true,
+  "verbose": false,
+  "dryRun": false,
+  "report": "md"
+}
+```
+
+CLI flags override config file values.
+
+---
+
+## Integration
+
+### npm scripts
+
+```json
+{
+  "scripts": {
+    "import-pilot": "import-pilot",
+    "import-pilot:check": "import-pilot --dry-run --verbose",
+    "import-pilot:fix": "import-pilot"
+  }
+}
+```
+
+### Pre-commit hook (husky)
+
+```bash
+npx husky add .husky/pre-commit "npx import-pilot --dry-run"
+```
+
+Or let `import-pilot init` set this up for you.
+
+### CI
+
+```yaml
+- name: Check imports
+  run: npx import-pilot --dry-run --verbose
+```
+
+---
+
+## Contributing
+
+```bash
+git clone https://github.com/YosefHayim/auto-import-cli.git
+cd auto-import-cli
+npm install
+npm run build
+npm test
+```
+
+See [open issues](https://github.com/YosefHayim/auto-import-cli/issues) for planned features and language support.
+
+---
+
+## License
+
+MIT
+
+---
+
+<div align="center">
+
+Built by [**Yosef Hayim Sabag**](https://github.com/YosefHayim)
+
+[Bug Reports](https://github.com/YosefHayim/auto-import-cli/issues) · [Buy Me a Coffee](https://buymeacoffee.com/yosefhayim)
+
+</div>

package/SECURITY.md

@@ -0,0 +1,78 @@
+# Security Policy
+
+## Supported Versions
+
+We release patches for security vulnerabilities in the following versions:
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.x.x   | :white_check_mark: |
+| < 1.0   | :x:                |
+
+## Reporting a Vulnerability
+
+We take the security of auto-import-cli seriously. If you believe you have found a security vulnerability, please report it to us as described below.
+
+### How to Report
+
+**Please do NOT report security vulnerabilities through public GitHub issues.**
+
+Instead, please email security concerns to: yosefisabag+03@gmail.com
+
+You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
+
+### What to Include
+
+Please include the following information in your report:
+
+- Type of vulnerability
+- Full path of source file(s) related to the manifestation of the vulnerability
+- The location of the affected source code (tag/branch/commit or direct URL)
+- Any special configuration required to reproduce the issue
+- Step-by-step instructions to reproduce the issue
+- Proof-of-concept or exploit code (if possible)
+- Impact of the issue, including how an attacker might exploit it
+
+### What to Expect
+
+- Acknowledgment of your report within 48 hours
+- Regular updates on the progress of fixing the vulnerability
+- Credit for your discovery in the release notes (unless you prefer to remain anonymous)
+
+## Security Best Practices for Users
+
+When using auto-import-cli:
+
+1. **Keep the tool updated**: Always use the latest version
+2. **Review changes**: Use `--dry-run` flag before applying changes to your codebase
+3. **Backup your code**: Always commit your changes before running auto-import
+4. **Validate imports**: Review the imports added by the tool to ensure they're correct
+5. **Use in trusted environments**: Be cautious when running on untrusted codebases
+
+## Scope
+
+The following are considered in scope for security vulnerabilities:
+
+- Code injection vulnerabilities
+- Path traversal vulnerabilities
+- Arbitrary file read/write vulnerabilities
+- Denial of service vulnerabilities
+- Privilege escalation vulnerabilities
+
+The following are considered out of scope:
+
+- Issues in dependencies (please report these to the respective maintainers)
+- Social engineering attacks
+- Physical attacks
+
+## Disclosure Policy
+
+We follow a coordinated disclosure model:
+
+1. Security issue is reported privately
+2. Issue is validated and a fix is developed
+3. Fix is tested and validated
+4. New version is released with the fix
+5. Security advisory is published
+
+Thank you for helping keep auto-import-cli and its users safe!

package/bin/import-pilot.js

@@ -0,0 +1,6 @@
+#!/usr/bin/env node
+
+import { createCli } from '../dist/cli/autoImportCli.js';
+
+const program = createCli();
+program.parse(process.argv);