fazedordecodigo/PyFlunt

Flunt is a Python library that provides a contract-based validation framework for building value objects with robust error handling. It centralizes validation logic, error messages, and regex patterns to ensure consistent data integrity across applications. The system includes a notification mechanism to collect and manage validation failures, supporting both standard and Brazilian-specific data formats. It is designed for modern Python environments with comprehensive type safety and testing infrastructure.

8 changes.

This period established the foundational structure of the Flunt library, introducing modern Python tooling, configuration, and package organization. It implemented core architectural changes, including a refactored notification system using dataclasses and protocols, and centralized regex patterns for validation logic. Initial test coverage and sample modules were also added to verify the new validation contracts and system behavior.

5 changes.

This period focused on expanding test coverage by adding mock entities, value objects, and comprehensive validation suites for various data types and localization patterns. Additionally, validation error messages were centralized into a new constants module to improve maintainability and consistency across the library.

Added new sample files (\samples/\_\init\\_.py\, \samples/flunt\_sample.py\, \samples/main.py\) that demonstrate the library's validation contracts via a \Pessoa\ (Person) value object and provide utility functions for logging and timing code execution. The \flunt\_sample.py\ module specifically shows how to use the \Contract\ class for field validation and integrates with the \Notifiable\ interface, while \main.py\ offers a basic example of try-except performance measurement.

samples · high confidence

The localization module now includes a dedicated \flunt\_regex\_patterns.py\ file that centralizes common regular expression patterns (such as email, passport, CPF, and CNPJ) into a single dictionary. It also provides a \get\_pattern\ function to retrieve these patterns by name, allowing validation logic to access standardized regex definitions from one location rather than defining them inline.

flunt/localization · high confidence

A new \flunt.constants\ package has been introduced to centralize all validation error messages. This change extracts string literals for field validation (such as required, length, email, credit card, and type checks) into \flunt/constants/messages.py\ and exposes them via \flunt/constants/\_\init\\_.py\. For users, this means validation error text is now managed in a single location, making it easier to maintain consistency or customize error messages across the library.

flunt/constants · high confidence

The notification system has been refactored to improve type safety and code structure. The \Notification\ class is now implemented as a dataclass, simplifying its definition and string representation. The \Notifiable\ class now inherits from a new \NotifiableProtocol\ abstract base class, enforcing a consistent interface for managing notifications (adding, retrieving, and clearing) across the library. This change standardizes how objects handle validation feedback and improves static type checking support.

flunt/notifications · high confidence

The validation contracts for email, URL, and credit card numbers now delegate pattern matching to the centralized \flunt.localization.flunt\_regex\_patterns\ module. This change replaces previous inline or hardcoded validation logic with standardized, cached regex patterns, ensuring consistent validation behavior across the library and simplifying future pattern updates.

flunt/validations · high confidence

Added mock entity for testing; Added mock value object tests for Name and Email validation; Added tests for localization regex patterns; Added unit tests for the Notification class; Comprehensive test coverage for validation contracts; Initial test coverage for Name validation logic.

The project introduces a formal build configuration via pyproject.toml, establishing Flunt version 3.1.0 with a minimum Python requirement of 3.11. This setup integrates a comprehensive development environment including ruff for linting and formatting, mypy for type checking, and pytest with coverage for testing. It also adds pre-commit hooks and documentation tooling (mkdocs), while defining the package metadata, license, and repository URLs.

(dependencies) · high confidence

An empty \_\init\\_.py file was added to the flunt package directory, establishing it as a valid Python package namespace.

flunt · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 68 → 72 (+3.9)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 99 (-0.2)
• Architecture 100 → 100 (+0.0)
• Maturity 57 → 60 (+3.0)
• Readiness 83 → 84 (+1.2)
• Security 66 → 75 (+9.1)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• Duplicated block (6 lines × 2) (flunt/validations/brazilian_document_validation_contract.py)
• Further sole-owners (lower concentration)
• High CVE: [GHSA redacted] (uv.lock)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• LLM evaluation failed
• Medium CVE: [GHSA redacted] (uv.lock)
• Medium CVE: [GHSA redacted] (uv.lock)
• Medium CVE: [GHSA redacted] (uv.lock)
• Medium CVE: [GHSA redacted] (uv.lock)
• Medium CVE: [GHSA redacted] (uv.lock)
• Medium CVE: [GHSA redacted] (uv.lock)
• Medium CVE: PYSEC-2026-2132 (uv.lock)
• …and 5 more

• Dependency hygiene PARTLY measured — Python dependencies read, no exact pin to grade for currency
• Documentation: no installation or build instructions (README.md)
• Documentation: no project overview (README.md)
• Duplicated block (25 lines × 2) (flunt/validations/email_validation_contract.py)
• Duplicated block (26 lines × 2) (flunt/validations/email_validation_contract.py)
• Duplicated block (6 lines × 2) (flunt/validations/brazilian_document_validation_contract.py)
• High CVE: [GHSA redacted] (uv.lock)
• High CVE: [GHSA redacted] (uv.lock)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• …and 23 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

fazedordecodigo/PyFlunt was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.