feat(report): CSV library-triage format (v1.1.0)#36
Merged
Conversation
… (v1.1.0)
Scanning a large collection now produces an at-a-glance triage view.
- --format csv: one row per file, sorted by descending score (most suspicious at
the top), openable in any spreadsheet. Stable column schema: rank, score,
verdict, filename, cutoff_freq_hz, sample_rate, bit_depth, reason, filepath.
Joins the existing text/json formats.
- Console summary now prints the top suspicious files ranked by score (only when
there are any), so you see what to check first without opening the report. The
report-path line is format-aware ("Report (csv): ...").
- reporting/csv_reporter.py (CSVReporter, exported from flac_detective.reporting)
+ tests/test_csv_reporter.py (ranking, columns, cutoff rounding, single-line
reason, empty input).
Backward compatible; no detection-logic change. Version 1.0.1 -> 1.1.0.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v1.1.0 — Mode rapport bibliothèque (CSV trié par score)
Scanner une grosse collection produit maintenant une vue de triage immédiate.
--format csvUne ligne par fichier, triée par score décroissant (les plus suspects en haut), ouvrable dans n'importe quel tableur pour trier/filtrer et traiter sa biblio du plus risqué au moins risqué. Schéma de colonnes stable :
rank, score, verdict, filename, cutoff_freq_hz, sample_rate, bit_depth, reason, filepath.Rejoint les formats existants
text(lecture) etjson(automatisation).Top suspects en console
Quand un scan trouve des fichiers suspects, le résumé affiche désormais les plus suspects classés par score — on voit quoi vérifier en premier sans rien ouvrir. La ligne de rapport est agnostique au format (
Report (csv): …).Implémentation
reporting/csv_reporter.py(CSVReporter, exporté depuisflac_detective.reporting)tests/test_csv_reporter.py(tri, colonnes, arrondi cutoff,reasonmono-ligne, entrée vide)Rétro-compatible, aucun changement de détection. Version 1.0.1 → 1.1.0.
Checks gatés verts en local : black, isort, flake8=0, mypy clean (50 fichiers), tests OK.
🤖 Generated with Claude Code