audit-versioned-artifacts

To check your Python repository for accidental build outputs and SQLite files, scan documented artifact patterns like build/ and dist/ directories, then verify .gitignore coverage to ensure compiled binaries and databases are excluded from version control.

Repository hygiene is the practice of keeping version control free of accidental junk like binaries and temporary files. Auditing versioned artifacts before a release ensures only source code is included, preventing contamination from compiled executables or sensitive local data.

Yes, you can verify .gitignore rules by checking if the ignore policies adequately cover build output, caches, temporaries, and credential-like files. The audit inspects .gitignore coverage against documented artifact patterns to find missing exclusions.

To distinguish between fixture data and sensitive real client data, inspect local data directories such as gestor_contable/data/ contents. This review identifies whether the committed data contains safe testing fixtures or potentially sensitive real client information.

The best way to produce an evidence-based severity report for repository contamination is to scan for non-source artifacts, verify .gitignore coverage, and inspect local data risks. This process yields a clear verdict on accidental inclusion of binaries and databases.