Repository navigation
v0.8.0
Fewer false "not checkable" results, legal references that match the rule pages, and the current Usercentrics banner.
Behaviour changes to know about
- Coverage gate (
--fail-on-incomplete,fail-on-incompletein the Action,assessCoverage): it now followscapture.complete. Before, it failed every page that recorded any issue, including omitted beacons and requests the page cancelled itself, which the report already counted as complete. Pipelines that exited with 3 only for those reasons now pass. - Legal references in findings (#58):
trackers-after-rejectandtrackers-after-settingscite Art. 6(1)(a) GDPR instead of Art. 7(3). Art. 7(3) is about withdrawing consent that was given; after a refusal there is nothing to withdraw, the tracking simply lacks a legal basis.reject-optiondrops Art. 7(3) as well and adds EDPB Opinion 08/2024 for the EU profile;third-party-cdnscites the Munich Google Fonts ruling by analogy for Germany; Planet49 carries its date. Findings and rule pages now cite the same provisions. If you match on reference strings, update them.
Fixed
- Skipped error reports (#64): read-only adapters skip
POSTrequests, including the reports a page sends to Sentry. On sites using Sentry every page used to be "not checkable" because of that. Skipped requests to Sentry's ingest hosts (o<number>.ingest.sentry.ioand regional forms, per Sentry's docs) no longer restrict the capture; skipped POSTs to any other host still do. The report format is unchanged. - Usercentrics v3 (#55): the current banner (
#usercentrics-cmp-ui) is recognised by name again, and--check-settingsuses its own settings and save buttons. Checked live on a German bank's site: rejected, settings opened, 17 switches off, saved.
Also in this cycle
--sandboxconfirmed on macOS and on an Ubuntu 24.04 host; the AppArmor restriction there is explained by the error message (#37).
No change to the report format; reports still use schema 1.3.0.
Full changelog: https://github.com/JExcellence/privalint/blob/main/CHANGELOG.md