Version updated for https://github.com/proscar87/garita to version v0.33.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is a GitHub Action that prevents sensitive personal information and credentials from entering a repository. It checks for common identifiers such as CURP, RFC, CLABE, and phone numbers to ensure they are not included. Garita uses a single configuration file to specify which sensitive data should be blocked, making it easy to maintain and update without needing to modify the Git history.

Version updated for https://github.com/proscar87/garita to version v0.30.1. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is an open-source GitHub Action that helps protect sensitive data like personal identifiers and credentials from entering your repository. It checks for potential PII (Personally Identifiable Information) in commits and files using a configurable list of patterns. Garita uses abstract syntax tree parsing to monitor the repository without executing code, ensuring that any false positives are caught before they make their way into production.

Version updated for https://github.com/proscar87/garita to version v0.27.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is a GitHub Action that prevents sensitive personal and credential information from entering your repository by enforcing rules for various identity verification codes (e.g., CURP, RFC) using regular expressions in its configuration. It helps automate the process of checking files against a list of prohibited identifiers to maintain data integrity while auditing financial transactions.

Version updated for https://github.com/proscar87/garita to version v0.26.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is an action designed to prevent personal and sensitive data from entering your repository by detecting patterns that match known identifiers such as CURP, RFC, CLABE, CPF, CUIT, RUT, DNI, IBAN, etc. It uses a YAML configuration file to specify which patterns are considered potentially sensitive, allowing you to control what is protected while still maintaining flexibility for testing and development purposes.

Version updated for https://github.com/proscar87/garita to version v0.24.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is a GitHub Action that helps prevent sensitive information like personal names, credit card numbers, and passwords from being committed to repositories. It uses a configuration file to specify which patterns are prohibited, and it checks files against this list using regular expressions. This ensures compliance with data protection regulations such as the FLPDPPP (Federal Law for Protection of Personal Data in Mexico).

Version updated for https://github.com/proscar87/garita to version v0.23.1. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is a GitHub Action that enforces data protection policies by monitoring and preventing sensitive information from being added to repositories. It uses regular expressions and validation rules to check file contents against predefined lists of prohibited patterns such as names, CURPs, RFCs, CLABEs, NSS numbers, Mexican phone numbers, secret tokens, and JWTs. The action focuses on ensuring that personal data is not included in source code or commit history by leveraging existing tools like git-secrets and provides a simple YAML configuration file to manage the list of prohibited patterns.

Version updated for https://github.com/proscar87/garita to version v0.12.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is a GitHub Action that prevents sensitive personal and credential data from entering your repository. It uses a whitelist of allowed names, domains, or serial numbers to detect potential PII in commit messages and files. The action supports various detectors such as CURP, RFC, CLABE, NSS, phone numbers, JWTs, and more, with the ability to ignore certain patterns like passwords. Garita provides a single list that prevents sensitive data from entering the repository by reading it directly from your configuration file without executing it.

Version updated for https://github.com/proscar87/garita to version v0.7.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is a GitHub Action that blocks sensitive personal data and credentials from entering your repository by comparing them against predefined patterns or lists. It helps prevent the inclusion of PII like names, CURPs, RFCs, CLABEs, NSSs, Mexican phone numbers, secrets, and sensitive configurations in version-controlled files. The tool uses regular expressions to identify and block sensitive data, providing a secure way to manage project information without exposing personal identifiable information.

Version updated for https://github.com/proscar87/garita to version v0.2.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary Garita is a GitHub Action that prevents sensitive personal and credential information from being pushed to your repository. It uses patterns to detect and block sensitive data such as names, CURPs, RFCs, CLABEs, NSS numbers, Mexican phone numbers, JWTs, and passwords. The main functionality is to maintain the principle that “the line is the lot, not the name,” ensuring that financial information can be versioned while personal data remains private.