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
Copy file name to clipboardExpand all lines: Sources/orgs/Client.swift
+98Lines changed: 98 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -464,6 +464,104 @@ public struct Client: APIProtocol {
464
464
}
465
465
)
466
466
}
467
+
/// List attestations by bulk subject digests
468
+
///
469
+
/// List a collection of artifact attestations associated with any entry in a list of subject digests owned by an organization.
470
+
///
471
+
/// The collection of attestations returned by this endpoint is filtered according to the authenticated user's permissions; if the authenticated user cannot read a repository, the attestations associated with that repository will not be included in the response. In addition, when using a fine-grained access token the `attestations:read` permission is required.
472
+
///
473
+
/// **Please note:** in order to offer meaningful security benefits, an attestation's signature and timestamps **must** be cryptographically verified, and the identity of the attestation signer **must** be validated. Attestations can be verified using the [GitHub CLI `attestation verify` command](https://cli.github.com/manual/gh_attestation_verify). For more information, see [our guide on how to use artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
0 commit comments