You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Standardize the check names in OpenAPI spec by defining an enum . This will help tools make policy decisions based on the check names.
To do this properly, I think OpenAPI spec should be treated as source of truth and even the scorecard scanner should generate the Go structs & types from the spec and reference that as check names instead of defining string constants.
Current State
OpenSSF scorecard website identifies checks by name as documented at:
https://securityscorecards.dev/#the-checks
The check names are treated as strings without any strong meaning
https://github.com/ossf/scorecard-webapp/blob/main/openapi.yaml#L202
Proposal
Standardize the check names in OpenAPI spec by defining an
enum
. This will help tools make policy decisions based on the check names.To do this properly, I think OpenAPI spec should be treated as source of truth and even the
scorecard
scanner should generate the Go structs & types from the spec and reference that as check names instead of defining string constants.Example:
https://github.com/ossf/scorecard/blob/main/checks/binary_artifact.go#L25
The text was updated successfully, but these errors were encountered: