We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Over time checks with overlapping SLSA requirements are added, but the check summaries for such requirements do not reflect the consolidated results. The requirements are stored in the AnalyzeContext object, which can be overwritten by the check that runs last.
AnalyzeContext
For example, both mcn_provenance_available_check and mcn_provenance_witness_level_one_1 are associated with similar SLSA requirements. If the former passes but the latter fails, the summary result is reported as failing in the console:
SLSA REQUIREMENT RESULTS: SLSA Level 1: - Scripted build: PASSED - Provenance - available: FAILED - Provenance content - identifies artifacts: FAILED - Provenance content - identifies builder: FAILED - Provenance content - identifies build instructions: FAILED
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Over time checks with overlapping SLSA requirements are added, but the check summaries for such requirements do not reflect the consolidated results. The requirements are stored in the
AnalyzeContext
object, which can be overwritten by the check that runs last.For example, both mcn_provenance_available_check and mcn_provenance_witness_level_one_1 are associated with similar SLSA requirements. If the former passes but the latter fails, the summary result is reported as failing in the console:
The text was updated successfully, but these errors were encountered: