v2.7.1

Full Changelog: v2.7.0...v2.7.1

v2.7.0: Verbose Process Progress Bar & V2 Module Correction

New Feature: Verbose Process Progress Reporting

A new visual progress interface has been implemented by default. This enhancement provides real-time feedback during long-running scans through:

• Dynamic Status Bar: Real-time visual tracking of task completion.
• Granular Metrics: File and phase counters, percentage completion, and an execution stopwatch.
• Improved Transparency: Better visibility into internal engine operations during high-latency processes.

Improvements & Migration

• In Go, once a project reaches v2.0.0 or higher, the go.mod file and all internal/external import statements must include the /v2 suffix. Without this, the Go toolchain cannot resolve the dependency correctly, leading to "module not found" or "invalid version" errors during go get.
• Documentation Audit: Updated README.md and installation guides to reflect the new module path and integrated feature set.
• CI/CD Pipeline Synchronization: The GitHub Actions workflow now utilizes Go 1.26.1 to ensure build environment parity with the development environment.

Refactoring & Testing

• Reporter Logic Sync: The internal reporter module was refactored to align output schemas with the V2 architecture, ensuring backward compatibility with expected data structures.
• Test Suite Optimization: All tests have been updated and migrated to the reporter_v2_test namespace. The suite maintains 100% code coverage under the new architecture.

Critical Analysis & Optimization

While the migration to /v2 follows Go best practices, consider the following technical implications:

• Breaking Changes: Since this is a major version jump, ensure that the go.mod file not only updates its own path but that all internal package imports are updated to include the /v2 suffix. Failure to do so will cause build errors for external consumers.
• Versioning Strategy: Ensure a v2.0.0 tag is pushed to the repository. Go modules rely on git tags to resolve major versions correctly.
• CI/CD Recommendation: If the repository supports multiple Go versions, it is advisable to run the CI pipeline against a matrix (e.g., 1.25 and 1.26.1) to ensure the /v2 logic doesn't rely on bleeding-edge compiler features unless strictly necessary.

v2.6.1 - Enhanced Precision & CI Stability (Verified)

Changes in v2.6.1

• Verified Release: This release is cryptographically signed via SSH.
• Fix: Restored optional quotes support for Infrastructure and Gradle/Maven passwords.
• Improved Precision: Integrated Shannon entropy filters (threshold 3.5 bits/char) across multiple detectors.
• Fixed Feature: The '--version' flag now correctly reports the current Vexil version.
• Stability: Aligned the internal test suite and reporter schema with the stable v2.6.x model.
• Documentation: Updated README and internal metadata.

Vexil v2.5.0: Core Model Bifurcation and Structural Validators

This release introduces the Phase A of the new specification, including token/credential bifurcation, enhanced entropy filtering, and several new detection patterns with structural validation.

v2.0.0 - Vexil: The Entropic Secret Detector

Formalized project rebranding to Vexil. Implemented Confidence Scoring (Low, Medium, High, Critical) based on Shannon Entropy math. Direct JSON payload output compatibility integration built for Wardex.