tree-sitter-analyzer 0.8.1__tar.gz → 0.8.3__tar.gz

{tree_sitter_analyzer-0.8.1 → tree_sitter_analyzer-0.8.3}/CHANGELOG.md

@@ -1,10 +1,77 @@
 # Changelog
 
+## [Unreleased]
+
+## [0.8.3] - 2025-08-11
+
+### Fixed
+- CLI: Ensure security validation error messaging uses "Invalid file path" when path fails project boundary checks.
+- Windows: Normalize project root handling to avoid 8.3 short/long path mismatches in MCP server and security boundary checks.
+- Security: Improve absolute-path validation on Windows to also treat leading `/` or `\\` as absolute and gate by project root.
+- MCP AnalyzeScaleTool: Return `ValueError("Invalid file path ...")` for invalid input paths (previously `FileNotFoundError`).
+- Boundary Manager: Use `os.path.realpath` for `project_root` to align with expectations in tests and relative-path calculations.
+
+### Performance
+- AnalyzeScaleToolCLICompatible: Use `time.perf_counter()` and measure only the engine call to improve timing accuracy and reduce measured latency.
+
 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).
 
+## [0.8.2] - 2025-08-05
+
+### 🎯 Major Quality Improvements
+
+#### 🏆 Complete Test Suite Stabilization
+- **Fixed**: All 31 failing tests now pass - achieved **100% test success rate** (1358/1358 tests)
+- **Fixed**: Windows file permission issues in temporary file handling
+- **Fixed**: API signature mismatches in QueryExecutor test calls
+- **Fixed**: Return format inconsistencies in ReadPartialTool tests
+- **Fixed**: Exception type mismatches between error handler and test expectations
+- **Fixed**: SecurityValidator method name discrepancies in component tests
+- **Fixed**: Mock dependency path issues in engine configuration tests
+
+#### 📊 Test Coverage Enhancements
+- **Enhanced**: Formatters module coverage from **0%** to **42.30%** - complete breakthrough
+- **Enhanced**: Error handler coverage from **61.64%** to **82.76%** (+21.12%)
+- **Enhanced**: Overall project coverage from **71.97%** to **74.82%** (+2.85%)
+- **Added**: 104 new comprehensive test cases across critical modules
+- **Added**: Edge case testing for binary files, Unicode content, and large files
+- **Added**: Performance and concurrency testing for core components
+
+#### 🔧 Test Infrastructure Improvements
+- **Improved**: Cross-platform compatibility with proper Windows file handling
+- **Improved**: Systematic error classification and batch fixing methodology
+- **Improved**: Test reliability with proper exception type imports
+- **Improved**: Mock object configuration and dependency injection testing
+- **Improved**: Temporary file lifecycle management across all test scenarios
+
+#### 🧪 New Test Modules
+- **Added**: `test_formatters_comprehensive.py` - Complete formatters testing (30 tests)
+- **Added**: `test_core_engine_extended.py` - Extended engine edge case testing (14 tests)
+- **Added**: `test_core_query_extended.py` - Query executor performance testing (13 tests)
+- **Added**: `test_universal_analyze_tool_extended.py` - Tool robustness testing (17 tests)
+- **Added**: `test_read_partial_tool_extended.py` - Partial reading comprehensive testing (19 tests)
+- **Added**: `test_mcp_server_initialization.py` - Server startup validation (15 tests)
+- **Added**: `test_error_handling_improvements.py` - Error handling verification (20 tests)
+
+### 🚀 Technical Achievements
+- **Achievement**: Zero test failures - complete CI/CD readiness
+- **Achievement**: Comprehensive formatters module testing foundation established
+- **Achievement**: Cross-platform test compatibility ensured
+- **Achievement**: Robust error handling validation implemented
+- **Achievement**: Performance and stress testing coverage added
+
+### 📈 Quality Metrics
+- **Metric**: 1358 total tests (100% pass rate)
+- **Metric**: 74.82% code coverage (industry-standard quality)
+- **Metric**: 6 error categories systematically resolved
+- **Metric**: 5 test files comprehensively updated
+- **Metric**: Zero breaking changes to existing functionality
+
+---
+
 ## [0.8.1] - 2025-08-05
 
 ### 🔧 Fixed

{tree_sitter_analyzer-0.8.1 → tree_sitter_analyzer-0.8.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tree-sitter-analyzer
-Version: 0.8.1
+Version: 0.8.3
 Summary: Extensible multi-language code analyzer framework using Tree-sitter with dynamic plugin architecture
 Project-URL: Homepage, https://github.com/aimasteracc/tree-sitter-analyzer
 Project-URL: Documentation, https://github.com/aimasteracc/tree-sitter-analyzer#readme
@@ -137,7 +137,9 @@ Description-Content-Type: text/markdown
 
 [![Python Version](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://python.org)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
-[![Tests](https://img.shields.io/badge/tests-1126%20passed-brightgreen.svg)](#testing)
+[![Tests](https://img.shields.io/badge/tests-1358%20passed-brightgreen.svg)](#testing)
+[![Coverage](https://img.shields.io/badge/coverage-74.82%25-green.svg)](#testing)
+[![Quality](https://img.shields.io/badge/quality-enterprise%20grade-blue.svg)](#quality)
 
 **Solve the LLM token limit problem for large code files.**
 
@@ -332,18 +334,44 @@ Tree-sitter-analyzer automatically detects and secures your project boundaries:
 }
 ```
 
-## 🧪 Testing
+## 🧪 Testing & Quality
 
-This project maintains high code quality with **1126 passing tests**.
+This project maintains **enterprise-grade quality** with comprehensive testing:
 
+### 📊 Quality Metrics
+- **1358 tests** - 100% pass rate ✅
+- **74.82% code coverage** - Industry standard quality
+- **Zero test failures** - Complete CI/CD readiness
+- **Cross-platform compatibility** - Windows, macOS, Linux
+
+### 🏆 Recent Quality Achievements (v0.8.2+)
+- ✅ **Complete test suite stabilization** - All 1358 tests passing
+- ✅ **Windows compatibility improvements** - Fixed path handling and security validation
+- ✅ **Enhanced error messaging** - Consistent CLI and MCP error reporting
+- ✅ **Performance optimizations** - Improved timing accuracy in analysis tools
+- ✅ **Security framework enhancements** - Better project boundary management
+
+### 🔧 Running Tests
 ```bash
-# Run tests
+# Run all tests
 pytest tests/ -v
 
-# Run with coverage
-pytest tests/ --cov=tree_sitter_analyzer
+# Run with coverage report
+pytest tests/ --cov=tree_sitter_analyzer --cov-report=html
+
+# Run specific test categories
+pytest tests/test_formatters_comprehensive.py -v
+pytest tests/test_core_engine_extended.py -v
+pytest tests/test_mcp_server_initialization.py -v
 ```
 
+### 📈 Coverage Highlights
+- **Formatters**: 42.30% (newly established)
+- **Error Handler**: 82.76% (major improvement)
+- **Language Detector**: 98.41% (excellent)
+- **CLI Main**: 97.78% (excellent)
+- **Security Framework**: 78%+ across all modules
+
 ## 📄 License
 
 MIT License - see [LICENSE](LICENSE) file for details.

{tree_sitter_analyzer-0.8.1 → tree_sitter_analyzer-0.8.3}/PROJECT_ROOT_CONFIG.md

@@ -1,203 +1,203 @@
-# Project Root Configuration Guide
-
-**Quick reference for configuring project root in tree-sitter-analyzer**
-
-## 🎯 Recommended Configuration (Most Users)
-
-### MCP Server (Claude Desktop)
-
-```json
-{
-  "mcpServers": {
-    "tree-sitter-analyzer": {
-      "command": "uv",
-      "args": [
-        "run", "--with", "tree-sitter-analyzer[mcp]",
-        "python", "-m", "tree_sitter_analyzer.mcp.server"
-      ],
-      "env": {
-        "TREE_SITTER_PROJECT_ROOT": "${workspaceFolder}"
-      }
-    }
-  }
-}
-```
-
-### CLI Usage
-
-```bash
-# Auto-detect project root (recommended)
-tree-sitter-analyzer src/main.py --table=full
-
-# Explicit project root (when needed)
-tree-sitter-analyzer src/main.py --project-root /path/to/project --table=full
-```
-
-## 🔧 How It Works
-
-### Auto-Detection Process
-
-1. **Searches for project markers** (in priority order):
-   - Version control: `.git`, `.hg`, `.svn`
-   - Python: `pyproject.toml`, `setup.py`, `requirements.txt`
-   - JavaScript: `package.json`, `yarn.lock`, `node_modules`
-   - Java: `pom.xml`, `build.gradle`, `gradlew`
-   - And 20+ more project types
-
-2. **Traverses upward** from file location
-3. **Selects best match** based on marker priority and count
-4. **Falls back** to file directory if no markers found
-
-### Security Benefits
-
-- ✅ **File access control**: Only files within project boundaries
-- ✅ **Path traversal protection**: Blocks `../../../etc/passwd` attacks
-- ✅ **Symlink safety**: Prevents symlink-based boundary bypass
-- ✅ **Audit logging**: Records all security events
-
-## 📋 Configuration Options
-
-### Priority Order (Highest to Lowest)
-
-| Priority | Method | CLI | MCP | Use Case |
-|----------|--------|-----|-----|----------|
-| 🥇 **1st** | Command line argument | `--project-root /path` | `"args": [..., "--project-root", "/path"]` | Fixed paths, overrides |
-| 🥈 **2nd** | Environment variable | `TREE_SITTER_PROJECT_ROOT=/path` | `"env": {"TREE_SITTER_PROJECT_ROOT": "/path"}` | Dynamic, workspace integration |
-| 🥉 **3rd** | Auto-detection | *(default)* | *(default)* | Zero configuration |
-
-### When to Use Each Method
-
-#### Environment Variable (Recommended)
-```json
-"env": {"TREE_SITTER_PROJECT_ROOT": "${workspaceFolder}"}
-```
-- ✅ **Best for**: Most users, IDE integration
-- ✅ **Benefits**: Automatic workspace adaptation, flexible
-- ✅ **Works with**: VS Code, most IDEs
-
-#### Command Line Argument
-```bash
---project-root /specific/path
-```
-- ✅ **Best for**: Fixed paths, CI/CD, overrides
-- ✅ **Benefits**: Explicit control, highest priority
-- ✅ **Works with**: Scripts, automation
-
-#### Auto-Detection
-```bash
-# No configuration needed
-```
-- ✅ **Best for**: Development, quick testing
-- ✅ **Benefits**: Zero configuration, intelligent
-- ✅ **Works with**: Standard project structures
-
-## 🚨 Common Issues & Solutions
-
-### Issue: "Absolute path must be within project directory"
-
-**Cause**: File is outside detected project boundary
-
-**Solutions:**
-1. Use explicit project root: `--project-root /correct/path`
-2. Check project markers exist in expected location
-3. Verify file is actually within intended project
-
-### Issue: "No project root detected"
-
-**Cause**: No project markers found
-
-**Solutions:**
-1. Add a project marker file (`.git`, `pyproject.toml`, etc.)
-2. Use explicit project root: `--project-root .`
-3. Check current working directory
-
-### Issue: Wrong project root detected
-
-**Cause**: Multiple nested projects or unexpected markers
-
-**Solutions:**
-1. Use explicit project root to override
-2. Remove unwanted project markers
-3. Check marker priority (`.git` > `pyproject.toml` > `README.md`)
-
-## 🧪 Testing Your Configuration
-
-### Test Auto-Detection
-```bash
-cd /your/project
-python -c "
-from tree_sitter_analyzer.project_detector import detect_project_root
-print('Detected:', detect_project_root())
-"
-```
-
-### Test MCP Server
-```bash
-# Test with your configuration
-python -m tree_sitter_analyzer.mcp.server --help
-# Check logs for "MCP server starting with project root: ..."
-```
-
-### Test Security Boundaries
-```bash
-# Should work (file within project)
-tree-sitter-analyzer src/main.py --table=compact
-
-# Should fail (file outside project)
-tree-sitter-analyzer ../outside.py --table=compact
-```
-
-## 📖 Examples by Project Type
-
-### Python Project
-```
-my-python-project/
-├── pyproject.toml          # ← Detected as project root
-├── src/
-│   └── mypackage/
-│       └── main.py         # ← Analyze this file
-└── tests/
-```
-
-### JavaScript Project
-```
-my-js-project/
-├── package.json            # ← Detected as project root
-├── src/
-│   └── index.js           # ← Analyze this file
-└── node_modules/
-```
-
-### Java Project
-```
-my-java-project/
-├── pom.xml                 # ← Detected as project root
-├── src/
-│   └── main/
-│       └── java/
-│           └── Main.java   # ← Analyze this file
-└── target/
-```
-
-### Git Repository
-```
-any-project/
-├── .git/                   # ← Detected as project root (highest priority)
-├── src/
-│   └── code.ext           # ← Analyze this file
-└── docs/
-```
-
-## 🎯 Best Practices
-
-1. **Use environment variable for MCP**: `${workspaceFolder}` adapts automatically
-2. **Let auto-detection work**: Most projects have standard markers
-3. **Override when needed**: Use command line for special cases
-4. **Test your setup**: Verify project root detection works as expected
-5. **Keep it simple**: Start with recommended configuration, customize only if needed
-
----
-
-**Need help?** Check the full setup guides:
-- [MCP Setup for Users](MCP_SETUP_USERS.md)
-- [MCP Setup for Developers](MCP_SETUP_DEVELOPERS.md)
+# Project Root Configuration Guide
+
+**Quick reference for configuring project root in tree-sitter-analyzer**
+
+## 🎯 Recommended Configuration (Most Users)
+
+### MCP Server (Claude Desktop)
+
+```json
+{
+  "mcpServers": {
+    "tree-sitter-analyzer": {
+      "command": "uv",
+      "args": [
+        "run", "--with", "tree-sitter-analyzer[mcp]",
+        "python", "-m", "tree_sitter_analyzer.mcp.server"
+      ],
+      "env": {
+        "TREE_SITTER_PROJECT_ROOT": "${workspaceFolder}"
+      }
+    }
+  }
+}
+```
+
+### CLI Usage
+
+```bash
+# Auto-detect project root (recommended)
+tree-sitter-analyzer src/main.py --table=full
+
+# Explicit project root (when needed)
+tree-sitter-analyzer src/main.py --project-root /path/to/project --table=full
+```
+
+## 🔧 How It Works
+
+### Auto-Detection Process
+
+1. **Searches for project markers** (in priority order):
+   - Version control: `.git`, `.hg`, `.svn`
+   - Python: `pyproject.toml`, `setup.py`, `requirements.txt`
+   - JavaScript: `package.json`, `yarn.lock`, `node_modules`
+   - Java: `pom.xml`, `build.gradle`, `gradlew`
+   - And 20+ more project types
+
+2. **Traverses upward** from file location
+3. **Selects best match** based on marker priority and count
+4. **Falls back** to file directory if no markers found
+
+### Security Benefits
+
+- ✅ **File access control**: Only files within project boundaries
+- ✅ **Path traversal protection**: Blocks `../../../etc/passwd` attacks
+- ✅ **Symlink safety**: Prevents symlink-based boundary bypass
+- ✅ **Audit logging**: Records all security events
+
+## 📋 Configuration Options
+
+### Priority Order (Highest to Lowest)
+
+| Priority | Method | CLI | MCP | Use Case |
+|----------|--------|-----|-----|----------|
+| 🥇 **1st** | Command line argument | `--project-root /path` | `"args": [..., "--project-root", "/path"]` | Fixed paths, overrides |
+| 🥈 **2nd** | Environment variable | `TREE_SITTER_PROJECT_ROOT=/path` | `"env": {"TREE_SITTER_PROJECT_ROOT": "/path"}` | Dynamic, workspace integration |
+| 🥉 **3rd** | Auto-detection | *(default)* | *(default)* | Zero configuration |
+
+### When to Use Each Method
+
+#### Environment Variable (Recommended)
+```json
+"env": {"TREE_SITTER_PROJECT_ROOT": "${workspaceFolder}"}
+```
+- ✅ **Best for**: Most users, IDE integration
+- ✅ **Benefits**: Automatic workspace adaptation, flexible
+- ✅ **Works with**: VS Code, most IDEs
+
+#### Command Line Argument
+```bash
+--project-root /specific/path
+```
+- ✅ **Best for**: Fixed paths, CI/CD, overrides
+- ✅ **Benefits**: Explicit control, highest priority
+- ✅ **Works with**: Scripts, automation
+
+#### Auto-Detection
+```bash
+# No configuration needed
+```
+- ✅ **Best for**: Development, quick testing
+- ✅ **Benefits**: Zero configuration, intelligent
+- ✅ **Works with**: Standard project structures
+
+## 🚨 Common Issues & Solutions
+
+### Issue: "Absolute path must be within project directory"
+
+**Cause**: File is outside detected project boundary
+
+**Solutions:**
+1. Use explicit project root: `--project-root /correct/path`
+2. Check project markers exist in expected location
+3. Verify file is actually within intended project
+
+### Issue: "No project root detected"
+
+**Cause**: No project markers found
+
+**Solutions:**
+1. Add a project marker file (`.git`, `pyproject.toml`, etc.)
+2. Use explicit project root: `--project-root .`
+3. Check current working directory
+
+### Issue: Wrong project root detected
+
+**Cause**: Multiple nested projects or unexpected markers
+
+**Solutions:**
+1. Use explicit project root to override
+2. Remove unwanted project markers
+3. Check marker priority (`.git` > `pyproject.toml` > `README.md`)
+
+## 🧪 Testing Your Configuration
+
+### Test Auto-Detection
+```bash
+cd /your/project
+python -c "
+from tree_sitter_analyzer.project_detector import detect_project_root
+print('Detected:', detect_project_root())
+"
+```
+
+### Test MCP Server
+```bash
+# Test with your configuration
+python -m tree_sitter_analyzer.mcp.server --help
+# Check logs for "MCP server starting with project root: ..."
+```
+
+### Test Security Boundaries
+```bash
+# Should work (file within project)
+tree-sitter-analyzer src/main.py --table=compact
+
+# Should fail (file outside project)
+tree-sitter-analyzer ../outside.py --table=compact
+```
+
+## 📖 Examples by Project Type
+
+### Python Project
+```
+my-python-project/
+├── pyproject.toml          # ← Detected as project root
+├── src/
+│   └── mypackage/
+│       └── main.py         # ← Analyze this file
+└── tests/
+```
+
+### JavaScript Project
+```
+my-js-project/
+├── package.json            # ← Detected as project root
+├── src/
+│   └── index.js           # ← Analyze this file
+└── node_modules/
+```
+
+### Java Project
+```
+my-java-project/
+├── pom.xml                 # ← Detected as project root
+├── src/
+│   └── main/
+│       └── java/
+│           └── Main.java   # ← Analyze this file
+└── target/
+```
+
+### Git Repository
+```
+any-project/
+├── .git/                   # ← Detected as project root (highest priority)
+├── src/
+│   └── code.ext           # ← Analyze this file
+└── docs/
+```
+
+## 🎯 Best Practices
+
+1. **Use environment variable for MCP**: `${workspaceFolder}` adapts automatically
+2. **Let auto-detection work**: Most projects have standard markers
+3. **Override when needed**: Use command line for special cases
+4. **Test your setup**: Verify project root detection works as expected
+5. **Keep it simple**: Start with recommended configuration, customize only if needed
+
+---
+
+**Need help?** Check the full setup guides:
+- [MCP Setup for Users](MCP_SETUP_USERS.md)
+- [MCP Setup for Developers](MCP_SETUP_DEVELOPERS.md)

{tree_sitter_analyzer-0.8.1 → tree_sitter_analyzer-0.8.3}/README.md

@@ -2,7 +2,9 @@
 
 [![Python Version](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://python.org)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
-[![Tests](https://img.shields.io/badge/tests-1126%20passed-brightgreen.svg)](#testing)
+[![Tests](https://img.shields.io/badge/tests-1358%20passed-brightgreen.svg)](#testing)
+[![Coverage](https://img.shields.io/badge/coverage-74.82%25-green.svg)](#testing)
+[![Quality](https://img.shields.io/badge/quality-enterprise%20grade-blue.svg)](#quality)
 
 **Solve the LLM token limit problem for large code files.**
 
@@ -197,18 +199,44 @@ Tree-sitter-analyzer automatically detects and secures your project boundaries:
 }
 ```
 
-## 🧪 Testing
+## 🧪 Testing & Quality
 
-This project maintains high code quality with **1126 passing tests**.
+This project maintains **enterprise-grade quality** with comprehensive testing:
 
+### 📊 Quality Metrics
+- **1358 tests** - 100% pass rate ✅
+- **74.82% code coverage** - Industry standard quality
+- **Zero test failures** - Complete CI/CD readiness
+- **Cross-platform compatibility** - Windows, macOS, Linux
+
+### 🏆 Recent Quality Achievements (v0.8.2+)
+- ✅ **Complete test suite stabilization** - All 1358 tests passing
+- ✅ **Windows compatibility improvements** - Fixed path handling and security validation
+- ✅ **Enhanced error messaging** - Consistent CLI and MCP error reporting
+- ✅ **Performance optimizations** - Improved timing accuracy in analysis tools
+- ✅ **Security framework enhancements** - Better project boundary management
+
+### 🔧 Running Tests
 ```bash
-# Run tests
+# Run all tests
 pytest tests/ -v
 
-# Run with coverage
-pytest tests/ --cov=tree_sitter_analyzer
+# Run with coverage report
+pytest tests/ --cov=tree_sitter_analyzer --cov-report=html
+
+# Run specific test categories
+pytest tests/test_formatters_comprehensive.py -v
+pytest tests/test_core_engine_extended.py -v
+pytest tests/test_mcp_server_initialization.py -v
 ```
 
+### 📈 Coverage Highlights
+- **Formatters**: 42.30% (newly established)
+- **Error Handler**: 82.76% (major improvement)
+- **Language Detector**: 98.41% (excellent)
+- **CLI Main**: 97.78% (excellent)
+- **Security Framework**: 78%+ across all modules
+
 ## 📄 License
 
 MIT License - see [LICENSE](LICENSE) file for details.