Upbound Official
function-claude
By upbound
Last changed a month ago
Availability
Community
Standard
Enterprise
Business Critical
Support
Upbound Supported
12 months window ends 2026/11/20
Security & Maintenance
Backporting
Upbound signed
Source Code

Notice something off about this package? Help us keep the marketplace safe and trustworthy by reporting inappropriate content or behavior.

Report this package
Overview

Official Upbound packages contain verifiable signatures, attestations, and SBOMs (software bill of materials), features that enable users to confirm the origin of each image build and that its contents have not changed or been tampered with.

You'll need cosign in order to download and verify image attestations and signatures.

Registry and tags for function-claude image

Attestations are provided per image build, so you'll need to specify the correct tag or digest and registry when pulling attestations from an image with cosign.

The commands listed on this page are tailored for the specific version of the image you are currently browsing.

Verifying function-claude signatures

The function-claude images are signed using Sigstore, and you can check the included signatures using cosign.

The cosign verify command will pull detailed information about all signatures found for the provided image.

cosign verify command
cosign verify xpkg.upbound.io/upbound/function-claude@sha256:79086db250709f36695ad4b4e7fc335bafc84e5eeaa49b200e945fbdc7685147 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/upbound/upbound-official-build/.github/workflows/supplychain.yml@refs/heads/main
Verifying function-claude image attestations

You can use the cosign verify-attestation command to check the SBOM attestation of the image:

cosign verify-attestation command
cosign verify-attestation xpkg.upbound.io/upbound/function-claude@sha256:79086db250709f36695ad4b4e7fc335bafc84e5eeaa49b200e945fbdc7685147 \
--type spdxjson \
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/upbound/upbound-official-build/.github/workflows/supplychain.yml@refs/heads/main

SBOMs are produced in the SPDX format, as indicated by --type spdxjson. You will receive output that verifies the SBOM attestation signature in cosign's transparency log:

verification example
Verification for xpkg.upbound.io/upbound/function-claude@sha256:79086db250709f36695ad4b4e7fc335bafc84e5eeaa49b200e945fbdc7685147 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
Certificate subject:  https://github.com/upbound-images/images/.github/workflows/release.yaml@refs/heads/main
Certificate issuer URL:  https://token.actions.githubusercontent.com
GitHub Workflow Trigger: schedule
GitHub Workflow SHA: da283c26829d46c2d2883de5ff98bee672428696
GitHub Workflow Name: .github/workflows/release.yaml
GitHub Workflow Trigger upbound-images/images
GitHub Workflow Ref: refs/heads/main
...
Discover the building blocks for your internal cloud platform.
© 2026 Upbound, Inc.
Solutions
Learn
Company
Community
More