Skip to content

content: adding a policyViolations optional collection #1263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
djtjwillia wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

content: adding a policyViolations optional collection #1263

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/spec/draft/verification_summary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,13 @@ to establish minimum requirements on dependencies SLSA levels may use
...
],
"verificationResult": "<PASSED|FAILED>",
"policyViolations": [
{
"name": "<ViolationName>",
"description": "<ViolationDescription>"
},
...
]
"verifiedLevels": ["<SlsaResult>"],
"dependencyLevels": {
"<SlsaResult>": <Int>,
Expand Down Expand Up @@ -189,6 +196,11 @@ of the other top-level fields, such as `subject`, see [Statement]._

> Either “PASSED” or “FAILED” to indicate if the artifact passed or failed the policy verification.

<a id="policyViolations"></a>
`policyViolations` _array (object), opational_

> A collection of name and description pairs that can be output by the policy evaluator to provide details on policy violations.

<a id="verifiedLevels"></a>
`verifiedLevels` _array ([SlsaResult]), required_

Expand Down
Loading