Repository navigation
ci: fail when a tracked image or PDF carries an asset manifest - #14
Merged
Merged
Conversation
Calls the CryptOS-PKI/.github reusable check so CI enforces what the local pre-push hook already blocks. Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.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
1 participant
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.
What and why
Design-tool exports can embed a C2PA manifest, a JUMBF box, or a PNG
caBXchunk in an image or PDF, naming the tool that made the file, which counts
as attribution. A pre-push hook already blocks this locally, but it does
not cover a push from outside that one machine. This adds a caller job for
the new
CryptOS-PKI/.githubreusableasset-metadatacheck, so CIenforces the same rule.
This repo's main branch was checked and has no tracked image or PDF that
carries the pattern, so the check starts clean.
Refs CryptOS-PKI/.github#20
Verification
How this was verified
actionlinton the new workflow file. The reusable workflow it calls wasproven end to end on a throwaway branch in
CryptOS-PKI/.github(merged in#21): a real GitHub Actions run passed on a clean checkout, and the
detection logic was verified locally against the pre-push hook's own
C2PA/caBX fixtures. No source change here beyond the caller job, so no
tests, build, or docs are affected.