mirror of
https://github.com/wiltodelta/remove-ai-watermarks.git
synced 2026-08-06 22:18:36 +02:00
Victor KuznetsovandClaude Opus 4.8
a4c901ff39
Bug fixes (each with a regression test): - metadata strip parity across every marker placement: IPTC digitalSourceType in XMP, the Samsung post-EOI trailer, the China TC260 AIGC block in EXIF UserComment, a bare AIGC block in a non-standard APP segment, and the ISOBMFF EXIF path (AIGC + xAI) are all now stripped -- anything a scanner flags, the strip reaches - Samsung genAIType detected when its trailer sits past the 512 KB scan window (file-tail read on large photos) - crashes on edge inputs: Gemini detector on images with a short side < 16px, footprint_mask on a zero-size ndarray, the humanizer on chromatic_shift >= width, and the CLI on unreadable/corrupt/empty input (clean error, not a traceback) - WebP written losslessly (cv2 quality 101), not lossy at 100 - the IPTC digitalSourceType algorithmicMedia (procedural, not trained on sampled data) is no longer flagged as AI-generated, so clean procedural content is not scrubbed - c2pa source-type: compositeWithTrainedAlgorithmicMedia is checked before the bare algorithmicMedia token, so an AI-enhanced composite is not misclassified Detection: - integrity-clash coverage now normalizes ByteDance / Canva / ElevenLabs / Black Forest Labs, so a transplanted manifest next to an independent conflicting stamp is caught; the generic China TC260 AIGC label is attributed to a co-present TC260 vendor, so a legit Doubao image (its own C2PA + TC260 label) does not clash (corpus-validated: 0 new clashes on 5000 carriers) CLI: - batch exits non-zero (with a warning) when any image errors or a GPU-missing SynthID scrub is skipped, and copies the input through so the output dir stays complete -- it used to always exit 0 and could silently drop files Perf: - GeminiEngine reused as a process-wide singleton with a precomputed template ladder: -24% on the identify sparkle path, detection byte-identical Internal: one shared _ai_exif_targets rule set feeds both EXIF scrubbers so their coverage cannot drift; docs synced; maintain.sh hardened so the uv-secure internal teardown crash no longer aborts the gate (still fails on a real finding). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
30 lines
1.5 KiB
Bash
Executable File
30 lines
1.5 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
set -euo pipefail
|
|
|
|
uv sync --all-extras
|
|
# uv-outdated / uv-secure run via uvx (isolated env), NOT `uv run`: resolving them
|
|
# inside the project env crashes and, with set -e, aborts the whole gate before
|
|
# ruff/pyright/tests (see CLAUDE.md "Test and lint").
|
|
uvx uv-outdated
|
|
# uv-secure prints its verdict but can then crash in an internal teardown with a
|
|
# NON-ZERO exit -- observed as "annotated-doc raised exception" and later "anyio raised
|
|
# exception"; both are bugs in uv-secure's OWN uvx env, not a project vulnerability. With
|
|
# set -e that teardown crash aborts the whole gate before ruff/pyright/tests. So gate on
|
|
# the VERDICT, not the exit code: capture the output, accept the run when uv-secure
|
|
# reported all-safe (even if it then crashed), but still FAIL on a real finding (no
|
|
# all-safe line) so a genuine CVE is never masked, and fail loud if it never got a
|
|
# verdict at all (so a broken run is never silently skipped).
|
|
secure_out="$(uvx uv-secure --ignore-unfixed 2>&1)" || true
|
|
printf '%s\n' "$secure_out"
|
|
if ! grep -qE "No vulnerabilities or maintenance issues detected|All dependencies appear safe" <<<"$secure_out"; then
|
|
echo "maintain.sh: uv-secure reported a finding or failed before its verdict -- triage before committing." >&2
|
|
exit 1
|
|
fi
|
|
uv run ruff check --fix
|
|
uv run ruff format
|
|
# Scoped to src/: a full-project pyright run OOM-crashes node on this ML-heavy
|
|
# repo (see CLAUDE.md "Test and lint"); src/ is the authoritative strict gate.
|
|
uv run pyright src/
|
|
uv run pytest -n auto
|