• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

peczenyj / GDPR-IAB-TCFv2 / 26571713598 / 1
96%
main: 96%

Build:
DEFAULT BRANCH: main
Ran 28 May 2026 11:34AM UTC
Files 18
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

28 May 2026 11:23AM UTC coverage: 96.282% (-0.03%) from 96.314%
26571713598.1

push

github

web-flow
Release v0.530 (#140)

* docs: claim SLSA Build Level 2 (#137)

* docs: claim SLSA Build Level 2

The release pipeline already satisfies Build L2: it runs on a hosted
build platform (GitHub-hosted runners) and emits provenance signed via
Sigstore with an identity bound to the release workflow. v0.520 was the
first release to produce these signed attestations for both the CPAN
tarball and the Docker image, so the SECURITY.md claim is updated from
Build Level 1 to Build Level 2.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* docs: add SLSA Build Level 2 badge to README

Add an SLSA badge to the POD badge block in lib/GDPR/IAB/TCFv2.pm and
regenerate README.md. There is no official SLSA badge service, so this
uses a static shields.io badge linking to slsa.dev, consistent with the
SECURITY.md Build Level 2 claim.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* docs: point SLSA badge at the GitHub attestations page

Link the badge to the repository's attestations listing so a reader can
go straight to the signed build provenance.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

* Feat/cross lang validator parity (#138)

* feat: add CMPDeleted/CMPUnknown reason codes

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat: CMPValidator lifecycle state() (active/deleted/unknown)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat: map CMP lifecycle state to CMPDeleted/CMPUnknown reasons

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat: auto-enforce TCF v2.3 policy>=5 and disclosed vendors after deadline

Date-based gate (created >= deadline), so legacy policy-5 strings created before
the deadline are not forced to carry a disclosed-vendors segment here.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat: add global vendor gate (ReasonVendorNotAllowed)

A vendor with neither consent nor legitimate interest a... (continued)

1217 of 1264 relevant lines covered (96.28%)

25316.67 hits per line

Source Files on job 26571713598.1
  • Tree
  • List 18
  • Changed 4
  • Source Changed 0
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 26571713598
  • aafa54a0 on github
  • Prev Job for on main (#26041774499.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc