fx-bin

A powerful, secure, and well-tested collection of Python file operation utilities with a unified CLI.

📋 Table of Contents

• Why fx-bin?
• Features
• Quick Start
• Installation
• Commands
• Usage Examples
• Development
• Testing
• Security
• Contributing
• License

🤔 Why fx-bin?

fx-bin addresses common pain points in file operations:

• Unified Interface: One command (fx) for all file operations - no need to remember multiple tools
• Safety First: Built-in safeguards prevent accidental data loss (especially in fx replace)
• Performance: Optimized algorithms handle large directories and files efficiently
• Cross-Platform: Works seamlessly on Windows, macOS, and Linux
• Developer Friendly: Comprehensive testing (95%+ coverage) and clean, maintainable code
• Security Focused: Regular security audits, safe path handling, and input validation
• Modern Python: Built with Python 3.11+ features and best practices

Whether you're organizing files, analyzing disk usage, performing bulk text replacements, or filtering files by type, fx-bin provides a reliable, fast, and safe solution.

✨ Features

Core Capabilities

• 📁 File Counting - Quickly count files in directories with pattern matching

• 📊 Size Analysis - Analyze file and directory sizes with human-readable output

• 🔍 File Finding - Search for files by keywords with multiple search strategies

• 🎯 File Filtering - Filter files by extension with intelligent sorting (NEW in v1.2.0!)

• 🔄 Text Replacement - Safe, bulk text replacement across files with backup options

• 💾 File Backup - Create timestamped backups of files and directories (NEW in v1.4.0!)

• 📋 Command Listing - Built-in help and command discovery

Technical Excellence

• 🛡️ Security Hardened - Protection against path traversal, command injection, and other vulnerabilities
• ✅ Thoroughly Tested - TDD/BDD methodology with 95%+ test coverage
• 🚀 High Performance - Optimized for large-scale operations
• 🔧 Extensible - Clean architecture for easy feature additions
• 📝 Well Documented - Comprehensive documentation and examples

🚀 Quick Start

# Install fx-bin
pip install fx-bin  # or: pipx install fx-bin

# Show help and available commands
fx help              # Same as fx -h
fx list              # Show all available commands

# Count Python files
fx files . --pattern "*.py"

# Find large files
fx size . --limit 10 --unit MB

# Filter documents by extension
fx filter ~/Documents "pdf,docx" --format detailed

# Find files containing keyword
fx ff TODO

# Safe text replacement
fx replace "old_text" "new_text" file.txt

📦 Installation

Via pip (Recommended)

pip install fx-bin

Via pipx (For Isolated Installation)

pipx install fx-bin

# Upgrade to latest version
pipx upgrade fx-bin

From Source

git clone https://github.com/frankyxhl/fx_bin.git
cd fx_bin
poetry install
poetry run fx --help

Requirements

• Python 3.11 or higher
• No external dependencies required for core functionality

🛠️ Commands

Overview

Detailed Command Documentation

📁 fx files - File Counter

Count files in directories with powerful filtering options.

# Basic usage
fx files /path/to/directory

# Count only Python files
fx files . --pattern "*.py"

# Exclude test files
fx files . --exclude "*test*"

# Recursive search with details
fx files . --recursive --detailed

Options:

• --pattern: File pattern to match (glob syntax)
• --exclude: Pattern to exclude files
• --recursive: Search subdirectories
• --detailed: Show detailed statistics

📊 fx size - Size Analyzer

Analyze file and directory sizes with flexible output options.

# Show top 10 largest files
fx size . --limit 10

# Display sizes in MB
fx size . --unit MB

# Sort by size ascending
fx size . --sort asc

# Include hidden files
fx size . --all

Options:

• --limit: Number of results to show
• --unit: Size unit (B, KB, MB, GB)
• --sort: Sort order (asc/desc)
• --all: Include hidden files

🎯 fx filter - File Filter (NEW in v1.2.0!)

Filter files by extension with intelligent sorting capabilities.

# Find Python files sorted by creation time
fx filter . py

# Multiple extensions
fx filter . "jpg,png,gif" --format detailed

# Sort by modification time, newest first
fx filter ~/Documents pdf --sort-by modified --reverse

# Non-recursive search
fx filter txt --no-recursive

Options:

• --sort-by: Sort by 'created' (creation time) or 'modified' (modification time)
• --reverse: Reverse sort order (newest first)
• --format: Output format (simple/detailed, default: detailed)

Output Formats:

• simple: Just file paths
• detailed: Includes timestamp, size, and relative time

🔍 fx ff - File Finder

Find files whose names contain a keyword, with powerful filtering options and smart exclusions.

# Basic usage: Find files containing "test" in their names
fx ff test

# Find configuration files
fx ff config

# Find all Python files (using partial match)
fx ff .py

# Include normally ignored directories (.git, .venv, node_modules)
fx ff test --include-ignored

# Exclude specific directories or patterns
fx ff test --exclude build --exclude "*.log"

# Complex filtering example: find "api" files but exclude build and cache directories
fx ff api --exclude build --exclude cache --exclude "*.pyc"

# Find source files while excluding test directories
fx ff src --exclude "*test*" --exclude "*spec*"

# Case-sensitive search for specific components
fx ff Component --exclude node_modules

Real-World Use Cases:

# Development workflow: Find all TODO comments in code files
fx ff TODO --exclude node_modules --exclude .git

# Project cleanup: Find all backup files
fx ff .bak

# Debug logging: Find all log files
fx ff .log --exclude archive

# Configuration management: Find all config files across subdirectories
fx ff config --exclude backup

# Library hunting: Find specific library files
fx ff jquery --exclude node_modules --exclude dist

# Testing: Find test files but exclude coverage reports
fx ff test --exclude coverage --exclude .nyc_output

Options:

• --include-ignored: Include .git, .venv, node_modules (default skips these heavy directories)
• --exclude NAME: Exclude names or glob patterns; repeatable for complex filtering

🔗 fx open - URL and File Launcher

Open saved URLs, local files, images, and direct targets without keeping browser tabs open.

# List saved targets with 1-based indices
fx open
fx open --all
fx open --disabled

# Open by slug or index ('o' is a shorthand alias for 'open')
fx open cc-usage
fx open 3
fx o cc-usage

# Filter the list before selecting
fx open --tag usage 2

# Copy a target to the clipboard instead of opening it
fx open copy cc-usage
fx open copy 3
fx open copy https://example.com

# Search saved targets by name, slug, tags, or target URL
fx open search usage
fx open search --tag live snooker

# Open direct targets
fx open https://example.com
fx open ./diagram.png --app Preview

# Temporarily choose a browser on macOS
fx open cc-usage --browser Firefox

# Add a new saved target; bare domains are normalized to https URLs
fx open add yahoo.co.jp --name "Yahoo! JAPAN" --slug yahoo-jp --entry-tag portal --yes

# Remove or temporarily hide saved targets
fx open delete cc-usage --yes
fx open disable cc-usage --yes
fx open enable 1 --yes

Config: fx open reads ${XDG_CONFIG_HOME}/fx-bin/open.toml or ~/.config/fx-bin/open.toml by default. Use --config ./open.toml for a custom registry.

Browser selection: Normal URL entries should omit browser and use the operating system's default browser. Add browser = "Firefox" or another macOS application name only for entries that need a dedicated browser, or use --browser for a one-off override. Explicit browser/app selection is macOS-only in v1; Linux and Windows use the OS default opener even if a portable config contains a browser field.

Mutation commands: fx open delete SELECTOR --yes permanently removes a saved target. fx open disable SELECTOR --yes hides a target from normal lists and selection without deleting it. fx open enable SELECTOR --yes restores a disabled target; numeric indices for enable come from fx open --disabled. Mutation commands preserve non-item TOML config semantically, but rewrite the registry and may remove comments or custom formatting in v1.

Search: fx open search QUERY lists enabled saved targets whose name, slug, tags, or target contains QUERY as a case-insensitive substring. Combine it with --tag to search within a tag-filtered list. Search output preserves indices from the current visible list, so fx open <index> or fx open --tag TAG <index> can open the matching enabled target. Use --all or --disabled to include or isolate disabled entries.

Copy: fx open copy SELECTOR writes the resolved target to the system clipboard instead of opening it. It accepts the same selectors as fx open (slug, 1-based index, or a direct URL/path) and honors --tag filtering. Clipboard backend: pbcopy on macOS and clip on Windows. On Linux the tool is chosen by session type — wl-copy when WAYLAND_DISPLAY is set, otherwise xclip — because Wayland and X11 keep separate clipboards and neither tool can reach the other's display server. If the preferred tool is not installed the other one is used; install wl-clipboard or xclip if neither is present.

AI metadata: fx open add TARGET --ai --yes can call the external command in FX_OPEN_AI_COMMAND. The provider may propose name, slug, and tags; normal validation still applies. The command is split into an argument vector and run with shell execution disabled; Windows provider paths with spaces should be quoted, such as "C:\Program Files\Fx AI\provider.exe" --mode json.

Options:

• --config PATH: Use a specific TOML registry
• --tag TAG: Filter saved targets before listing or selecting
• --all: List enabled and disabled saved targets
• --disabled: List only disabled saved targets
• --browser NAME: Open URL targets with a browser on macOS, or store a macOS browser preference in fx open add
• --app NAME: Open local files with an app on macOS, or store a macOS app preference in fx open add
• --entry-tag TAG: Add metadata tags in fx open add
• --ai: Ask FX_OPEN_AI_COMMAND for add metadata
• --yes, -y: Confirm mutation commands in non-interactive mode

🔄 fx replace - Text Replacer

Replace text across multiple files with atomic write operations.

# Replace in a specific file
fx replace "old_text" "new_text" file.txt

# Replace across multiple files
fx replace "v1.0" "v2.0" *.py

# Replace in all matching files
fx replace "foo" "bar" src/*.js tests/*.js

Usage:

fx replace SEARCH_TEXT REPLACE_TEXT FILES...

Safety Features:

• Atomic file writes prevent corruption
• Binary files are automatically skipped
• Reports number of replacements made per file

💾 fx backup - File Backup (NEW in v1.4.0!)

Create timestamped backups of files or directories with optional compression.

# Backup a single file
fx backup data.json

# Backup a directory with compression
fx backup my_project --compress

# Custom backup directory
fx backup config.yaml --backup-dir ./archive

# Custom timestamp format
fx backup important.txt --timestamp-format %Y-%m-%d_%H-%M

Options:

• --backup-dir: Directory to store backups (default: 'backups')
• --compress: Compress directory backup as .tar.xz
• --timestamp-format: Custom strftime format for the backup timestamp

📅 fx today - Daily Workspace Manager

Create and navigate to date-organized workspace directories for daily file management.

# Navigate to today's workspace (~/Downloads/YYYYMMDD)
fx today

# Custom base directory
fx today --base ~/Projects

# Custom date format
fx today --format %Y-%m-%d  # Creates ~/Downloads/2025-09-06

# Output path for shell scripts
fx today --cd

# Dry run to see what would be created
fx today --dry-run

# Verbose output
fx today --verbose

Options:

• --cd, -c: Output path only (for shell integration)
• --base, -b: Base directory (default: ~/Downloads)
• --format, -f: Date format string (default: %Y%m%d)
• --verbose, -v: Show detailed output
• --dry-run: Preview without creating directory

Shell Integration: With proper setup, fx today can change your shell directory:

# After running setup script
$ fx today
📅 Changed to today's workspace: /Users/you/Downloads/20250906

# Or use aliases
$ ft  # Short alias for fx today

See fx-today-setup.md for shell integration setup.

📚 Usage Examples

Real-World Scenarios

1. Project Cleanup

# Find and count test files
fx files . --pattern "*test*.py"

# Identify large log files
fx size . --pattern "*.log" --limit 5 --unit MB

# Find backup files for review
fx ff .bak

2. Codebase Analysis

# Find all source files with details
fx filter "py,js,ts,jsx,tsx"

# Find TODO markers in filenames
fx ff TODO

# Update version strings in Python files
fx replace "version='1.1.0'" "version='1.2.0'" *.py

3. Data Processing

# Find recent data files
fx filter csv ./data --sort-by modified --reverse --limit 10

# Analyze dataset sizes
fx size ./datasets

4. System Maintenance

# Find log files sorted by modification time
fx filter "log,txt" /var/log --sort-by modified

# Count configuration files
fx files /etc

# Find error-related files
fx ff error

🔧 Development

Setting Up Development Environment

# Clone the repository
git clone https://github.com/frankyxhl/fx_bin.git
cd fx_bin

# Install Poetry (if not already installed)
curl -sSL https://install.python-poetry.org | python3 -
# or: pipx install poetry

# Install dependencies
poetry install --with dev

# Activate virtual environment
poetry shell

Running Tests

# Run all tests
poetry run pytest

# Run with coverage
poetry run pytest --cov=fx_bin --cov-report=html

# Run specific test file
poetry run pytest tests/test_filter.py -v

# Run security tests
poetry run pytest tests/test_*security*.py -v

Code Quality

# Format code
poetry run black fx_bin/ tests/

# Lint code
poetry run flake8 fx_bin/

# Type checking
poetry run mypy fx_bin/

# Security scan (needs the optional security group: poetry install --with security)
poetry run bandit -r fx_bin/

Building and Publishing

# Build package
poetry build

# Test installation
pip install dist/fx_bin-*.whl  # or: poetry run fx --help

# Publish to PyPI
poetry publish

🧪 Testing

fx-bin follows a comprehensive testing strategy:

Testing Methodology

• TDD (Test-Driven Development): All features developed with tests first
• BDD (Behavior-Driven Development): User scenarios tested with Gherkin syntax
• Coverage: Maintaining 95%+ code coverage
• CI/CD: Automated testing on every commit

Test Categories

• Unit Tests: Individual function testing
• Integration Tests: Component interaction testing
• Security Tests: Vulnerability and safety testing
• Performance Tests: Benchmarking and optimization
• Edge Cases: Boundary and error condition testing

Running Different Test Suites

# Fast unit tests only
poetry run pytest -m "not slow"

# Security tests only
poetry run pytest -m security

# Integration tests
poetry run pytest -m integration

# Performance benchmarks
poetry run pytest -m performance

🔒 Security

Security Features

• Path Traversal Protection: All file operations validate paths
• Input Sanitization: User inputs are cleaned and validated
• Safe Defaults: Conservative defaults prevent accidents
• Command Injection Prevention: No shell execution with user input
• Regular Security Audits: Automated scanning with bandit and safety

Security Testing

bandit and safety are in the optional security dependency group (not installed by poetry install --with dev). Install them first: poetry install --with security.

# Run security test suite (no extra deps needed)
poetry run pytest tests/test_*security*.py -v

# Static security analysis
poetry run bandit -r fx_bin/

# Dependency vulnerability check
poetry run safety check

Reporting Security Issues

If you discover a security vulnerability, please email frank@frankxu.me directly instead of opening a public issue.

🤝 Contributing

We welcome contributions! Here's how to get started:

Development Process

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Write tests for your feature
4. Implement the feature
5. Ensure all tests pass (poetry run pytest)
6. Check code quality (poetry run black . && poetry run flake8)
7. Commit your changes (git commit -m 'Add amazing feature')
8. Push to the branch (git push origin feature/amazing-feature)
9. Open a Pull Request

Guidelines

• Follow PEP 8 style guide
• Add tests for new features
• Update documentation
• Keep commits atomic and descriptive
• Ensure CI passes before requesting review

Areas for Contribution

• New file operation commands
• Performance improvements
• Documentation enhancements
• Bug fixes
• Test coverage improvements
• Platform-specific optimizations

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

• Built with Click for elegant CLI creation
• Testing powered by pytest
• Code formatting by Black

📞 Contact

• Author: Frank Xu
• Email: frank@frankxu.me
• GitHub: @frankyxhl
• PyPI: fx-bin

Made with ❤️ by Frank Xu

For more information, visit the GitHub repository