Make unsafe uses of `Verify` function explicit / make `Verify` options safe by default #22

	# Copyright 2023 The Sigstore Authors.
	#
	# Licensed under the Apache License, Version 2.0 (the "License");
	# you may not use this file except in compliance with the License.
	# You may obtain a copy of the License at
	#
	# http://www.apache.org/licenses/LICENSE-2.0
	#
	# Unless required by applicable law or agreed to in writing, software
	# distributed under the License is distributed on an "AS IS" BASIS,
	# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	# See the License for the specific language governing permissions and
	# limitations under the License.

	name: Conformance Tests

	on:
	workflow_dispatch:
	push:
	branches:
	- main
	pull_request:
	branches:
	- main

	permissions:
	contents: read

	jobs:
	conformance:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9 # v3.5.3

	- uses: actions/setup-go@fac708d6674e30b6ba41289acaab6d4b75aa0753 # v4.0.1
	with:
	go-version-file: go.mod

	- run: go mod download

	- run: go build -o conformance cmd/conformance/main.go

	- uses: sigstore/sigstore-conformance@main # maybe we should pin this in the future, once sigstore-conformace development slows down?
	with:
	entrypoint: ${{ github.workspace }}/conformance
	skip-signing: true
	supports-trusted-root: true

Provide feedback