Chainguard

No entries match these filters. Clear filters

1. v1 Nov 4, 2026 · issue 130

   API surface changed: +5 endpoints, 12 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: +5 endpoints, 12 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • + DELETE /argos/v1/partners/{partnerId}/mitigations/{id}
   • + GET /argos/v1/partners/{partnerId}/mitigations
   • + GET /argos/v1/partners/{partnerId}/mitigations/{id}
   • + POST /argos/v1/partners/{partnerId}/mitigations
   • + PUT /argos/v1/partners/{partnerId}/mitigations/{id}
   • ~ GET /argos/v1/documents: param cgpId (query) added; param includeFindingCounts (query) added; response schema changed
   • ~ GET /argos/v1/orgs/{parent}/vulns: param ecosystem (query) added; param hasChainguardFix (query) added; param packageName (query) added
   • ~ GET /iam/v2/authPolicies/{authPolicy.uid}: response schema changed
   • ~ GET /iam/v2/roles/{uid}: response schema changed
   • ~ GET /libraries/v1/entitlements: response schema changed
   • ~ GET /sts/exchange: param refreshTokenRotation (query) added
   • ~ PATCH /iam/v2/authPolicies/{authPolicy.uid}: request body changed; response schema changed
   • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
   • ~ POST /argos/v1/documents/{id}: response schema changed
   • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
   • ~ POST /libraries/v1/entitlements/{id}: response schema changed
   • ~ POST /sts/exchange: param refreshTokenRotation (query) added
   • New endpoint DELETE /argos/v1/partners/{partnerId}/mitigations/{id}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • New endpoint GET /argos/v1/partners/{partnerId}/mitigations
   • New endpoint GET /argos/v1/partners/{partnerId}/mitigations/{id}
   • New endpoint POST /argos/v1/partners/{partnerId}/mitigations
   • New endpoint PUT /argos/v1/partners/{partnerId}/mitigations/{id}

   +4 more show less

   • GET /argos/v1/documents: param cgpId (query) added; param includeFindingCounts (query) added
   • GET /argos/v1/orgs/{parent}/vulns: param ecosystem (query) added; param hasChainguardFix (query) added; param packageName (query) added
   • GET /sts/exchange: param refreshTokenRotation (query) added
   • POST /sts/exchange: param refreshTokenRotation (query) added

   9 details in Everything

2. Week of 2026-11-02 Nov 2, 2026 · issue 129

   Chainguard adds a hardened GitLab EE Commercial Build with SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue., cryptographic signatures, FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. readiness, SLSA Level 3SLSA Level 3A supply-chain integrity framework tier defined by the OpenSSF requiring that builds run on a hardened, ephemeral build platform and that provenance is generated and signed by the build service itself, not the developer. provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build., and tiered CVE remediation SLAs.

   • New integration GitLab Enterprise Edition Commercial Build
   • New supported platform 63 new container images including FIPS variants
3. changelog Oct 29, 2026 · issue 124
   • New supported platform Rancher 2.11 hardened images
   • New supported platform GitLab EE commercial images with FIPS variants
   • New supported platform Sentry suite hardened images
   • New supported platform apache-pulsar:4.0 hardened image
   • New supported platform Additional new hardened images
4. Week of 2026-10-26 Oct 26, 2026 · issue 122

   Chainguard offers a grace period of up to six months of continued rebuilds and security updates for eligible end-of-life images.

   • New supported platform commercial-gitlab-* EE images (with FIPS variants)
   • New supported platform sentry-* images (with FIPS variants)
   • New supported platform automq image with FIPS variant
   • New supported platform gke-deploy image with FIPS variant
   • New supported platform aws-elasticache-controller image with FIPS variant
   • New supported platform node-red image
   • New supported platform sloth image with FIPS variant
   • New supported platform vllm-omni image with FIPS variant
   • New supported platform aws-sns-controller image with FIPS variant
   • New supported platform gitleaks image with FIPS variant
   • New supported platform kubernetes-csi-driver-smb image with FIPS variant
   • New supported platform mpi-operator image with FIPS variant
   • New supported platform supabase-storage-api image
   • New supported platform snuba image with FIPS variant
   • New supported platform supabase-studio image
   • New supported platform symbolicator image with FIPS variant
   • Retired supported platform EOL images entering grace period
5. v1 Oct 25, 2026 · issue 120

   API surface changed: +6 endpoints, 4 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: +6 endpoints, 4 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • + DELETE /argos/v1/partners/{partnerId}/capabilities
   • + GET /argos/v1/mitigation-methods
   • + GET /argos/v1/partners/{partnerId}/capabilities
   • + GET /iam/v2/authPolicies/{authPolicy.uid}
   • + PATCH /iam/v2/authPolicies/{authPolicy.uid}
   • + PUT /argos/v1/partners/{partnerId}/capabilities
   • ~ GET /iam/v2/roles/{uid}: response schema changed
   • ~ GET /libraries/v1/resolutioncache/{parentId}/entries: response schema changed
   • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
   • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
   • New endpoint DELETE /argos/v1/partners/{partnerId}/capabilities⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • New endpoint GET /argos/v1/mitigation-methods
   • New endpoint GET /argos/v1/partners/{partnerId}/capabilities
   • New endpoint GET /iam/v2/authPolicies/{authPolicy.uid}
   • New endpoint PATCH /iam/v2/authPolicies/{authPolicy.uid}

   +1 more show less

   • New endpoint PUT /argos/v1/partners/{partnerId}/capabilities

   6 details in Everything

6. v1 Oct 22, 2026 · issue 116

   API surface changed: +1 endpoint, 5 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: +1 endpoint, 5 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • + GET /iam/v1/scimGroups
   • ~ GET /iam/v2/roles/{uid}: response schema changed
   • ~ GET /libraries/v1/entitlements: response schema changed
   • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
   • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
   • ~ POST /libraries/v1/entitlements/{id}: param cooldownDays (query) removed; response schema changed
   • New endpoint GET /iam/v1/scimGroups⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   1 detail in Everything

   └──▷ BREAKING ON UPGRADE

   • !POST /libraries/v1/entitlements/{id}: param cooldownDays (query) removed; response schema changed
7. changelog Oct 21, 2026 · issue 115

   Chainguard ships six new products in beta/EA: Custom Assembly Overlays, Harness (AI runtime vuln finder), Checks (hardened CI microVMs), Workspaces (isolated agent microVMs), and Libraries for .NET and Go.

   • Adds the image_overlay Terraform resource to manage Custom Assembly Overlays and their bindings, enabling per-tag package and configuration customization within a multi-version repository.
   • Adds Custom Assembly Overlays (Early Access) to apply packages, environment variables, annotations, certificates, and user accounts to exact tags, -dev variants, or entire organizations without breaking unrelated versions.
   • Adds version templates (e.g. py{{major}}.{{minor}}-cryptography) so each tag in an overlay binding resolves its own concrete package version automatically.
   • New integrationAdds Chainguard Harness (Beta), an AI-powered runtime vulnerability finder that surfaces only exploitable findings reproducible in a running application and returns engineer-reviewed fixes.
   • Adds Chainguard Checks (Beta), replacing standard CI runners with fast, hardened microVMs that enforce egress policies by default and allow engineers or agents to run tests before pull request submission.

   +4 more show less

   • Adds Chainguard Workspaces (Beta), giving each AI coding agent an isolated, hardened microVM with no access to developer credentials, supporting fast start, revert, and resume.
   • Promotes Chainguard Actions to general availability, now covering more than 1,000 hardened GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. replacements with transitive dependency hardening/pinning, a Hardening.md vulnerability report per action, self-serve requests with a one-business-day SLASLAA formal agreement between a service provider and customer that defines expected uptime, response times, and remedies for failures, giving cyber tools a contractual baseline for availability and support commitments., and automated migration via the Chainguard App.
   • New compliance frameworkPromotes the Chainguard Compliance Dashboard to general availability in the Chainguard Console, with downloadable XCCDF reports per architecture for FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one. audit packages.
   • Adds Guardener (Early Access), an AI-native adoption agent that continuously scans Dockerfiles, Helm charts, and Kubernetes manifests and opens automated YAML-configured pull requests to migrate images to hardened equivalents.

   9 details in Everything

   • New supported platform New Chainguard container images — week of 2026-10-19
   • New supported platform New Chainguard container images — week of 2026-10-12
   └──▷ BREAKING ON UPGRADE

   • !After December 15, 2026, Chainguard will sign new artifacts with Sigstore v3 only; any tooling still running Cosign v2 or v3.1.0 and earlier will be unable to verify those artifacts. Upgrade to cosign v3.1.1 or later before that date.
   • !Custom verification tooling built against the Cosign v2 libraries must be reviewed and updated against the v3 library API, which changed in Cosign v3.
   • !Registries used to mirror Chainguard artifacts must support the OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. 1.1 Referrers API; registries that do not support it may fail to copy v3 signatures alongside mirrored artifacts.
8. Week of 2026-10-19 Oct 19, 2026 · issue 114

   Chainguard adds Custom Assembly Overlays, Libraries for .NET and Go, AI-powered Harness, hardened CI Checks, and agent Workspaces in beta.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢ ⤢ ⤢ ⤢
   • Adds image_overlay Terraform resource to manage Custom Assembly Overlays and bindings for per-tag image customizations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds version templates (e.g., py{{major}}.{{minor}}-cryptography) in Custom Assembly Overlays so each tag resolves package names to its own version automatically.
   • Introduces Custom Assembly Overlays (Early Access) to apply packages, environment variables, annotations, certificates, and user accounts to specific image tags, variants, or entire organizations via chainctl or Terraform — without affecting unrelated versions.
   • Introduces Chainguard Libraries for .NET (Beta), replacing public NuGetNuGetMicrosoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code. feeds with a secure Chainguard endpoint that applies automated malware and greyware scanning plus customizable organization policies for C#, F#, and Visual Basic dependencies.
   • Introduces Chainguard Harness (Beta), an AI-powered engine that finds exploitable runtime vulnerabilities — including logic flaws, injection, and resource exhaustion — and returns engineer-reviewed fixes without requiring customer access to frontier models.

   +3 more show less

   • Introduces Chainguard Checks (Beta), replacing standard CI runners with hardened microVMs that secure credentials and enforce egress policies by default, usable before code submission so pull requests pass on the first try.
   • Introduces Chainguard Workspaces (Beta), giving each AI coding agent an isolated, hardened microVM with no access to developer credentials, preventing prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools. and credential exposure from agents running on developer machines.
   • Adds 45 new container images this week, including crossplane-function-kcl, crossplane-gcp-bigquery, crossplane-gcp-cloudfunctions, crossplane-gcp-cloudrun, crossplane-gcp-cloudscheduler, crossplane-gcp-datastream, crossplane-gcp-secretmanager, crossplane-azuread, crossplane-provider-nop, multiple openstack-* variants, logstash-fips, mountpoint-s3-csi-driver-fips, opentelemetry-dotnet-instrumentation, commercial-nginx-ingress-plus-fips, openscap-fips, nemo-gym, nemo-skills, and others — many with FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants.

   8 details in Everything

   └──▷ BREAKING ON UPGRADE

   • !After December 15, 2026, Chainguard will sign artifacts with Sigstore v3 format only; Cosign v2 or v3.1.0 and earlier cannot verify artifacts published after that date — upgrade to Cosign v3.1.1 or later before that deadline.
   • !Custom verification tooling built against the Cosign v2 libraries will break because the Cosign library API changed in v3 — review and update against the v3 libraries.
   • !Registries that do not support the OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. 1.1 Referrers API may fail to copy Sigstore v3 signatures when mirroring Chainguard artifacts after December 15, 2026 — confirm registry support before the cutover.
9. v1 Oct 15, 2026 · issue 109

   API surface changed: 15 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: 15 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • ~ GET /iam/v1/externalGroupRoleMappings: response schema changed
   • ~ GET /iam/v1/externalGroupRoleMappings/{id}: response schema changed
   • ~ GET /iam/v1/groups:checkEligibility: response schema changed
   • ~ GET /iam/v2/externalGroupRoleMappings: response schema changed
   • ~ GET /iam/v2/externalGroupRoleMappings/{uid}: response schema changed
   • ~ GET /iam/v2/groups:checkEligibility: response schema changed
   • ~ GET /iam/v2/roles/{uid}: response schema changed
   • ~ GET /registry/v1/entitlements/{parent}/catalog-images: param includeDeleted (query) added; response schema changed
   • ~ GET /registry/v1/entitlements/{parent}/images: param includeDeleted (query) added; response schema changed
   • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
   • ~ POST /iam/v1/externalGroupRoleMappings/{id}: request body changed; response schema changed
   • ~ POST /iam/v1/externalGroupRoleMappings:batchDelete: response schema changed
   • ~ POST /iam/v2/externalGroupRoleMappings/{uid}: request body changed; response schema changed
   • ~ POST /iam/v2/externalGroupRoleMappings:batchDelete: response schema changed
   • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
   • GET /registry/v1/entitlements/{parent}/catalog-images: param includeDeleted (query) added⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • GET /registry/v1/entitlements/{parent}/images: param includeDeleted (query) added

   2 details in Everything

10. docs update Oct 14, 2026 · issue 108

    Chainguard adds chainctl skills verify and --verify flag to confirm SigstoreSigstoreAn open-source project maintained by the Linux Foundation that provides free signing, verification, and transparency infrastructure for software artifacts, letting cyber tools prove code provenance without managing private keys.-signed agent skill provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build. before install or pull.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Verify a public skill by tag before deciding to install it — resolves to a pinned digest so you know exactly what you verified.
    copy

    $ chainctl skills verify skills.cgr.dev/public/github.com/github/awesome-copilot/game-engine:latest -o json

    Install a skill only after confirming Chainguard's signature on the exact fetched digest — exits nonzero and writes nothing if verification fails.
    copy

    $ chainctl skills install --verify skills.cgr.dev/public/github.com/github/awesome-copilot/game-engine:latest

    Look up your organization's SKILLS identity UIDP so you can pass it to cosign verify for independent signature verification.
    copy

    $ chainctl iam account-associations describe your-organization --chainguard -o json \
      | jq -r '.[0].chainguard.service_bindings.SKILLS'

    • Adds chainctl skills verify subcommand to confirm a Chainguard-signed agent skill's Sigstore bundle against the owning organization's SKILLS identity, accepting a tag or digest reference and outputting results in table or JSON (-o json) format.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds --verify flag to chainctl skills pull and chainctl skills install to check the skill's signature on the exact fetched digest before writing any files or symlinks to disk; a non-verified result exits nonzero and writes nothing.
    • Adds --allow-unverifiable-host flag alongside --verify to accept skills from staging or development registries (not skills.cgr.dev) with a warning rather than a hard failure.
    • Supports verifying skills from a private organization registry with Cosign using chainctl auth configure-docker and cosign verify --certificate-oidc-issuer=https://issuer.enforce.dev --certificate-identity=https://issuer.enforce.dev/<skills-identity-uidp>.
    • Adds a verification field to the JSON output of chainctl skills pull and chainctl skills install when --verify and -o json are combined, embeddingembeddingLists of numbers a model produces to represent the meaning of text, images or code, so similar items sit close together. They power semantic search and RAG. the same result as chainctl skills verify -o json.

    +1 more show less

    • Exposes the organization SKILLS identity UIDP via chainctl iam account-associations describe <org> --chainguard -o json | jq -r '.[0].chainguard.service_bindings.SKILLS' to support manual Cosign verification workflows.

    6 details in Everything

11. docs update Oct 14, 2026 · issue 108

    Chainguard: Adds chainctl skills verify "$HARDENED_REF" to check that Chainguard signed a hardened agent skill result for your organization.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Verify a hardened skill signature before pulling it locally, so nothing is downloaded unless Chainguard's signature checks out.
    copy

    $ chainctl skills pull --verify "$HARDENED_REF" ./harden-demo-reviewed

    Confirm a hardened skill is signed by Chainguard for your org before committing to an install in your environment.
    copy

    $ chainctl skills verify "$HARDENED_REF"

12. docs update Oct 14, 2026 · issue 108
    └──▷ TRY IT
    Verify a published agent skill's Chainguard signature before trusting it in a pipeline.
    copy

    $ chainctl skills verify skills.cgr.dev/public/github.com/github/awesome-copilot/game-engine:latest

    Pull an agent skill only if its signature verifies — safe for use in automated or CI environments.
    copy

    $ chainctl skills pull --verify skills.cgr.dev/public/github.com/github/awesome-copilot/game-engine:latest ./game-engine

13. docs update Oct 14, 2026 · issue 108

    Chainguard: Verifying a skill requires the groups.list capability, available through the built-in editor, viewer, limited_owner, or console_viewer roles.

    └──▷ TRY IT
    Confirm Chainguard signed an agent skill before trusting it in your organization's registry.
    copy

    $ chainctl skills verify "$HARDENED_REF"

    Install an agent skill only if its signature verifies — block installation of tampered or unsigned skills in a pipeline.
    copy

    $ chainctl skills install --verify "$HARDENED_REF"

14. Week of 2026-10-12 Oct 12, 2026 · issue 108

    Chainguard Actions and Compliance Dashboard hit GA; Guardener AI migration agent launches in Early Access with 17 new images added.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Launches Chainguard Actions (GA) with 1,000+ continuously hardened, drop-in replacements for GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure., including pinning of transitive action dependencies and a Hardening.md report per action listing removed vulnerabilities.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds self-serve action requests via Chainguard Actions with a one-business-day SLASLAA formal agreement between a service provider and customer that defines expected uptime, response times, and remedies for failures, giving cyber tools a contractual baseline for availability and support commitments. and automated migration through the Chainguard App or migration skill.
    • Launches the Chainguard Compliance Dashboard (GA) in the Chainguard Console, providing a centralized view of container compliance, vulnerability posture, and audit-ready reporting with continuously logged image attestations and real-time CVE status.
    • Surfaces OpenSCAP scan results against the DISA General Purpose Operating System (GPOS) SRG and FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto. validation details on every FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. image in the Chainguard Console.
    • Adds per-architecture downloadable XCCDF reports on FIPS images in the Chainguard Console for inclusion as supporting evidence in FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one. and other audit packages.

    +2 more show less

    • Launches Guardener (Early Access), Chainguard's AI-native adoption agent, providing continuous repository scanning across Dockerfiles, Helm charts, and Kubernetes manifests with automated pull requests configured in YAML for image swaps.
    • Adds 17 new container images this week, including aws-sqs-controller, zeek, istioctl, llm-d-router-coordinator, llm-d-router-disagg-sidecar, llm-d-router-endpoint-picker, openstack-keystone-oshelm-fips, verdaccio, whereabouts-fips, openstack-barbican-oshelm, and openstack-manila-oshelm, most available in standard and FIPS variants.

    7 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The spark:3.5 container image has passed its grace period and is no longer available as of 2026-10-12.
15. docs update Oct 10, 2026 · issue 100

    Chainguard Libraries adds direct lockfile verification via chainctl libraries verify for JavaScript projects.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Verify a JavaScript project's supply chain in CI before installing any dependencies — catches issues at the lockfile stage.
    copy

    $ chainctl libraries verify package-lock.json

    • Supports verifying a JavaScript lockfile directly with chainctl libraries verify package-lock.json, without installing dependencies first.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    1 detail in Everything

16. docs update Oct 8, 2026 · issue 097
    └──▷ TRY IT
    Verify a JavaScript project's lockfile in CI before installing dependencies, to catch unvetted packages early.
    copy

    $ chainctl libraries verify package-lock.json

17. docs update Oct 8, 2026 · issue 097

    Chainguard: Adds --ttl=8760h (max one year, default 30 days) to control pull token lifetime.

    └──▷ TRY IT
    Generate a pull token for a Catalog Starter org and store credentials as CI secrets so pipelines can pull from cgr.dev without OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. federation.
    copy

    $ chainctl auth pull-token create --output=env --ttl=8760h

    Revoke a Catalog Starter pull token when chainctl iam identity delete is unavailable — find and remove its role binding instead.
    copy

    $ chainctl iam role-bindings list
    chainctl iam role-bindings delete <role-binding-id>

18. docs update Oct 6, 2026 · issue 096

    Chainguard Actions launches a 1,000+ hardened action catalog with Guardener bot, SLSASLSASupply-chain Levels for Software Artifacts, a framework for assessing how software was built and protecting that process from tampering. Provenance records help verify where a build came from. attestations, and chainctl actions discover for full dependency scanning.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Discover all actions and container images — including transitive dependencies — used across a repository to audit your full supply chain exposure.
    copy

    $ chainctl actions discover $GIT_ORGANIZATION/$REPO --recursive

    Enable Guardener automated migration PRs for a repository so Chainguard hardened equivalents are swapped in without manual effort.
    .chainguard/actions.yaml copy

    enabled: true
    migrate:
      enabled: true

    Link your Chainguard organization to GitHub so Guardener can inventory and protect workflows across every accessible repository.
    copy

    $ chainctl guardener github link

    • Adds chainctl guardener github link to link a Chainguard organization to a GitHub organization for Guardener bot setup.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds chainctl actions discover subcommand to scan workflows and composite actions and list all referenced actions and container images, with --recursive to follow transitive dependencies and --timeout to cap API usage.
    • Adds .chainguard/actions.yaml config file — set at the repo or org-level .github repository — with migrate.enabled: true to activate automated migration pull requests via Guardener.
    • Introduces a catalog of more than 1,000 hardened GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure., each pulled from upstream at a pinned commit, reviewed by a static ruleset and an AI-powered analysis pass, and shipped with a signed SLSA provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build. attestation.
    • Ships a static pre-pass that catches static-inline-injection (expression interpolated into a run: block), static-unsanitized-env-write, and invalid-yaml findings, each with per-occurrence location detail.

    +3 more show less

    • Adds AI-powered policy checks covering unpinned-uses, script-injection, unsafe-shell, hardcoded-credentials, github-env-injection, suspicious-run-content, and permissions / missing-permissions / broad-permissions findings.
    • Pins transitive container image dependencies to digest (image:tag@sha256:<digest>) and rewrites nested action uses: references to hardened catalog copies where available.
    • Provides the Chainguard App (beta) for GitHub organizations, which inventories actions across repositories, comments on PRs introducing unhardened actions, and opens automated migration PRs once enabled.

    8 details in Everything

19. docs update Oct 6, 2026 · issue 096

    Chainguard: Introduces Guardener feature to inventory actions across repositories and open migration pull requests to swap in hardened equivalents.

    └──▷ TRY IT
    Discover all actions and container images referenced across every workflow in a repo, following composite actions transitively, to build a full dependency inventory before migration.
    copy

    $ chainctl actions discover $GIT_ORGANIZATION/$REPO --recursive

    Enable Guardener automated migration pull requests for a repository by adding the config file — install the Chainguard App and run chainctl guardener github link first.
    .chainguard/actions.yaml copy

    enabled: true
    migrate:
      enabled: true

20. docs update Oct 6, 2026 · issue 096

    Chainguard Libraries adds direct lockfile verification for JavaScript via chainctl libraries verify⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Verify a JavaScript lockfile in CI before installing dependencies, catching supply-chain issues early in the pipeline.
    copy

    $ chainctl libraries verify package-lock.json

    • Adds support for verifying JavaScript lockfiles directly with chainctl libraries verify package-lock.json, without requiring dependencies to be installed first.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    1 detail in Everything

21. docs update Oct 6, 2026 · issue 096

    Catalog Starter orgs can now authenticate CI pipelines via pull tokens using chainctl auth pull-token create --output=env.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Authenticate a GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. CI pipeline to cgr.dev when your org cannot create assumable identities.
    copy

    $ chainctl auth pull-token create --output=env

    Create a pull token with a custom lifetime (up to one year) to reduce rotation frequency in long-running pipelines.
    copy

    $ chainctl auth pull-token create --output=env --ttl=8760h

    Revoke a Catalog Starter pull token when role-binding deletion is the only available path.
    copy

    $ chainctl iam role-bindings list
    chainctl iam role-bindings delete <role-binding-id>

    • Adds chainctl auth pull-token create --output=env to generate pull-token credentials for CI pipelines in Catalog Starter organizations, setting CHAINGUARD_IDENTITY_ID and CHAINGUARD_TOKEN environment variables for use as registry secrets.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Pull tokens support a configurable lifetime via --ttl (default 30 days, maximum --ttl=8760h for one year) before requiring rotation.
    • Revoke a pull token by running chainctl iam role-bindings list to find its binding, then chainctl iam role-bindings delete <role-binding-id> — because chainctl iam identity delete is unavailable in Catalog Starter.
    • Documents that setup-chainctl GitHub Action and OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. federation (GitLab, CircleCI, Buildkite, Jenkins, Kubernetes) are unsupported for Catalog Starter organizations, which must use pull tokens instead.

    4 details in Everything

22. changelog Oct 5, 2026 · issue 095

    FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto. validated OpenSSL v3.6 provider with post-quantumpost-quantumCryptography designed to stay secure against a large quantum computer, which could break today's RSA and elliptic-curve keys. NIST standardized the first algorithms in 2024 as ML-KEM, ML-DSA and SLH-DSA. algorithms (ML-KEMML-KEMNIST's post-quantum key-exchange standard (FIPS 203), formerly Kyber. Two parties use it to agree on a shared secret, usually alongside X25519 in a hybrid TLS handshake., ML-DSAML-DSANIST's main post-quantum digital signature standard (FIPS 204), formerly Dilithium. It is the planned replacement for RSA and ECDSA signatures on certificates and code., SLH-DSASLH-DSANIST's hash-based post-quantum signature standard (FIPS 205), formerly SPHINCS+. Its security rests only on hash functions, so it is slower and larger than ML-DSA but a conservative backup.); Go and .NET Libraries invite-only beta; tag-based Custom Assembly via Terraform and chainctl.

    • Achieves FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. 140-3 validation (Certificate #5523) for the Chainguard FIPS Provider for OpenSSL v3.6, including hybrid post-quantum key exchangepost-quantum key exchangeA cryptographic handshake algorithm designed to resist attacks from quantum computers, using math problems like lattices that quantum algorithms cannot efficiently solve, letting tools stay secure against future quantum-capable adversaries. for TLS via ML-KEM paired with classical key exchange, and standardized post-quantum algorithms ML-KEM, ML-DSA, and SLH-DSA alongside classical FIPS algorithms AES, SHA-2, SHA-3, ECDSAECDSAThe elliptic-curve signature algorithm behind most TLS certificates, blockchains and many hardware keys. It is one of the algorithms post-quantum signatures are meant to replace., and RSARSAThe oldest widely used public-key algorithm, for both encryption and signatures, with security resting on factoring large numbers. A large quantum computer would break it..
    • New supported platformChainguard FIPS container images can opt in to the validated OpenSSL v3.6 module starting October 1, 2026; note that SHA-1SHA-1A cryptographic hash function standardized by NIST that produces a 160-bit digest; tools use it for file integrity checks, though it is now considered cryptographically broken and unsuitable for collision-resistant applications. is not an approved algorithm in v3.6.
    • Adds Go and .NET ecosystem support to Chainguard Libraries through an invite-only beta, letting organizations pull Go and .NET packages and evaluate them in existing development workflows.
    • Adds tag-based Custom Assembly management via the Chainguard Terraform provider, enabling creation of overlays and binding them to specific tags of a Custom Assembly repository.
    • Adds tag-based Custom Assembly management via chainctl, enabling creation of overlays and binding them to specific tags of a Custom Assembly repository.

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !SHA-1 is not an approved algorithm in the OpenSSL v3.6 FIPS module — workloads using SHA-1 will break if you opt FIPS container images in to the v3.6 module.
23. Week of 2026-10-05 Oct 5, 2026 · issue 096

    Athena coalition publishes first 14 silent Java CVE disclosures; Chainguard ships 37 new container images including crossplane-azure and openstack variants.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds advisories for 14 silent Java vulnerabilities (1 critical, 1 high, 8 medium, 4 low) to the Chainguard Libraries VEXVEXA machine-readable statement from a vendor saying whether a CVE in a component actually affects their product. It is how a scanner is told to stop flagging a vulnerability that is not reachable. feed, so scanners integrating with Chainguard Libraries now surface these previously uncategorized bugs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Provides remediated artifact versions in Chainguard Repository with a -0.cgr.N suffix for Chainguard Libraries customers, adoptable by updating a lockfile entry.
    • Adds 8 new crossplane-azure-* and crossplane-aws-* container images (including FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants): crossplane-azure-compute, crossplane-azure-containerservice, crossplane-azure-eventhub, crossplane-azure-network, crossplane-azure-operationalinsights, crossplane-aws-s3vectors, crossplane-azure-cognitiveservices, and crossplane-function-extra-resources.
    • Adds 10 new openstack-* container images: openstack-ceph-config-helper, openstack-cinder-oshelm, openstack-client-oshelm, openstack-glance-oshelm, openstack-keystone-oshelm, openstack-neutron-oshelm, openstack-nova-oshelm, openstack-octavia-oshelm, openstack-placement-oshelm, and openstack-libvirt-oshelm.
    • Adds new images longhorn-engine-fips, ray-fips, elasticsearch-iamguarded-fips as FIPS-tier container images.

    +3 more show less

    • Adds nemo-rl (AI tier), kserve-llmisvc-controller (AI + FIPS), and aws-lambda-provided (application + FIPS) container images.
    • Adds commercial-kyverno-cli and commercial-kyverno-readiness-checker to the commercial image tier.
    • Adds playwright-chromium, pmm-server, datadog-serverless-init, floci, and livekit-sip container images.

    8 details in Everything

24. changelog Oct 4, 2026 · issue 094

    Chainguard FIPS Provider for OpenSSL v3.6 achieves FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto. validation with post-quantumpost-quantumCryptography designed to stay secure against a large quantum computer, which could break today's RSA and elliptic-curve keys. NIST standardized the first algorithms in 2024 as ML-KEM, ML-DSA and SLH-DSA. ML-KEMML-KEMNIST's post-quantum key-exchange standard (FIPS 203), formerly Kyber. Two parties use it to agree on a shared secret, usually alongside X25519 in a hybrid TLS handshake., ML-DSAML-DSANIST's main post-quantum digital signature standard (FIPS 204), formerly Dilithium. It is the planned replacement for RSA and ECDSA signatures on certificates and code., and SLH-DSASLH-DSANIST's hash-based post-quantum signature standard (FIPS 205), formerly SPHINCS+. Its security rests only on hash functions, so it is slower and larger than ML-DSA but a conservative backup.; Go and .NET Libraries enter invite-only beta.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Supports hybrid post-quantum key exchangepost-quantum key exchangeA cryptographic handshake algorithm designed to resist attacks from quantum computers, using math problems like lattices that quantum algorithms cannot efficiently solve, letting tools stay secure against future quantum-capable adversaries. for TLS pairing classical key exchange with ML-KEM as an approved FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. service under the newly FIPS 140-3-validated Chainguard FIPS Provider for OpenSSL v3.6 (Certificate #5523).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Includes standardized post-quantum algorithms ML-KEM, ML-DSA, and SLH-DSA alongside classical FIPS algorithms AES, SHA-2, SHA-3, ECDSAECDSAThe elliptic-curve signature algorithm behind most TLS certificates, blockchains and many hardware keys. It is one of the algorithms post-quantum signatures are meant to replace., and RSARSAThe oldest widely used public-key algorithm, for both encryption and signatures, with security resting on factoring large numbers. A large quantum computer would break it. in the validated module.
    • Chainguard FIPS container images can opt in to the v3.6 module starting October 1, 2026; note that SHA-1SHA-1A cryptographic hash function standardized by NIST that produces a 160-bit digest; tools use it for file integrity checks, though it is now considered cryptographically broken and unsuitable for collision-resistant applications. is not an approved algorithm in v3.6.
    • Extends Chainguard Libraries to Go and .NET ecosystems through an invite-only beta, letting accepted organizations pull Go and .NET packages and evaluate them in existing development workflows.
    • Adds 19 new container images this week, including both standard and FIPS variants, among them mcp-grafana-fips, kubernetes-pause-fips, chainguard-server-hypervisor-gcp, argocd-agent, victoriatraces, vault-secrets-webhook, ray, foundry, conftest, kured, keepalived, nix, and kates.

    +1 more show less

    • Adds guides for managing tag-based Custom Assembly with the Chainguard Terraform provider and with chainctl, covering overlays and binding them to specific tags of a Custom Assembly repository.
    • Supports hybrid post-quantum key exchangepost-quantum key exchangeA cryptographic handshake algorithm designed to resist attacks from quantum computers, using math problems like lattices that quantum algorithms cannot efficiently solve, letting tools stay secure against future quantum-capable adversaries. for TLS pairing classical key exchange with ML-KEM as an approved FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. service under the newly FIPS 140-3-validated Chainguard FIPS Provider for OpenSSL v3.6 (Certificate #5523).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Extends Chainguard Libraries to Go and .NET ecosystems through an invite-only beta, letting accepted organizations pull Go and .NET packages and evaluate them in existing development workflows.
    • Adds 19 new container images this week, including both standard and FIPS variants, among them mcp-grafana-fips, kubernetes-pause-fips, chainguard-server-hypervisor-gcp, argocd-agent, victoriatraces, vault-secrets-webhook, ray, foundry, conftest, kured, keepalived, nix, and kates.
    • Adds guides for managing tag-based Custom Assembly with the Chainguard Terraform provider and with chainctl, covering overlays and binding them to specific tags of a Custom Assembly repository.

    2 more in Everything

    └──▷ BREAKING ON UPGRADE

    • !SHA-1 is not an approved algorithm in the v3.6 FIPS module; workloads using SHA-1 will break if they opt in to the OpenSSL v3.6 module.
25. v1 Oct 3, 2026 · issue 093

    API surface changed: +1 endpoint, 9 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: +1 endpoint, 9 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + GET /vulnerabilities/v1/advisory_events
    • ~ GET /iam/v2/identities: response schema changed
    • ~ GET /iam/v2/identities/{uid}: response schema changed
    • ~ GET /iam/v2/roles/{uid}: response schema changed
    • ~ GET /sts/exchange: param delegated (query) added; param task (query) added
    • ~ PATCH /iam/v2/identities/{uid}: request body changed; response schema changed
    • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/identities/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /sts/exchange: param delegated (query) added; param task (query) added
    • New endpoint GET /vulnerabilities/v1/advisory_events⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • GET /sts/exchange: param delegated (query) added; param task (query) added
    • POST /sts/exchange: param delegated (query) added; param task (query) added

    3 details in Everything

26. v1 Sep 29, 2026 · issue 089

    API surface changed: +1 endpoint, 14 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: +1 endpoint, 14 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + DELETE /vulnerabilities/v1/advisory_events/{id}
    • ~ GET /iam/v2/roles/{uid}: response schema changed
    • ~ GET /libraries/v1/artifacts/count: response schema changed
    • ~ GET /libraries/v1/aws-marketplace-subscriptions/{id}: response schema changed
    • ~ GET /libraries/v1/resolutioncache/{parentId}/entries: response schema changed
    • ~ GET /libraries/v1/resolutioncache/{parentId}/status: response schema changed
    • ~ GET /vulnerabilities/v1/advisories: param createdBeforeTime (query) added; param createdSinceTime (query) added; param eventCreatedBeforeTime (query) added; param eventCreatedSinceTime (query) added
    • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ PATCH /libraries/v1/aws-marketplace-subscriptions/{id}: request body changed; response schema changed
    • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /libraries/v1/aws-marketplace-subscriptions/{id}: request body changed; response schema changed
    • ~ POST /libraries/v1/aws-marketplace-subscriptions/{id}:cancel: response schema changed
    • ~ POST /libraries/v1/entitlements/{id}: request body changed
    • ~ POST /libraries/v1/resolutioncache/{parentId}:optout: response schema changed
    • ~ POST /libraries/v1/resolutioncache/{parentId}:zap: response schema changed
    • New endpoint DELETE /vulnerabilities/v1/advisory_events/{id}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • GET /vulnerabilities/v1/advisories: param createdBeforeTime (query) added; param createdSinceTime (query) added; param eventCreatedBeforeTime (query) added; param eventCreatedSinceTime (query) added

    2 details in Everything

27. docs update Sep 29, 2026 · issue 089

    Chainguard Agent Skills CLI gains --dry-run, --copy, --yes, --tag, and --parent/--group flags for publishing and installing skills⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Validate a skill artifact locally before publishing — useful in PR CI to catch build errors without creating a registry entry.
    copy

    $ chainctl skills publish --tag v1.0.0 --dry-run

    Publish the same skill artifact under both a pinned version tag and latest so consumers can reference either.
    copy

    $ chainctl skills publish --tag v1.0.0 --tag latest

    • Adds --dry-run flag to the skills publish command to build and validate an artifact without publishing it.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds --tag flag (repeatable) to publish a skill under one or more explicit tags, e.g. --tag v1.0.0 --tag latest; omitting --tag publishes as a default and warns that no version was pinned.
    • Adds --copy flag to the skills install command to give each agent its own copy of a skill, rather than the default shared symlink under .agents/skills/.
    • Adds --yes flag to non-interactively accept the Agent Skills Terms of Service and Data Privacy Agreement in CI environments where no interactive terminal is available.
    • Adds --parent flag to entitlements subcommands and --group flag to other skills subcommands to target a specific organization.

    +3 more show less

    • Deleting a skill's last remaining version now also removes the empty skill entry automatically, preventing stale entries in listing output.
    • Adds support for passing a tag-less reference (e.g. "$HARDENED_REPO") to skill uninstall, but only when no versions remain; skills with existing versions require an explicit tag.
    • Requires chainctl v0.2.364 or later for Agent Skills functionality.
    • Adds --dry-run flag to the skills publish command to build and validate an artifact without publishing it.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds --tag flag (repeatable) to publish a skill under one or more explicit tags, e.g. --tag v1.0.0 --tag latest; omitting --tag publishes as a default and warns that no version was pinned.
    • Adds --copy flag to the skills install command to give each agent its own copy of a skill, rather than the default shared symlink under .agents/skills/.
    • Adds --yes flag to non-interactively accept the Agent Skills Terms of Service and Data Privacy Agreement in CI environments where no interactive terminal is available.
    • Adds --parent flag to entitlements subcommands and --group flag to other skills subcommands to target a specific organization.

    +2 more show less

    • Adds support for passing a tag-less reference (e.g. "$HARDENED_REPO") to skill uninstall, but only when no versions remain; skills with existing versions require an explicit tag.
    • Requires chainctl v0.2.364 or later for Agent Skills functionality.

    1 more in Everything

28. Week of 2026-09-28 Sep 28, 2026 · issue 089

    Chainguard gains FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto. validation with post-quantumpost-quantumCryptography designed to stay secure against a large quantum computer, which could break today's RSA and elliptic-curve keys. NIST standardized the first algorithms in 2024 as ML-KEM, ML-DSA and SLH-DSA. algorithms, Libraries beta for Go and .NET, and 19 new container images.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Adds FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. 140-3 validated Chainguard FIPS Provider for OpenSSL v3.6 (Certificate #5523), including hybrid post-quantum TLS key exchange via ML-KEMML-KEMNIST's post-quantum key-exchange standard (FIPS 203), formerly Kyber. Two parties use it to agree on a shared secret, usually alongside X25519 in a hybrid TLS handshake. paired with classical algorithms, plus standalone ML-KEM, ML-DSAML-DSANIST's main post-quantum digital signature standard (FIPS 204), formerly Dilithium. It is the planned replacement for RSA and ECDSA signatures on certificates and code., and SLH-DSASLH-DSANIST's hash-based post-quantum signature standard (FIPS 205), formerly SPHINCS+. Its security rests only on hash functions, so it is slower and larger than ML-DSA but a conservative backup. support alongside AES, SHA-2, SHA-3, ECDSAECDSAThe elliptic-curve signature algorithm behind most TLS certificates, blockchains and many hardware keys. It is one of the algorithms post-quantum signatures are meant to replace., and RSA; opt-in available for Chainguard FIPS container images starting October 1, 2026.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Launches Chainguard Libraries for Go and .NET ecosystems in an invite-only beta, letting accepted organizations pull Go and .NET packages from Chainguard Libraries into existing development workflows.
    • Adds 19 new container images this week, including chainguard-server-hypervisor-gcp, kured (+fips), conftest (+fips), foundry, keepalived (+fips), mcp-grafana-fips, nix, ray, vault-secrets-webhook (+fips), argocd-agent, kates (+fips), kubernetes-pause-fips, and victoriatraces (+fips).

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !SHA-1SHA-1A cryptographic hash function standardized by NIST that produces a 160-bit digest; tools use it for file integrity checks, though it is now considered cryptographically broken and unsuitable for collision-resistant applications. is not an approved algorithm in the OpenSSL v3.6 FIPS module — workloads relying on SHA-1 will break if they opt in to the v3.6 module on or after October 1, 2026.
29. changelog Sep 26, 2026 · issue 086

    Chainguard adds EU Sovereign Artifacts beta, Guardener now covers GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure., and 26+ new container images.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ USE IT
    Temporarily restore the old sonar-scanner-cli default-user behavior in Kubernetes after the October 12 breaking change takes effect.
    yaml copy

    securityContext:
      runAsUser: 0

    Redirect the Sonar scanner scratch directory to the old workspace path so pipelines reading report-task.txt continue to work without switching to root.
    copy

    $ docker run --rm \
      -v $(pwd):/usr/src \
      cgr.dev/chainguard/sonar-scanner-cli \
      -Dsonar.working.directory=/usr/src/.scannerwork

    • Guardener automated migration tool now covers GitHub Actions in addition to container images, inventorying Actions across an organization's repositories, mapping them to hardened Chainguard equivalents, and opening pull requests pinned to a specific SHA rather than a mutable tag.
    • Guardener runs in two modes: an upfront pass that surfaces existing Actions usage and opens migration pull requests, and ongoing standardization that watches workflow files and suggests Chainguard equivalents as new upstream Actions appear.
    • Adds tutorial for pulling packages from Chainguard package repositories through Sonatype Nexus as pull-through caches for apk packages.
    • Adds tutorial for pulling packages from Chainguard package repositories through Sonatype Nexus as pull-through caches for apk packages.

    2 more in Everything

30. docs update Sep 26, 2026 · issue 086

    Chainguard: Adds chainctl skills describe and chainctl skills pull support for full hardened artifact references including the user-namespace path (skills.cgr.dev/<org-uidp>/users/<user-namespace>/<skill>@sha256:<digest>).

    └──▷ TRY IT
    Submit a local skill for hardening in CI and capture the job ID so the pipeline can check status asynchronously without blocking on completion.
    copy

    $ JOB_ID=$(chainctl skills harden ./harden-demo --group your-organization -o id)
    chainctl skills status --group your-organization --id "$JOB_ID" --wait --timeout 30m

    Harden a previously pushed artifact by digest to ensure you target an exact, immutable version rather than a mutable tag.
    copy

    $ chainctl skills harden --group your-organization --name harden-demo \
      --digest 'sha256:<64-hex-digest-from-push>' --wait --timeout 30m

    List all hardened and uploaded skills across both registries to confirm a job result is available before installing.
    copy

    $ chainctl skills list --group your-organization --source all --recursive

    • Hardened skill downloads include a HARDENING.md report alongside SKILL.md in the ./hardened/<skill-name>/ output directory, summarizing changes and open scanner findings.
    • Hardening jobs are deduplicated server-side: submitting the same organization, user, skill name, and content digest returns the existing job ID rather than creating a new one.
    • Uploads target uploads.cgr.dev by default in production; no registry environment variable is required.
    • Chainguard Agent Skills is available as a beta service requiring a Skills entitlement and accepted Skills terms on the organization.

    4 details in Everything

31. docs update Sep 26, 2026 · issue 086
    └──▷ TRY IT
    Upload an agent skill and submit it for hardening so the secured version is published to your org-scoped registry.
    copy

    $ chainctl skills harden

32. docs update Sep 26, 2026 · issue 086

    Chainguard: Adds chainctl skills harden to submit uploaded agent skills for hardening and track jobs through to completion.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Upload an agent skill artifact and submit it for hardening, then track the job until the hardened image is available in your org registry.
    copy

    $ chainctl skills harden uploads.cgr.dev/<your-org>/<skill>

    • Supports uploading original skills to uploads.cgr.dev/<your-org>/<skill> before hardening.
    • Publishes hardened skill results under skills.cgr.dev/<org-uidp>/users/<user-namespace>/<skill>, namespaced to the uploading user within the org.

    2 details in Everything

33. changelog Sep 25, 2026 · issue 085

    Chainguard adds EU data-residency beta for Containers and Libraries, plus 26+ new container images including FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Temporarily restore the previous sonar-scanner-cli non-root behavior after the October 12 default-user change, while you migrate pipelines to read report-task.txt from /tmp/.scannerwork.
    copy

    $ docker run --user 0 cgr.dev/chainguard/sonar-scanner-cli

    Migrate a Kubernetes deployment of sonar-scanner-cli to read scanner output from the new /tmp/.scannerwork path, or explicitly preserve the old path by setting the working directory flag.
    copy

    $ docker run cgr.dev/chainguard/sonar-scanner-cli -Dsonar.working.directory=<project>/.scannerwork

    • Launches Sovereign Artifacts beta for enrolled customers, storing Chainguard Containers and Libraries artifact bytes in an EU region with automatic backfill of existing artifacts and ~30% faster pulls from Europe.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds openjdk:26 container image (released 2026-09-17, EOL 2027-03-17).
    • Adds ceph:19 container image (released 2026-09-19, EOL 2027-03-19).
    • Adds kuma:2.12 container image (released 2026-09-09, EOL 2027-03-09).

    4 details in Everything

34. docs update Sep 25, 2026 · issue 085

    Chainguard adds chainctl skills harden and chainctl skills status for server-side agent skill hardening with job tracking⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Harden a local skill directory and wait for the server-side result in one step — ideal for CI pipelines where you want to block until the hardened artifact and HARDENING.md report are ready.
    copy

    $ chainctl skills harden ./harden-demo --group your-organization --wait --timeout 30m

    Submit a hardening job from CI without blocking, then check progress later using the captured job ID.
    copy

    $ JOB_ID=$(chainctl skills harden ./harden-demo --group your-organization -o id)
    chainctl skills status --group your-organization --id "$JOB_ID" --wait --timeout 30m

    List all hardened skills across every user namespace in your organization, including version-tagged and digest-only artifacts, to find a completed hardening result.
    copy

    $ chainctl skills list --group your-organization --source skills --recursive

    • Adds chainctl skills harden command to upload a local agent skill directory or existing uploads-registry artifact, submit it for server-side hardening, and download the result with a HARDENING.md report.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds chainctl skills status command with --id, --wait, and --timeout flags to track a hardening job and resume waiting for its result using the 64-character job ID.
    • Adds --folder, --digest, --wait, and --timeout flags to chainctl skills harden, supporting four input forms: positional path, --folder, an uploads.cgr.dev reference, or --digest with --name.
    • Adds --digest and --name flags to chainctl skills harden to target an exact artifact by digest instead of tag or path.
    • Adds -o id output flag to chainctl skills harden to capture and return only the job ID for deferred status checks.

    +9 more show less

    • Adds --recursive (-r) flag to chainctl skills list to traverse nested user-namespace folders and show all hardened skills with full paths in the NAME column.
    • Adds --source flag to chainctl skills list with values skills (hardened registry at skills.cgr.dev), uploads (original uploads at uploads.cgr.dev), and all (both registries labeled by source).
    • Adds chainctl skills entitlements create and chainctl skills accept-terms commands to enable the Agent Skills service for an organization.
    • Adds chainctl skills entitlements list to check whether an organization already has a Skills entitlement.
    • Hardened artifacts are published under a per-user namespace at skills.cgr.dev/<org-uidp>/users/<user-namespace>/<skill-name>@sha256:<digest>, isolating results across submitters.
    • Adds chainctl skills describe to inspect a full artifact reference (upload or hardened) by its registry path.
    • Adds chainctl skills pull to download a hardened artifact by its exact reference into a specified local directory.
    • Adds chainctl skills install to detect local agents and deploy a hardened skill, reporting placement location.
    • Adds chainctl skills validate to check a skill directory's structure locally before submitting for hardening.
    • Adds chainctl skills harden command to upload a local agent skill directory or existing uploads-registry artifact, submit it for server-side hardening, and download the result with a HARDENING.md report.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds chainctl skills status command with --id, --wait, and --timeout flags to track a hardening job and resume waiting for its result using the 64-character job ID.
    • Adds --folder, --digest, --wait, and --timeout flags to chainctl skills harden, supporting four input forms: positional path, --folder, an uploads.cgr.dev reference, or --digest with --name.
    • Adds --digest and --name flags to chainctl skills harden to target an exact artifact by digest instead of tag or path.
    • Adds -o id output flag to chainctl skills harden to capture and return only the job ID for deferred status checks.

    +7 more show less

    • Adds chainctl skills entitlements create and chainctl skills accept-terms commands to enable the Agent Skills service for an organization.
    • Adds chainctl skills entitlements list to check whether an organization already has a Skills entitlement.
    • Hardened artifacts are published under a per-user namespace at skills.cgr.dev/<org-uidp>/users/<user-namespace>/<skill-name>@sha256:<digest>, isolating results across submitters.
    • Adds chainctl skills describe to inspect a full artifact reference (upload or hardened) by its registry path.
    • Adds chainctl skills pull to download a hardened artifact by its exact reference into a specified local directory.
    • Adds chainctl skills install to detect local agents and deploy a hardened skill, reporting placement location.
    • Adds chainctl skills validate to check a skill directory's structure locally before submitting for hardening.

    2 more in Everything

35. docs update Sep 25, 2026 · issue 085

    Chainguard: Adds chainctl skills accept-terms --group <org> to accept terms before using the registry.

    └──▷ TRY IT
    Upload a local agent skill, submit it for hardening, and wait up to 30 minutes for a signed, hardened result — the typical first-time workflow for a new org skill.
    copy

    $ chainctl skills entitlements create --parent your-organization
    chainctl skills accept-terms --group your-organization
    chainctl skills push hello-world --group your-organization --tag v1.0.0
    chainctl skills harden uploads.cgr.dev/your-organization/hello-world:v1.0.0 \
      --group your-organization --wait --timeout 30m

    Browse all hardened skills across user-namespace folders, then install and invoke a specific hardened result in Claude Code.
    copy

    $ chainctl skills list --group your-organization --source skills --recursive
    export HARDENED_REF='skills.cgr.dev/<org-uidp>/users/<user-namespace>/hello-world@sha256:<digest>'
    chainctl skills install "$HARDENED_REF"
    export INSTALLED_SKILL='<install-name-from-describe>'

    Remove a specific published version from the hardened registry after listing its available tags.
    copy

    $ HARDENED_REPO="${HARDENED_REF%@*}"
    chainctl skills versions "$HARDENED_REPO"
    export HARDENED_TAG='<tag-from-the-versions-output>'
    chainctl skills delete "$HARDENED_REPO:$HARDENED_TAG"

    • Adds chainctl skills push <name> --group <org> --tag <version> to upload agent skills to uploads.cgr.dev.
    • Adds chainctl skills harden <ref> --group <org> --wait --timeout 30m to submit an uploaded skill for hardening and download results to ./hardened/<name>/, including a HARDENING.md findings report.
    • Adds chainctl skills status --group <org> --id <job-id> to check the status of an in-progress hardening job.
    • Adds chainctl skills describe <hardened-ref> to inspect a hardened skill's details and retrieve its install name.
    • Adds chainctl skills uninstall <install-name> to remove an installed skill from the local machine.

    +3 more show less

    • Adds chainctl skills versions <hardened-repo> to list available tags for a published hardened skill.
    • Adds chainctl skills delete <hardened-repo>:<tag> to remove a specific published version from the hardened registry.
    • Introduces the Chainguard Skills Registry, a new hosted service for publishing, hardening, and distributing agent skills scoped to an organization via uploads.cgr.dev and skills.cgr.dev.

    8 details in Everything

36. docs update Sep 25, 2026 · issue 085

    Chainguard adds skill hardening pipeline: upload to uploads.cgr.dev, submit with chainctl, and serve from skills.cgr.dev.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Upload an agent skill and submit it for hardening so the secured version is published to your org-scoped registry path.
    copy

    $ chainctl skills harden

    • Introduces a skill hardening pipeline: upload original skills to uploads.cgr.dev/<your-org>/<skill>, submit with chainctl skills harden, and receive hardened results published under skills.cgr.dev/<org-uidp>/users/<user-namespace>/<skill> scoped to your organization.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Serves hardened agent skills from both public and private registries at skills.cgr.dev/<your-org>/.

    2 details in Everything

37. docs update Sep 25, 2026 · issue 085

    Chainguard: Supports uploading original skills to uploads.cgr.dev/<your-org>/<skill> before hardening, scoped to your organization.

38. changelog Sep 24, 2026 · issue 084

    Chainguard: Publishes tutorial for pulling packages from Chainguard package repositories through Sonatype Nexus raw repositories as pull-through caches for apk packages.

    └──▷ USE IT
    Restore the previous sonar-scanner-cli working-directory behavior in a Kubernetes pod spec after the October 12 default-user change.
    yaml copy

    securityContext:
      runAsUser: 0

    Override the scanner working directory via a JVMJVMThe Java Virtual Machine, a runtime maintained by Oracle (and implemented by others) that executes Java bytecode on any OS, giving cyber tools a portable, garbage-collected environment with a large ecosystem of libraries. property so report-task.txt lands in the expected project path instead of /tmp/.scannerwork.
    copy

    $ docker run --rm -v $(pwd):/usr/src cgr.dev/chainguard/sonar-scanner-cli \
      -Dsonar.working.directory=/usr/src/.scannerwork

39. changelog Sep 23, 2026 · issue 083

    Chainguard launches Sovereign Artifacts beta for EU data residency, storing container and library artifacts in-region for ~30% faster pulls.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Redirect the SonarScanner working directory to the old location so pipelines that read report-task.txt from <project>/.scannerwork continue to work after the October 12 change.
    copy

    $ docker run cgr.dev/chainguard/sonar-scanner-cli:latest sonar-scanner -Dsonar.working.directory=<project>/.scannerwork

    • Adds openjdk:26 and ceph:19 container images.
    • Adds 26 new container images this week, including clamav-prometheus-exporter, crossplane-azure-marketplaceordering, kserve-sklearnserver, commercial-spilo-fips, graphql-hive-gateway, jupyterhub-k8s-singleuser-sample, nuxeo-2025, chainguard-server-hypervisor-aws, mongodb-kubernetes, opentelemetry-python-instrumentation-fips, strimzi-kafka-fips, crossplane-aws-emrcontainers, kro, pyrra, starboard-exporter, krakend, mongodb-search, and FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants.
    • Adds cursor-agent, chainguard-desktop-workstation-pc, commercial-avocado, rustfs, cloudzero-agent, trivy-k8s-wrapper, access-log-exporter, datahub-gms, kates-connect, kubeflow-trainer-controller-manager, and tracee container images.

    3 details in Everything

40. changelog Sep 22, 2026 · issue 082
    └──▷ TRY IT
    Preserve existing sonar-scanner-cli pipeline behavior after the October 12 default-user change by explicitly redirecting the working directory back to the project workspace.
    copy

    $ docker run --rm -v "$(pwd):/usr/src" cgr.dev/chainguard/sonar-scanner-cli -Dsonar.working.directory=/usr/src/.scannerwork -Dsonar.projectBaseDir=/usr/src

41. v1 Sep 21, 2026 · issue 081

    API surface changed: 13 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: 13 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • ~ GET /iam/v2/identityProviders: response schema changed
    • ~ GET /iam/v2/identityProviders/{uid}: response schema changed
    • ~ GET /registry/v1/eoltags: param excludeVcsSnapshots (query) added
    • ~ GET /registry/v1/repotagssummary/{repoId}: param excludeVcsSnapshots (query) added
    • ~ GET /registry/v1/tags: param excludeVcsSnapshots (query) added
    • ~ GET /registry/v2/tags: param includeVcsSnapshots (query) added
    • ~ GET /vulnerabilities/v1/advisories/{parentId}/events: response schema changed
    • ~ PATCH /iam/v2/identityProviders/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/identityProviders/{uid}: request body changed; response schema changed
    • ~ POST /vulnerabilities/v1/advisories: response schema changed
    • ~ POST /vulnerabilities/v1/advisories/{parentId}/events: request body changed; response schema changed
    • ~ PUT /vulnerabilities/v1/advisories/{id}: request body changed; response schema changed
    • ~ PUT /vulnerabilities/v1/advisory_events/{id}: request body changed; response schema changed
    • GET /registry/v1/eoltags: param excludeVcsSnapshots (query) added⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • GET /registry/v1/repotagssummary/{repoId}: param excludeVcsSnapshots (query) added
    • GET /registry/v1/tags: param excludeVcsSnapshots (query) added
    • GET /registry/v2/tags: param includeVcsSnapshots (query) added

    4 details in Everything

42. Week of 2026-09-21 Sep 21, 2026 · issue 082

    Chainguard adds EU Sovereign Artifacts beta for data residency and ships 18 new container images including FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Launches Sovereign Artifacts beta, storing and serving Chainguard Containers and Chainguard Libraries artifact bytes in an EU region for enrolled customers, with automatic backfill of existing artifacts and approximately 30% faster pulls from Europe.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds new cursor-agent (application tier) container image.
    • Adds new chainguard-desktop-workstation-pc (base tier) container image.
    • Adds new commercial-avocado (commercial tier) container image.
    • Adds new rustfs (application tier) container image.

    +7 more show less

    • Adds new cloudzero-agent (application + FIPS tier) container image.
    • Adds new trivy-k8s-wrapper (application + FIPS tier) container image.
    • Adds new access-log-exporter (application + FIPS tier) container image.
    • Adds new datahub-gms (application + FIPS tier) container image.
    • Adds new kates-connect (application + FIPS tier) container image.
    • Adds new kubeflow-trainer-controller-manager (application + FIPS tier) container image.
    • Adds new tracee (application + FIPS tier) container image.

    12 details in Everything

43. docs update Sep 15, 2026 · issue 075

    New guide: sync Chainguard registry images to Harbor via proxy cache or replication rule⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Generate a pull token scoped to your org so Harbor can authenticate to cgr.dev without using personal credentials.
    copy

    $ chainctl auth configure-docker --pull-token

    Pull a Chainguard image through a Harbor proxy cache project once the endpoint and project are configured.
    copy

    $ docker pull $HARBOR_URL/cgr-proxy/$ORGANIZATION/$IMAGE:$TAG

    Pull a replicated Chainguard image from a Harbor mirror project after the replication rule has run.
    copy

    $ docker pull $HARBOR_URL/cgr-mirror/$IMAGE:$TAG

    • Adds chainctl auth configure-docker --pull-token as the way to generate pull-token credentials for Harbor to authenticate against cgr.dev.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Supports configuring a Harbor proxy cache project (e.g. cgr-proxy) backed by the Chainguard registry, enabling docker pull $HARBOR_URL/cgr-proxy/$ORGANIZATION/$IMAGE:$TAG.
    • Supports configuring a Harbor pull-based replication rule (e.g. cgr-mirror) to copy images from the Chainguard registry into a local Harbor project, with Flatten All Levels flattening and scheduled or manual trigger modes.

    3 details in Everything

44. docs update Sep 15, 2026 · issue 075

    New guide: set up Google Artifact Registry as a pull-through cache for Chainguard Free and Production containers⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Generate a long-lived pull token to authenticate Google Artifact Registry (or other non-OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. environments) against your org's private Chainguard registry.
    copy

    $ chainctl auth login
    chainctl auth configure-docker --pull-token

    Store the pull token password as a Google Secret Manager secret so Artifact Registry can use it for authenticated pull-through of Production containers.
    copy

    $ export PASSWORD="<pull-token>"
    gcloud secrets create chainguard-pull-token
    echo -n $PASSWORD | gcloud secrets versions add chainguard-pull-token --data-file=-

    Pull a Chainguard Free container through a configured Google Artifact Registry pull-through remote repository.
    copy

    $ gcloud auth configure-docker us-central1-docker.pkg.dev
    docker pull us-central1-docker.pkg.dev/<your-project-id>/chainguard-pull-through/chainguard/go:latest

    • Adds gcloud secrets create and gcloud secrets versions add workflow to store a Chainguard pull token password as a Google Secret Manager secret for authenticated Artifact Registry pull-through.

    1 detail in Everything

45. docs update Sep 15, 2026 · issue 075

    Chainguard: Supports configuring a remote Artifactory repository pointed at https://cgr.dev/ with the optional Project ID field to strip the chainguard/ or organization-name prefix from downstream pull paths.

    └──▷ TRY IT
    Generate a long-lived pull token to use as Artifactory remote repository credentials for pulling Chainguard Production Containers — capture the returned <identity-id> and <pull-token> for the repository's User Name and Password fields.
    copy

    $ chainctl auth configure-docker --pull-token --parent <organization>

    After authenticating to Artifactory, pull a Chainguard Production Container through the cgr-private remote repository — the organization prefix is included in the path unless Project ID was set during repository creation.
    copy

    $ docker login -u <linky@example.com> <my-project>.jfrog.io
    docker pull <my-project>.jfrog.io/cgr-private/<organization>/chainguard-base:latest

    Pull a Chainguard Free Container through the cgr-public remote repository after authenticating to Artifactory with a generated token.
    copy

    $ docker login -u <linky@example.com> <my-project>.jfrog.io
    docker pull <my-project>.jfrog.io/cgr-public/chainguard/go

    • Enables Artifactory as a pull-through cache for Chainguard Free Containers via a remote repository (example key cgr-public) requiring Enable Token Authentication and Block Mismatching Mime Types settings.
    • Enables Artifactory as a pull-through cache for Chainguard Production Containers via a remote repository (example key cgr-private) authenticated with a chainctl-generated <identity-id> and <pull-token>.
    • Supports configuring an Artifactory virtual repository to aggregate both free (cgr-public) and production (cgr-private) remote repositories under a single pull endpoint.

    3 details in Everything

46. docs update Sep 15, 2026 · issue 075

    Chainguard containers can now be pulled through Amazon ECRECRAmazon Elastic Container Registry, AWS's managed service for storing and distributing Docker and OCI container images, giving cyber tools a private, IAM-gated registry without self-hosting infrastructure. pull-through cache using a stored pull token in AWS Secrets Manager.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Generate a scoped Chainguard pull token that stays valid for one year, then store it in Secrets Manager so ECR can authenticate to cgr.dev on every cache refresh.
    copy

    $ chainctl auth configure-docker --pull-token --ttl=8760h
    
    # Use the printed <identity-id> and <pull-token> values:
    aws secretsmanager create-secret \
      --name ecr-pullthroughcache/chainguard-prod \
      --secret-string '{"username":"<identity-id>","accessToken":"<pull-token>"}' \
      --region us-east-1

    Create an ECR pull-through cache rule scoped to your private Chainguard namespace so images can be pulled with short paths like cg-ecr/chainguard-base:latest.
    copy

    $ aws ecr create-pull-through-cache-rule \
      --ecr-repository-prefix cg-ecr \
      --upstream-registry-url cgr.dev \
      --upstream-repository-prefix example.com \
      --credential-arn arn:aws:secretsmanager:us-east-1:<aws_account_id>:secret:ecr-pullthroughcache/chainguard-prod \
      --region us-east-1

    Authenticate Docker to your ECR private registry and pull a Chainguard Production Container through the cache.
    copy

    $ aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin <aws_account_id>.dkr.ecr.us-east-1.amazonaws.com
    docker pull <aws_account_id>.dkr.ecr.us-east-1.amazonaws.com/cg-ecr/chainguard-base:latest

    • Supports storing Chainguard credentials in AWS Secrets Manager under the ecr-pullthroughcache/ prefix using the username and accessToken keys, enabling ECR to authenticate to cgr.dev on your behalf.
    • Supports creating an ECR pull-through cache rule via aws ecr create-pull-through-cache-rule with --upstream-registry-url cgr.dev, --upstream-repository-prefix, and --credential-arn to cache Chainguard Production Containers in your private ECR registry.
    • Adds native Chainguard upstream option in the Amazon ECR console under Private registry > Pull through cache > Add rule, with a dedicated Chainguard upstream selection and namespace scoping controls.

    3 details in Everything

47. docs update Sep 15, 2026 · issue 075

    Chainguard adds chainctl actions entitlements create and chainctl actions entitlements list subcommands for managing action entitlements.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    List all action entitlements configured in your Chainguard environment to audit what actions are permitted.
    copy

    $ chainctl actions entitlements list

    Create a new action entitlement to grant a specific action capability in your Chainguard environment.
    copy

    $ chainctl actions entitlements create

48. docs update Sep 15, 2026 · issue 075
    └──▷ TRY IT
    Review all action entitlements currently provisioned in your Chainguard environment.
    copy

    $ chainctl actions entitlements list

    Provision a new action entitlement to grant access to a specific Chainguard action.
    copy

    $ chainctl actions entitlements create

49. docs update Sep 15, 2026 · issue 075

    Chainguard adds chainctl skills entitlements create command for managing agent skill entitlements.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

50. docs update Sep 15, 2026 · issue 075

    Chainguard Catalog Starter lets teams trial up to five production-grade container images free via console or chainctl⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ TRY IT
    Bootstrap a brand-new Catalog Starter account and pick your five free images entirely from the terminal.
    copy

    $ chainctl starter init

    After signing up, add the specific images you want to evaluate so they become available to pull.
    copy

    $ chainctl starter add-images python nginx postgresql

    Verify that provisioning is complete and check how many of your five image slots are in use before pulling.
    copy

    $ chainctl starter status

    • Adds chainctl starter init to interactively sign up for a new Catalog Starter account from the command line.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds chainctl starter request-access to join an existing Catalog Starter organization from the CLI.
    • Adds chainctl starter add-images to select up to five non-FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. images for a Catalog Starter plan, accepting one to four image names as arguments.
    • Adds chainctl starter status to display registry path, account provisioning status, image quota usage, and per-image readiness for a Catalog Starter organization.
    • Introduces Chainguard Catalog Starter, a free standalone plan (beta) that lets teams pull up to five non-FIPS production-grade Chainguard container images via cgr.dev/$ORGANIZATION/$IMAGE:latest without a paid subscription.

    5 details in Everything

51. v1 Sep 14, 2026 · issue 074

    Chainguard: New endpoint GET /argos/v1/vex/dump

    API change

    Chainguard: New endpoint GET /argos/v1/vex/dump

    • + GET /argos/v1/vex/documents/{ecosystem}/{package}
    • + GET /argos/v1/vex/dump
    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/stig:download
    • ~ GET /iam/v1/rolebindings: response schema changed
    • ~ GET /iam/v2/roleBindings: response schema changed
    • ~ GET /iam/v2/roleBindings/{uid}: response schema changed
    • ~ GET /policies/v1/decisions: param artifactId (query) added; response schema changed
    • ~ GET /registry/v1/entitlements/{parent}:effective: response schema changed
    • ~ GET /registry/v2/repos/{repoUid}/digests/{digest}/stig: response schema changed
    • ~ PATCH /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings:batchCreate: response schema changed
    • ~ POST /policies/v1/policies/validate: request body changed
    • ~ POST /registry/v1/entitlements/{parent}:addImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:removeImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:swapImages: response schema changed
52. Week of 2026-09-14 Sep 14, 2026 · issue 076

    Chainguard adds 26 new container images this week, including FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants for MongoDB, Kafka, OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor., and more.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Adds clamav-prometheus-exporter (application + FIPS) container image.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds crossplane-azure-marketplaceordering (application) container image.
    • Adds kserve-sklearnserver (ai) container image.
    • Adds commercial-spilo-fips (FIPS) container image.
    • Adds graphql-hive-gateway (application) container image.

    +12 more show less

    • Adds jupyterhub-k8s-singleuser-sample (application + FIPS) container image.
    • Adds nuxeo-2025 (application) container image.
    • Adds chainguard-server-hypervisor-aws (base) container image.
    • Adds mongodb-kubernetes (application + FIPS) container image.
    • Adds opentelemetry-python-instrumentation-fips (FIPS) container image.
    • Adds strimzi-kafka-fips (FIPS) container image.
    • Adds crossplane-aws-emrcontainers (application + FIPS) container image.
    • Adds kro (application + FIPS) container image.
    • Adds pyrra (application + FIPS) container image.
    • Adds starboard-exporter (application + FIPS) container image.
    • Adds krakend (application + FIPS) container image.
    • Adds mongodb-search (application + FIPS) container image.

    17 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Effective 2026-10-12: the sonar-scanner-cli image default user changes from root (UID 0) to nonroot (UID 65532); the scanner scratch directory moves from <project>/.scannerwork to /tmp/.scannerwork, breaking pipelines that read report-task.txt from the old location and derived images that write to system paths as root. To restore previous behavior, run with --user 0 (Docker), USER root (Dockerfile), or runAsUser: 0 (Kubernetes), or set -Dsonar.working.directory=<project>/.scannerwork and ensure the workspace is writable by the container user.
53. v1 Sep 13, 2026 · issue 073

    API surface changed: +3 endpoints, 13 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: +3 endpoints, 13 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + GET /argos/v1/vex/documents/{ecosystem}/{package}
    • + GET /argos/v1/vex/dump
    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/stig:download
    • ~ GET /iam/v1/rolebindings: response schema changed
    • ~ GET /iam/v2/roleBindings: response schema changed
    • ~ GET /iam/v2/roleBindings/{uid}: response schema changed
    • ~ GET /policies/v1/decisions: param artifactId (query) added; response schema changed
    • ~ GET /registry/v1/entitlements/{parent}:effective: response schema changed
    • ~ GET /registry/v2/repos/{repoUid}/digests/{digest}/stig: response schema changed
    • ~ PATCH /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings:batchCreate: response schema changed
    • ~ POST /policies/v1/policies/validate: request body changed
    • ~ POST /registry/v1/entitlements/{parent}:addImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:removeImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:swapImages: response schema changed
    • New endpoint GET /argos/v1/vex/documents/{ecosystem}/{package}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • New endpoint GET /registry/v2/repos/{repoUid}/digests/{digest}/stig:download
    • GET /policies/v1/decisions: param artifactId (query) added

    3 details in Everything

54. changelog Sep 13, 2026 · issue 073

    Chainguard adds Go 1.27 images including a new go-openssl-fips container and JFrog Catalog integration for Chainguard Libraries⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Adds go-openssl-fips container image that selects its FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments.-validated cryptographic module at deployment time rather than at compile time, enabling a single artifact to satisfy both OpenSSL FIPS and Go Cryptographic Module requirements without recompilation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Ships Go 1.27 across three Chainguard container images: go, go-fips, and go-openssl-fips.
    • Integrates Chainguard Libraries with JFrog Catalog, allowing joint customers to pull Chainguard-built packages through JFrog and enabling JFrog Zero-Touch Remediation to substitute patched Chainguard packages without changing developer workflows; Java support ships now, with JavaScript and Python to follow by end of September 2026.
    • Adds 39 new container images including 10 kubeflow-pipelines-* FIPS variants (kubeflow-pipelines-api-server-fips, kubeflow-pipelines-cache-deployer-fips, kubeflow-pipelines-cache-server-fips, kubeflow-pipelines-driver-fips, kubeflow-pipelines-frontend-fips, kubeflow-pipelines-metadata-envoy-fips, kubeflow-pipelines-metadata-writer-fips, kubeflow-pipelines-persistenceagent-fips, kubeflow-pipelines-scheduledworkflow-fips, kubeflow-pipelines-viewer-crd-controller-fips) plus dbmate, hadolint, jruby, gubernator, fortiotel, packer, security-profiles-operator, opentelemetry-go-instrumentation, redpanda-console-fips, and others.
    • Adds go-openssl-fips container image that selects its FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments.-validated cryptographic module at deployment time rather than at compile time, enabling a single artifact to satisfy both OpenSSL FIPS and Go Cryptographic Module requirements without recompilation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Integrates Chainguard Libraries with JFrog Catalog, allowing joint customers to pull Chainguard-built packages through JFrog and enabling JFrog Zero-Touch Remediation to substitute patched Chainguard packages without changing developer workflows; Java support ships now, with JavaScript and Python to follow by end of September 2026.
    • Adds 39 new container images including 10 kubeflow-pipelines-* FIPS variants (kubeflow-pipelines-api-server-fips, kubeflow-pipelines-cache-deployer-fips, kubeflow-pipelines-cache-server-fips, kubeflow-pipelines-driver-fips, kubeflow-pipelines-frontend-fips, kubeflow-pipelines-metadata-envoy-fips, kubeflow-pipelines-metadata-writer-fips, kubeflow-pipelines-persistenceagent-fips, kubeflow-pipelines-scheduledworkflow-fips, kubeflow-pipelines-viewer-crd-controller-fips) plus dbmate, hadolint, jruby, gubernator, fortiotel, packer, security-profiles-operator, opentelemetry-go-instrumentation, redpanda-console-fips, and others.

    1 more in Everything

55. v1 Sep 12, 2026 · issue 072

    Chainguard: New endpoint GET /argos/v1/vex/documents/{ecosystem}/{package}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    Chainguard: New endpoint GET /argos/v1/vex/documents/{ecosystem}/{package}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + GET /argos/v1/vex/documents/{ecosystem}/{package}
    • + GET /argos/v1/vex/dump
    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/stig:download
    • ~ GET /iam/v1/rolebindings: response schema changed
    • ~ GET /iam/v2/roleBindings: response schema changed
    • ~ GET /iam/v2/roleBindings/{uid}: response schema changed
    • ~ GET /policies/v1/decisions: param artifactId (query) added; response schema changed
    • ~ GET /registry/v1/entitlements/{parent}:effective: response schema changed
    • ~ GET /registry/v2/repos/{repoUid}/digests/{digest}/stig: response schema changed
    • ~ PATCH /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings:batchCreate: response schema changed
    • ~ POST /policies/v1/policies/validate: request body changed
    • ~ POST /registry/v1/entitlements/{parent}:addImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:removeImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:swapImages: response schema changed
56. changelog Sep 12, 2026 · issue 072

    Chainguard: Adds go-openssl-fips container image for Go 1.27 that selects its FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments.-validated cryptographic module at deployment time rather than at compile time, enabling a single build artifact to run across environments without recompilation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ USE IT
    Build a Go 1.27 FIPS image once and deploy to any environment — the validated OpenSSL FIPS module is chosen at deployment, not compile time, so you no longer need separate pipelines for different FIPS providers.
    Dockerfile copy

    FROM cgr.dev/chainguard/go-openssl-fips:latest

    • Ships 39 new container images this week, including 10 kubeflow-pipelines-* FIPS variants and new images for dbmate, hadolint, jruby, kserve-huggingfaceserver, gubernator, packer, security-profiles-operator, aws-lambda-dotnet, opentelemetry-go-instrumentation, presidio-anonymizer, redpanda-console-fips, and others.

    1 detail in Everything

57. v1 Sep 11, 2026 · issue 071

    Chainguard: New endpoint GET /argos/v1/vex/documents/{ecosystem}/{package}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    Chainguard: New endpoint GET /argos/v1/vex/documents/{ecosystem}/{package}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + GET /argos/v1/vex/documents/{ecosystem}/{package}
    • + GET /argos/v1/vex/dump
    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/stig:download
    • ~ GET /iam/v1/rolebindings: response schema changed
    • ~ GET /iam/v2/roleBindings: response schema changed
    • ~ GET /iam/v2/roleBindings/{uid}: response schema changed
    • ~ GET /policies/v1/decisions: param artifactId (query) added; response schema changed
    • ~ GET /registry/v1/entitlements/{parent}:effective: response schema changed
    • ~ GET /registry/v2/repos/{repoUid}/digests/{digest}/stig: response schema changed
    • ~ PATCH /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roleBindings:batchCreate: response schema changed
    • ~ POST /policies/v1/policies/validate: request body changed
    • ~ POST /registry/v1/entitlements/{parent}:addImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:removeImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:swapImages: response schema changed
    • New endpoint GET /argos/v1/vex/dump

    1 detail in Everything

58. changelog Sep 11, 2026 · issue 071

    Chainguard Libraries now work in JFrog Catalog with Xray and Curation policy support. Java is available now; JavaScript and Python support is planned for September 2026.

    └──▷ USE IT
    Build a single Go 1.27 FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. artifact and deploy it to environments requiring different validated crypto modules — no recompilation needed at deployment.
    Dockerfile copy

    FROM cgr.dev/chainguard/go-openssl-fips:1.27

59. v1 Sep 10, 2026 · issue 070

    API surface changed: +1 endpoint, 3 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: +1 endpoint, 3 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/stig:download
    • ~ GET /policies/v1/decisions: param artifactId (query) added; response schema changed
    • ~ GET /registry/v2/repos/{repoUid}/digests/{digest}/stig: response schema changed
    • ~ POST /policies/v1/policies/validate: request body changed
    • New endpoint GET /registry/v2/repos/{repoUid}/digests/{digest}/stig:download⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • GET /policies/v1/decisions: param artifactId (query) added

    2 details in Everything

60. changelog Sep 10, 2026 · issue 070

    Chainguard adds Go 1.27 images with runtime FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. module selection and Chainguard Libraries support in JFrog Catalog.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Adds go-openssl-fips container image for Go 1.27 that selects its FIPS-validated cryptographic module at deployment rather than at build time, enabling a single artifact to run with either the OpenSSL FIPS provider or the Go Cryptographic Module without recompilation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds Go 1.27 support across the go, go-fips, and go-openssl-fips Chainguard container images.
    • Integrates Chainguard Libraries with JFrog Catalog so joint customers can pull Chainguard-built packages through JFrog Artifact Repository without build errors, enabling JFrog Zero-Touch Remediation with patched Chainguard packages; Java support is live, JavaScript and Python to follow by end of September 2026.
    • Adds 39 new container images including 10 FIPS variants of kubeflow-pipelines-* components, plus dbmate, hadolint, jruby, kserve-huggingfaceserver, gubernator, fortiotel, packer, security-profiles-operator, aws-lambda-dotnet, opentelemetry-go-instrumentation, presidio-anonymizer, redpanda-console-fips, and others.
    • Adds go-openssl-fips container image for Go 1.27 that selects its FIPS-validated cryptographic module at deployment rather than at build time, enabling a single artifact to run with either the OpenSSL FIPS provider or the Go Cryptographic Module without recompilation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Integrates Chainguard Libraries with JFrog Catalog so joint customers can pull Chainguard-built packages through JFrog Artifact Repository without build errors, enabling JFrog Zero-Touch Remediation with patched Chainguard packages; Java support is live, JavaScript and Python to follow by end of September 2026.
    • Adds 39 new container images including 10 FIPS variants of kubeflow-pipelines-* components, plus dbmate, hadolint, jruby, kserve-huggingfaceserver, gubernator, fortiotel, packer, security-profiles-operator, aws-lambda-dotnet, opentelemetry-go-instrumentation, presidio-anonymizer, redpanda-console-fips, and others.

    1 more in Everything

61. changelog Sep 9, 2026 · issue 069

    Chainguard: Adds Go 1.27 support across three Chainguard container images: go, go-fips, and go-openssl-fips.

    └──▷ USE IT
    Build a single Go 1.27 binary that satisfies FedRAMPFedRAMPA US government program that standardizes cloud security authorization, letting vendors get a single assessment accepted across federal agencies instead of repeating the process for each one./CNSA 2.0 requirements — the validated FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. module is chosen at deploy time, so one image runs across environments without recompilation.
    Dockerfile copy

    FROM cgr.dev/chainguard/go-openssl-fips:latest AS build
    RUN go build -o /app ./...
    
    FROM cgr.dev/chainguard/go-openssl-fips:latest
    COPY --from=build /app /app
    ENTRYPOINT ["/app"]

    • Integrates Chainguard Libraries with JFrog Catalog, allowing joint customers to pull Chainguard-built packages through JFrog and enabling JFrog Zero-Touch Remediation with Chainguard packages; Java support ships now, with JavaScript and Python scheduled by end of September 2026.
    • Adds 39 new container images including kubeflow-pipelines-api-server-fips, kubeflow-pipelines-cache-deployer-fips, kubeflow-pipelines-cache-server-fips, kubeflow-pipelines-driver-fips, kubeflow-pipelines-frontend-fips, kubeflow-pipelines-metadata-envoy-fips, kubeflow-pipelines-metadata-writer-fips, kubeflow-pipelines-persistenceagent-fips, kubeflow-pipelines-scheduledworkflow-fips, kubeflow-pipelines-viewer-crd-controller-fips, dbmate, hadolint, jruby, kserve-huggingfaceserver, gubernator, fortiotel, packer, security-profiles-operator, aws-lambda-dotnet, opentelemetry-go-instrumentation, prom-label-proxy, kserve-sklearnserver-fips, presidio-anonymizer, and redpanda-console-fips.

    2 details in Everything

62. docs update Sep 9, 2026 · issue 069

    New guide: use Cloudsmith as a pull-through cache for Chainguard Free and Production container images

    └──▷ TRY IT
    Generate a 7-day pull token for a Chainguard org registry to use as Cloudsmith upstream credentials.
    copy

    $ chainctl auth configure-docker --pull-token --ttl=168h

    Pull a Production container image from Chainguard through a Cloudsmith pull-through repository.
    copy

    $ docker pull docker.cloudsmith.io/chainguard-example/chainguard-private/chainguard.edu/python:3.9-dev

    • Supports Cloudsmith as a pull-through cache for Chainguard Free containers by setting the upstream Proxy URL to https://cgr.dev/chainguard with Mode set to Cache and Proxy.
    • Supports Cloudsmith as a pull-through cache for Chainguard Production containers by setting the upstream Proxy URL to https://cgr.dev/ and authenticating with a pull token generated via chainctl auth configure-docker --pull-token.
    • Adds --ttl flag to chainctl auth configure-docker --pull-token to control pull token lifetime (e.g. --ttl=24h; default is 30 days).
    • Enables pulling Production containers through Cloudsmith using the path docker.cloudsmith.io/<cloudsmith-organization>/<cloudsmith-repository>/<chainguard-registry>/IMAGE.
    • Supports Cloudsmith as a pull-through cache for Chainguard Free containers by setting the upstream Proxy URL to https://cgr.dev/chainguard with Mode set to Cache and Proxy.
    • Supports Cloudsmith as a pull-through cache for Chainguard Production containers by setting the upstream Proxy URL to https://cgr.dev/ and authenticating with a pull token generated via chainctl auth configure-docker --pull-token.
    • Enables pulling Production containers through Cloudsmith using the path docker.cloudsmith.io/<cloudsmith-organization>/<cloudsmith-repository>/<chainguard-registry>/IMAGE.

    1 more in Everything

63. docs update Sep 9, 2026 · issue 069

    Chainguard now supports Amazon ECRECRAmazon Elastic Container Registry, AWS's managed service for storing and distributing Docker and OCI container images, giving cyber tools a private, IAM-gated registry without self-hosting infrastructure. as a pull-through cache, letting you serve Chainguard Containers from your own ECR private registry.

    └──▷ TRY IT
    Generate a Chainguard pull token valid for one year to supply to ECR's Secrets Manager credential store.
    copy

    $ chainctl auth configure-docker --pull-token --ttl=8760h

    Store the Chainguard pull token in Secrets Manager under the required ecr-pullthroughcache/ prefix so ECR can authenticate to cgr.dev on your behalf.
    copy

    $ aws secretsmanager create-secret \
      --name ecr-pullthroughcache/<secret_name> \
      --secret-string '{"username":"<identity-id>","accessToken":"<pull-token>"}' \
      --region <region>

    Create an ECR pull-through cache rule scoped to your org's private Chainguard namespace so pulls use short paths like cg-ecr/chainguard-base:latest.
    copy

    $ aws ecr create-pull-through-cache-rule \
      --ecr-repository-prefix cg-ecr \
      --upstream-registry-url cgr.dev \
      --upstream-repository-prefix example.com \
      --credential-arn arn:aws:secretsmanager:<region>:<aws_account_id>:secret:ecr-pullthroughcache/<secret_name> \
      --region <region>

    • Adds support for Amazon ECR pull-through cache rules targeting cgr.dev, with credentials stored as a Secrets Manager secret whose name must begin with the ecr-pullthroughcache/ prefix and whose keys must be username and accessToken.
    • Adds chainctl auth configure-docker --pull-token to generate a longer-lived Chainguard pull token suitable for registry mirroring tools like ECR, with an optional --ttl flag (e.g. --ttl=8760h) to control expiry.
    • Supports scoping a pull-through cache rule to a single private namespace via --upstream-repository-prefix on aws ecr create-pull-through-cache-rule, so that downstream image paths omit the org namespace.
    • Supports an unscoped rule (omitting --upstream-repository-prefix, or selecting No prefix in the ECR console) to cache any repository the pull token can access, including Free containers from the public chainguard namespace, using full paths like cg-ecr/example.com/chainguard-base:latest or cg-ecr/chainguard/go:latest.
    • Adds a Chainguard upstream option in the Amazon ECR console pull-through cache rule wizard (Private registry > Pull through cache > Add rule > Specify upstream), allowing AWS-console-only configuration without the CLI.

    5 details in Everything

64. docs update Sep 9, 2026 · issue 069

    Chainguard Catalog Starter lets teams trial up to five production-grade container images free via console or chainctl

    └──▷ TRY IT
    Sign up for a new Catalog Starter account and select your free images entirely from the terminal.
    copy

    $ chainctl starter init

    Add specific images to your Catalog Starter plan after signup — for example, picking python and nginx as two of your five slots.
    copy

    $ chainctl starter add-images python nginx

    Check provisioning status and confirm all selected images are ready to pull before updating CI/CD pipelines.
    copy

    $ chainctl starter status

    • Adds chainctl starter init command to sign up for a new Catalog Starter account interactively from the CLI.
    • Adds chainctl starter request-access command to join an existing Catalog Starter organization from the CLI.
    • Adds chainctl starter add-images command to select up to five non-FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. images for a Catalog Starter plan from the CLI.
    • Adds chainctl starter status command to show registry path, account provisioning status, image quota usage, and per-image readiness.
    • Introduces Chainguard Catalog Starter, a free standalone plan allowing teams to choose and pull up to five non-FIPS container images (including dependent Helm charts) from the Chainguard catalog without a paid subscription.

    +2 more show less

    • Catalog Starter images can be pulled through third-party registries such as JFrog Artifactory and integrated into CI/CD pipelines.
    • Users in a Catalog Starter organization are assigned the limited_owner role, granting Console browsing, image pulling, and pull token creation.

    7 details in Everything

65. docs update Sep 8, 2026 · issue 068

    Chainguard Libraries quickstart documents source-rebuilt Java, JavaScript, and Python packages with chainctl entitlement, pull-token, and verify commands

    └──▷ TRY IT
    Provision a Python Libraries entitlement and create a 30-day pull token to authenticate your build tooling against the Chainguard repository.
    copy

    $ chainctl libraries entitlements create --ecosystems=PYTHON
    chainctl auth pull-token create --repository=python --ttl=720h

    After configuring your build tool, confirm that your resolved dependencies were actually built from source by Chainguard rather than served from upstream.
    copy

    $ chainctl libraries verify /path/to/artifact

    • Adds chainctl libraries entitlements create --ecosystems=JAVASCRIPT (also JAVA, PYTHON) to provision access to Chainguard Libraries from the CLI.
    • Adds chainctl auth pull-token create --repository=java|javascript|python --ttl=<duration> to generate basic-auth credentials; default TTLTTLTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. is 720h (30 days), maximum is 8760h (365 days).
    • Adds chainctl libraries verify /path/to/artifact to confirm which dependencies were built from source by Chainguard; requires libraries.java.pull, libraries.javascript.pull, or libraries.python.pull permission, or the Owner role.
    • Adds chainctl libraries update-hashes to rewrite existing JavaScript or Python lockfile checksums to Chainguard's without regenerating the lockfile from scratch.
    • Serves Chainguard-rebuilt Java packages via https://libraries.cgr.dev/java/ with optional upstream fallback for packages not yet built by Chainguard.

    +4 more show less

    • Serves Chainguard-rebuilt JavaScript packages via https://libraries.cgr.dev/javascript/ configurable in .npmrc, with npm/pnpm/Yarn/Yarn Classic/Bun support.
    • Serves Chainguard-rebuilt Python packages via https://libraries.cgr.dev/python/ (simple index at https://libraries.cgr.dev/python/simple) and a separate CVE-remediated repository at https://libraries.cgr.dev/python-remediated (simple index at https://libraries.cgr.dev/python-remediated/simple).
    • Supports pull-token creation through the Chainguard Console under 'Overview > Manage pull tokens > Create access tokenaccess tokenA credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions.' as an alternative to chainctl.
    • Upstream fallback for serving eligible upstream packages through the Chainguard repository endpoint is available as an opt-in setting (off by default) with configurable policy controls including cooldown and malware scanning.

    9 details in Everything

66. v1 Sep 7, 2026 · issue 067

    API surface changed: +2 endpoints, 4 modified

    API change

    API surface changed: +2 endpoints, 4 modified

    • + GET /iam/v1/scimUsers
    • + POST /vulnerabilities/v2/vulnCountReports:list
    • ~ GET /iam/v2/roles/{uid}: response schema changed
    • ~ GET /libraries/v1/artifacts: response schema changed
    • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
    • New endpoint GET /iam/v1/scimUsers
    • New endpoint POST /vulnerabilities/v2/vulnCountReports:list
    • GET /iam/v2/roles/{uid}: response schema changed
    • GET /libraries/v1/artifacts: response schema changed
    • PATCH /iam/v2/roles/{uid}: request body changed; response schema changed

    +1 more show less

    • POST /iam/v2/roles/{uid}: request body changed; response schema changed

    6 details in Everything

67. Week of 2026-09-07 Sep 7, 2026 · issue 069

    Chainguard ships Go 1.27 with runtime FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. module selection, JFrog Catalog integration for Libraries, and 39 new container images including kubeflow-pipelines FIPS variants.

    • Adds go-openssl-fips image for Go 1.27 that selects its FIPS-validated cryptographic module at deployment time rather than at compile time, enabling a single artifact to satisfy both OpenSSL FIPS provider and Go Cryptographic Module requirements without recompilation — with CNSA 2.0 readiness.
    • Adds go and go-fips images updated to Go 1.27, alongside the new go-openssl-fips image, with Go 1.26 and earlier continuing to be supported until end-of-life.
    • Adds JFrog Catalog recognition for Chainguard-built packages, allowing joint Chainguard and JFrog customers to pull Chainguard Libraries through JFrog — enabling JFrog Zero-Touch Remediation to swap in patched Chainguard packages without developer workflow changes or major version upgrades.
    • Adds Java support for Chainguard Libraries in JFrog Catalog at launch, with JavaScript and Python support scheduled by end of September 2026.
    • Adds 10 new kubeflow-pipelines-* FIPS container images including kubeflow-pipelines-api-server-fips, kubeflow-pipelines-cache-deployer-fips, kubeflow-pipelines-cache-server-fips, kubeflow-pipelines-driver-fips, kubeflow-pipelines-frontend-fips, kubeflow-pipelines-metadata-envoy-fips, kubeflow-pipelines-metadata-writer-fips, kubeflow-pipelines-persistenceagent-fips, kubeflow-pipelines-scheduledworkflow-fips, and kubeflow-pipelines-viewer-crd-controller-fips.

    +1 more show less

    • Adds new container images including security-profiles-operator, jruby, kserve-huggingfaceserver, kserve-sklearnserver-fips, presidio-anonymizer, redpanda-console-fips, opentelemetry-go-instrumentation, packer, aws-lambda-dotnet, and others — totalling 39 new images this week.
    • Adds go-openssl-fips image for Go 1.27 that selects its FIPS-validated cryptographic module at deployment time rather than at compile time, enabling a single artifact to satisfy both OpenSSL FIPS provider and Go Cryptographic Module requirements without recompilation — with CNSA 2.0 readiness.
    • Adds JFrog Catalog recognition for Chainguard-built packages, allowing joint Chainguard and JFrog customers to pull Chainguard Libraries through JFrog — enabling JFrog Zero-Touch Remediation to swap in patched Chainguard packages without developer workflow changes or major version upgrades.
    • Adds Java support for Chainguard Libraries in JFrog Catalog at launch, with JavaScript and Python support scheduled by end of September 2026.
    • Adds 10 new kubeflow-pipelines-* FIPS container images including kubeflow-pipelines-api-server-fips, kubeflow-pipelines-cache-deployer-fips, kubeflow-pipelines-cache-server-fips, kubeflow-pipelines-driver-fips, kubeflow-pipelines-frontend-fips, kubeflow-pipelines-metadata-envoy-fips, kubeflow-pipelines-metadata-writer-fips, kubeflow-pipelines-persistenceagent-fips, kubeflow-pipelines-scheduledworkflow-fips, and kubeflow-pipelines-viewer-crd-controller-fips.
    • Adds new container images including security-profiles-operator, jruby, kserve-huggingfaceserver, kserve-sklearnserver-fips, presidio-anonymizer, redpanda-console-fips, opentelemetry-go-instrumentation, packer, aws-lambda-dotnet, and others — totalling 39 new images this week.

    1 more in Everything

68. v1 Sep 4, 2026 · issue 064

    API surface changed: +2 endpoints, 15 modified

    API change

    API surface changed: +2 endpoints, 15 modified

    • + GET /libraries/v1/malware/blocklist/statistics
    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/stig
    • ~ GET /iam/v2/roles/{uid}: response schema changed
    • ~ GET /registry/v1/entitlements/{parent}/catalog-images: response schema changed
    • ~ GET /registry/v1/entitlements/{parent}/images: response schema changed
    • ~ GET /registry/v1/entitlements/{parent}:effective: response schema changed
    • ~ GET /registry/v1/repos/{repoId}/digests/{digest}/chart: response schema changed
    • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /argos/v1/documents/{id}: response schema changed
    • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /policies/v1/policies/validate: request body changed
    • ~ POST /policies/v1/policies/{id}: request body changed; response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:addImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:removeImages: response schema changed
    • ~ POST /registry/v1/entitlements/{parent}:swapImages: response schema changed
    • ~ POST /registry/v1/repos/{parentId}:addChart: request body changed; response schema changed
    • ~ PUT /policies/v1/policies/{id}: request body changed; response schema changed
    • New endpoint GET /libraries/v1/malware/blocklist/statistics
    • New endpoint GET /registry/v2/repos/{repoUid}/digests/{digest}/stig
    • GET /iam/v2/roles/{uid}: response schema changed
    • GET /registry/v1/entitlements/{parent}/catalog-images: response schema changed
    • GET /registry/v1/entitlements/{parent}/images: response schema changed

    +12 more show less

    • GET /registry/v1/entitlements/{parent} response schema changed
    • GET /registry/v1/repos/{repoId}/digests/{digest}/chart: response schema changed
    • PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
    • POST /argos/v1/documents/{id}: response schema changed
    • POST /iam/v2/roles/{uid}: request body changed; response schema changed
    • POST /policies/v1/policies/validate: request body changed
    • POST /policies/v1/policies/{id}: request body changed; response schema changed
    • POST /registry/v1/entitlements/{parent}:addImages: response schema changed
    • POST /registry/v1/entitlements/{parent}:removeImages: response schema changed
    • POST /registry/v1/entitlements/{parent}:swapImages: response schema changed
    • POST /registry/v1/repos/{parentId}:addChart: request body changed; response schema changed
    • PUT /policies/v1/policies/{id}: request body changed; response schema changed

    17 details in Everything

69. changelog Sep 2, 2026 · issue 062

    Chainguard adds custom container pull policies in open beta, plus build pinning for Libraries across JS, Python, and Java.

    • Introduces custom container pull policies (open beta): organizations can now write their own Rego-based container pull policies, submitted as YAML manifests and managed with chainctl, supporting parameterized declarations with per-binding values, and an ENFORCE mode that blocks pulls without loosening system policies.
    • Enables build pinning for all organizations using Chainguard Libraries with upstream fallback across JavaScript, Python, and Java — recording which copy (upstream mirror or Chainguard rebuild) was first pulled and resolving that version consistently until explicitly changed.
    • Adds 21 new container images this week, including dynatrace-operator, netshoot, strimzi-drain-cleaner, nomad, redpanda-console, apache-polaris, kserve-pmmlserver, kserve-xgbserver, victorialogs-vlagent, and FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants mlrun-api-fips and mlrun-fips.
    • Extends active support window for Istio 1.29 images (istio, istio-cni, istio-envoy, istio-operator, istio-pilot-agent, istio-pilot-discovery, ztunnel) and teleport:18 through 2027-02-28.

    4 details in Everything

70. docs update Aug 31, 2026 · issue 060

    Chainguard Guardener launches with Hardened Actions, Commit Verification, and AI-driven Dockerfile migration via chainctl agent dockerfile

    • New chainctl agent dockerfile commands run AI-driven, iterative migration of Dockerfiles to Chainguard Containers locally.
    • New Hardened Actions capability recommends and migrates GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. to Chainguard's hardened, SHA-pinned equivalents via non-blocking PR review comments or scheduled/on-demand migration pull requests.
    • New Commit Verification capability enforces cryptographically signed commits against a per-repository policy, supporting keyless (Sigstore) signatures and static keys such as GPG.
    • New .chainguard/ configuration model enables Guardener GitHub App capabilities (Hardened Actions, Commit Verification) per repository via committed config files.

    4 details in Everything

71. docs update Aug 31, 2026 · issue 060

    Chainguard Libraries for Python: source-rebuilt PyPI packages with CVE backports, CUDACUDANVIDIA's platform and programming interface for running general computation on its GPUs. Nearly every AI training and inference stack is built on it first. wheels, and remediated index endpoints

    • Adds https://libraries.cgr.dev/python/ index serving PyPI packages rebuilt from source within the Chainguard Factory, consumable via pip, uv, or poetry.
    • Adds https://libraries.cgr.dev/python-remediated/ index providing older package versions with High and Critical CVEs patched, identified by a +cgr.N local version suffix (e.g., 1.1.2+cgr.1).
    • Adds CUDA-specific indexes — https://libraries.cgr.dev/cu126/simple/, https://libraries.cgr.dev/cu128/simple/, and https://libraries.cgr.dev/cu129/simple/ — serving GPUGPUA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference.-accelerated Python wheels built and tested against specific NVIDIA CUDA versions.
    • Supports Chainguard Repository as a single endpoint for Python package retrieval with protected upstream PyPI fallback, allowing Chainguard-built packages to be preferred while uncovered packages fall through to PyPI.
    • Supports integration with third-party repository managers (Cloudsmith, JFrog Artifactory, Sonatype Nexus Repository) for centralized access control and upstream fallback.

    +2 more show less

    • Extended support for Python 3.9 packages available until May 15, 2026; supported versions are Python 3.10 and later.
    • Distributes packages as Python wheels (manylinux_2_28 and manylinux_2_39) for x86_64 and aarch64 Linux, accompanied by source distribution tarballs; Windows and macOS builds fall back to PyPI via the repository manager.

    7 details in Everything

72. docs update Aug 31, 2026 · issue 060

    Chainguard Libraries for JavaScript launches with SLSASLSASupply-chain Levels for Software Artifacts, a framework for assessing how software was built and protecting that process from tampering. Provenance records help verify where a build came from. provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build., SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue., and a secured npm-protocol endpoint at libraries.cgr.dev

    └──▷ TRY IT
    Verify a downloaded package tarball's SLSA provenance was produced by Chainguard — useful in CI before accepting a dependency.
    copy

    $ chainctl libraries verify axios-mock-adapter-1.17.0.tgz

    Manually extract and verify a package's SLSA provenance bundle with cosign for debugging or custom workflow integration.
    copy

    $ curl -H "Authorization: Bearer $(chainctl auth token --audience=libraries.cgr.dev)" \
      "https://libraries.cgr.dev/javascript/-/npm/v1/attestations/axios-mock-adapter@1.17.0" | \
      jq -c '.attestations[] | select(.predicateType | contains("slsa")) | .bundle' \
      > axios-mock-adapter-provenance.sigstore.json
    
    cosign verify-blob-attestation \
      --bundle axios-mock-adapter-provenance.sigstore.json \
      --type slsaprovenance1 \
      --certificate-oidc-issuer=https://issuer.enforce.dev \
      --certificate-identity-regexp="^https://issuer.enforce.dev/" \
      --check-claims=false \
      axios-mock-adapter-1.17.0.tgz

    Retrieve the SPDXSPDXAn open standard for describing software components, licenses and their relationships. Its documents let different tools exchange a software bill of materials without inventing a new format. SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. for a specific package version to feed into a software composition analysissoftware composition analysisSoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. pipeline.
    copy

    $ curl -H "Authorization: Bearer $(chainctl auth token --audience=libraries.cgr.dev)" \
      https://libraries.cgr.dev/javascript/-/npm/v1/sbom/spdx/react-router@7.11.0

    • New chainctl libraries verify PACKAGE-VERSION.tgz command verifies a package tarball's SLSA provenance attestation in a single step.
    • New chainctl libraries update-hashes command updates lockfile integrity hashes in place after switching from upstream npm to Chainguard-rebuilt packages.
    • Adds https://libraries.cgr.dev/javascript/ as the npm-protocol repository endpoint for Chainguard-built JavaScript packages, authenticated with credentials retrieved via chainctl.
    • Exposes SLSA provenance bundles per package via GET https://libraries.cgr.dev/javascript/-/npm/v1/attestations/PACKAGE@VERSION, filterable with jq for slsa predicate type; attestations are signed by Chainguard's OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. issuer https://issuer.enforce.dev.
    • Exposes SBOMs in SPDX format per package via GET https://libraries.cgr.dev/javascript/-/npm/v1/sbom/spdx/PACKAGE@VERSION; availability can be checked with npm show PACKAGE@VERSION dist.sboms.

    +4 more show less

    • Provides an optional upstream npm Registry fallback through the Chainguard Repository, with configurable security policy controls including malware scanning and a configurable cooldown period for newly published upstream versions.
    • Adds build pinning to keep a version pulled from upstream stable after Chainguard publishes its own build, preventing unexpected hash changes.
    • Supports consumption through a repository manager (JFrog Artifactory, Sonatype Nexus) via global configuration, in addition to direct per-workstation build-tool configuration.
    • Compatible with npm, pnpm (v11+ recommended), Yarn, and Yarn Berry via the npm repository format.

    9 details in Everything

73. docs update Aug 31, 2026 · issue 060

    Chainguard Libraries for Java delivers patched Maven artifacts via a drop-in repository at libraries.cgr.dev/java/ with SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. and SLSASLSASupply-chain Levels for Software Artifacts, a framework for assessing how software was built and protecting that process from tampering. Provenance records help verify where a build came from. provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build. files.

    └──▷ TRY IT
    Download a specific Maven artifact directly from the Chainguard repository for offline inspection or verification.
    copy

    $ curl -L --user "$CHAINGUARD_JAVA_IDENTITY_ID:$CHAINGUARD_JAVA_TOKEN" \
      -O https://libraries.cgr.dev/java/commons-io/commons-io/2.13.0/commons-io-2.13.0.pom

    Fetch the SLSA provenance and SBOM for an artifact to verify supply-chain integrity before use.
    copy

    $ curl -L --user "$CHAINGUARD_JAVA_IDENTITY_ID:$CHAINGUARD_JAVA_TOKEN" \
      -O https://libraries.cgr.dev/java/org/apache/commons/commons-compress/1.23.0/commons-compress-1.23.0.slsa-attestation.json \
      -O https://libraries.cgr.dev/java/org/apache/commons/commons-compress/1.23.0/commons-compress-1.23.0.spdx.json

    List all Chainguard-built versions of a library to identify whether a patched version is available before updating your build file.
    copy

    $ curl -L --user "$CHAINGUARD_JAVA_IDENTITY_ID:$CHAINGUARD_JAVA_TOKEN" \
      https://libraries.cgr.dev/java/org/apache/commons/commons-lang3/maven-metadata.xml

    • New Chainguard Libraries for Java service rebuilds Maven Central and other common Java artifacts from source with the latest vulnerability patches and supply-chain protections, accessible at https://libraries.cgr.dev/java/.
    • Adds CVE Remediation (beta for Spring Boot): patched artifacts are published with a -0.cgr.N version suffix (e.g. org.apache.commons:commons-lang3:3.18.0-0.cgr.1) so version ranges can automatically resolve to remediated builds.
    • Each built artifact includes a .slsa-attestation.json SLSA provenance file and a .spdx.json SBOM file co-located with the .jar and .pom in the repository directory.
    • Supports optional upstream Maven Central fallback with source code and maintainer behavior scanning and a configurable cooldown period, managed through the Chainguard Repository.
    • Authentication to https://libraries.cgr.dev/java/ uses credentials retrieved via chainctl, exposed as $CHAINGUARD_JAVA_IDENTITY_ID and $CHAINGUARD_JAVA_TOKEN environment variables.

    +2 more show less

    • Repository directory at https://libraries.cgr.dev/java/ provides Maven-format browsable directory listing; maven-metadata.xml per artifact path lists all Chainguard-built versions.
    • Cache-clearing commands for troubleshooting resolution: rm -rf ~/.m2/repository (Maven), rm -rf ~/.gradle/caches/ (Gradle), bazel clean --expunge (Bazel).

    7 details in Everything

74. Week of 2026-08-31 Aug 31, 2026 · issue 060

    Chainguard adds custom Rego container pull policies, build pinning for Libraries, and new Windows-compatible chainctl workflows.

    └──▷ TRY IT
    Review which package-version copies your organization has pinned under Chainguard Libraries build pinning, or initiate an opt-out.
    copy

    $ chainctl libraries cache

    • Adds chainctl policies custom validate subcommand that reports the exact line and column of a policy error before storing it, enabling CI validation of Rego policy manifests.
    • Introduces custom container pull policies (open beta): organizations can now write Rego expressions submitted as YAML manifests, managed via chainctl, supporting parameters with per-binding values and ENFORCE mode that blocks pulls.
    • Adds chainctl libraries cache command to review which package-version copies (upstream mirror or Chainguard rebuild) your organization holds, or to opt out of build pinning.
    • Enables build pinning for all organizations using Chainguard Libraries with upstream fallback across JavaScript, Python, and Java — recording the first-resolved copy of each package version to keep lockfiles and checksums stable.
    • Extends chainctl self-update on Windows to replace the running executable correctly and verify release attestations before installing, without requiring administrator privileges.

    +1 more show less

    • Adds 21 new container images including dynatrace-operator, netshoot, strimzi-drain-cleaner, redpanda-console, apache-polaris, nomad, kserve-pmmlserver, kserve-xgbserver, victorialogs-vlagent, mlrun-api-fips, mlrun-fips, and kube-logging-operator-fluentd-drain-watch, with both standard and FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants where noted.

    6 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The container images kube-conformance:1.32, kubernetes:1.32, nextcloud-server:31, rke2-runtime:1.32, and teleport:17 have passed their grace periods and are no longer available.
75. v1 Aug 28, 2026 · issue 058

    API surface changed: +2 endpoints, 11 modified

    API change

    API surface changed: +2 endpoints, 11 modified

    • + GET /registry/v1/chart-image-bindings
    • + GET /registry/v2/catalogImages
    • ~ GET /argos/v1/documents: param updatedSince (query) added
    • ~ GET /argos/v1/orgs/{parent}/vulns: param updatedSince (query) added
    • ~ GET /iam/v2/roles/{uid}: response schema changed
    • ~ GET /libraries/v1/artifacts: param sourceTypes (query) added
    • ~ GET /libraries/v1/artifacts/{id}/versions: param sourceTypes (query) added
    • ~ GET /policies/v1/overrides: response schema changed
    • ~ GET /registry/v1/repos/{repoId}/chart-image-bindings: response schema changed
    • ~ GET /vulnerabilities/v2/advisories/{uid}: response schema changed
    • ~ PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /iam/v2/roles/{uid}: request body changed; response schema changed
    • ~ POST /policies/v1/overrides/{id}: request body changed; response schema changed
    • New endpoint GET /registry/v1/chart-image-bindings
    • New endpoint GET /registry/v2/catalogImages
    • GET /argos/v1/documents: param updatedSince (query) added
    • GET /argos/v1/orgs/{parent}/vulns: param updatedSince (query) added
    • GET /iam/v2/roles/{uid}: response schema changed

    +8 more show less

    • GET /libraries/v1/artifacts: param sourceTypes (query) added
    • GET /libraries/v1/artifacts/{id}/versions: param sourceTypes (query) added
    • GET /policies/v1/overrides: response schema changed
    • GET /registry/v1/repos/{repoId}/chart-image-bindings: response schema changed
    • GET /vulnerabilities/v2/advisories/{uid}: response schema changed
    • PATCH /iam/v2/roles/{uid}: request body changed; response schema changed
    • POST /iam/v2/roles/{uid}: request body changed; response schema changed
    • POST /policies/v1/overrides/{id}: request body changed; response schema changed

    13 details in Everything

76. changelog Aug 26, 2026 · issue 057
    └──▷ HOW TO FIND IT
    Provision a Helm chart for your organization directly from the Console without filing a support ticket.
    📍In the Chainguard Console, go to your organization's Registry, select Helm Charts, choose the desired chart, review the required images identified by the Console, and confirm to start asynchronous provisioning.
    • Chainguard API v2 is now generally available at /v2/, replacing the v2beta1 path prefix, with a stable contract covering organization and access management, registry metadata, vulnerability and security advisories, event subscriptions, and library artifacts; ships an OpenAPIOpenAPIA vendor-neutral specification for describing REST APIs in a machine-readable format, maintained by the OpenAPI Initiative. Cyber tools use it to auto-generate clients, documentation, and validation from a single source of truth. specification and v2 Go SDK clients.
    • API v2 standardizes cursor-based pagination, server-side ordering, resource naming, dedicated resource lookups, partial updates, and typed error details.
    • Supports SCIMSCIMA standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. user provisioning (Early Access) via the /Users resource for Okta and Microsoft Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments.; assigning a user creates/updates their Chainguard provisioning record, and deactivating or unassigning them blocks the next login or token refresh within approximately one hour.
    • Catalog customers can now provision Chainguard Helm charts directly from the Chainguard Console without filing a support ticket; the Console resolves required missing images, adds them in a single request, and provisions the chart asynchronously without EOL tags.
    • Adds 27 new container images this week, including FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants for Airbyte components (airbyte-bootloader, airbyte-cron, airbyte-worker, airbyte-workload-api-server, airbyte-workload-launcher), percona-server-mongodb-fips, commercial-nginx-plus-fips, apache-activemq-artemis-fips, and kubernetes-csi-external-health-monitor-fips, among others.
    └──▷ BREAKING ON UPGRADE

    • !Existing v2beta1 integrations must update their path prefix from /v2beta1/ to /v2/; request and response shapes are preserved.
77. docs update Aug 25, 2026 · issue 056

    Chainguard Catalog Starter now manageable via chainctl with new starter subcommands for signup, access, images, and status.

    └──▷ TRY IT
    Sign up for a new Catalog Starter account without leaving the terminal.
    copy

    $ chainctl starter init

    Add specific images to your Catalog Starter quota after identifying them in the Chainguard Directory.
    copy

    $ chainctl starter add-images python nginx

    Check quota usage and per-image readiness before pulling images in CI.
    copy

    $ chainctl starter status

    • Adds chainctl starter init to sign up for a new Catalog Starter account interactively from the command line.
    • Adds chainctl starter request-access to request access to an existing organization's Catalog Starter plan.
    • Adds chainctl starter add-images to add up to four images (by name) to a Catalog Starter subscription from the CLI.
    • Adds chainctl starter status to display registry path, account provisioning status, image quota usage, and per-image readiness for a Catalog Starter organization.

    4 details in Everything

78. Week of 2026-08-24 Aug 24, 2026 · issue 056

    Chainguard adds SCIMSCIMA standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. user provisioning (Early Access), promotes API v2 to GA, and launches self-serve Helm chart provisioning.

    • Adds SCIM user provisioning (Early Access) for Okta and Microsoft Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. via the /Users SCIM resource — creating/updating provisioning records on assignment and blocking login within ~1 hour of deactivation or token expiry.
    • Promotes Chainguard API v2 to general availability at /v2/, with a stable contract covering organization and access management, registry metadata, vulnerability and security advisories, event subscriptions, and library artifacts; existing v2beta1 integrations need only update the path prefix.
    • Adds cursor-based pagination, server-side ordering, resource naming, dedicated resource lookups, partial updates, and typed error details to the stable API v2, plus an OpenAPIOpenAPIA vendor-neutral specification for describing REST APIs in a machine-readable format, maintained by the OpenAPI Initiative. Cyber tools use it to auto-generate clients, documentation, and validation from a single source of truth. specification and v2 Go SDK clients.
    • Enables self-serve Helm chart provisioning from the Chainguard Console for Catalog customers — resolving required images, adding them in a single request, and provisioning asynchronously without EOL tags.
    • Adds 27 new container images this week including airbyte-bootloader, airbyte-cron, airbyte-worker, airbyte-workload-api-server, airbyte-workload-launcher (all with FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants), percona-server-mongodb-fips, application-gateway-kubernetes-ingress, falcosidekick-ui, kubernetes-csi-external-health-monitor-fips, mlrun, mlrun-api, spiffe-csi-driver, apache-activemq-artemis-fips, aws-iam-controller, commercial-nginx-plus-fips, kserve-lgbserver, and ranger.

    5 details in Everything

79. v1 Aug 20, 2026 · issue 051

    API surface changed: +79 endpoints, −78 endpoints, 14 modified

    API change

    API surface changed: +79 endpoints, −78 endpoints, 14 modified

    • + DELETE /events/v2/subscriptions/{uid}
    • + DELETE /iam/v2/accountAssociations/{uid}
    • + DELETE /iam/v2/externalGroupRoleMappings/{uid}
    • + DELETE /iam/v2/groupInvites/{uid}
    • + DELETE /iam/v2/groups/{uid}
    • + DELETE /iam/v2/identities/{uid}
    • + DELETE /iam/v2/identityProviders/{uid}
    • + DELETE /iam/v2/roleBindings/{uid}
    • + DELETE /iam/v2/roles/{uid}
    • + DELETE /registry/v2/repos/{uid}
    • + DELETE /registry/v2/tags/{uid}
    • + GET /advisory/v2/documents
    • + GET /advisory/v2/images/resolvedVulns
    • + GET /advisory/v2/metadata
    • + GET /events/v2/subscriptions
    • + GET /events/v2/subscriptions/{uid}
    • + GET /iam/v2/accountAssociations
    • + GET /iam/v2/accountAssociations/{uid}
    • + GET /iam/v2/externalGroupRoleMappings
    • + GET /iam/v2/externalGroupRoleMappings/{uid}
    • + GET /iam/v2/groupInvites
    • + GET /iam/v2/groupInvites/{uid}
    • + GET /iam/v2/groups
    • + GET /iam/v2/groups/{uid}
    • + GET /iam/v2/groups:checkEligibility
    • + GET /iam/v2/groups:lookupGroup
    • + GET /iam/v2/identities
    • + GET /iam/v2/identities/{uid}
    • + GET /iam/v2/identities:lookupIdentity
    • + GET /iam/v2/identityProviders
    • + GET /iam/v2/identityProviders/{uid}
    • + GET /iam/v2/roleBindings
    • + GET /iam/v2/roleBindings/{uid}
    • + GET /iam/v2/roles
    • + GET /iam/v2/roles/{uid}
    • + GET /iam/v2/terms/{group}
    • + GET /libraries/v2/artifacts
    • + GET /libraries/v2/artifacts/count
    • + GET /libraries/v2/artifacts/{artifactId}/versions
    • + GET /ping/v2/ping
    • + GET /registry/v1/repotagssummary/{repoId}
    • + GET /registry/v2/repos
    • + GET /registry/v2/repos/{repoReadme.uid}/readme
    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/architectures
    • + GET /registry/v2/repos/{repoUid}/digests/{digest}/size
    • + GET /registry/v2/repos/{uid}
    • + GET /registry/v2/tags
    • + GET /registry/v2/tags/{uid}
    • + GET /vulnerabilities/v2/advisories
    • + GET /vulnerabilities/v2/advisories/{uid}
    • + PATCH /iam/v2/accountAssociations/{uid}
    • + PATCH /iam/v2/groups/{uid}
    • + PATCH /iam/v2/identities/{uid}
    • + PATCH /iam/v2/identities:updateIdentityMetadata
    • + PATCH /iam/v2/identityProviders/{uid}
    • + PATCH /iam/v2/roleBindings/{uid}
    • + PATCH /iam/v2/roles/{uid}
    • + PATCH /registry/v2/repos/{repoReadme.uid}/readme
    • + PATCH /registry/v2/repos/{uid}
    • + POST /events/v2/subscriptions/{uid}
    • + POST /iam/v2/accountAssociations/{uid}
    • + POST /iam/v2/accountAssociations/{uid}:checkAccountAssociation
    • + POST /iam/v2/externalGroupRoleMappings/{uid}
    • + POST /iam/v2/externalGroupRoleMappings:batchDelete
    • + POST /iam/v2/groupInvites/{uid}
    • + POST /iam/v2/groups/{groupUid}:requestGroupAccess
    • + POST /iam/v2/groups/{uid}
    • + POST /iam/v2/identities/{uid}
    • + POST /iam/v2/identityProviders/{identityProviderUid}:generateScimToken
    • + POST /iam/v2/identityProviders/{identityProviderUid}:regenerateScimToken
    • + POST /iam/v2/identityProviders/{identityProviderUid}:revokeScimToken
    • + POST /iam/v2/identityProviders/{identityProviderUid}:setScimEnabled
    • + POST /iam/v2/identityProviders/{uid}
    • + POST /iam/v2/roleBindings/{uid}
    • + POST /iam/v2/roleBindings:batchCreate
    • + POST /iam/v2/roles/{uid}
    • + POST /iam/v2/terms/{group}
    • + POST /registry/v2/repos/{uid}
    • + POST /registry/v2/tags/{uid}
    • ~ GET /iam/v1/identityProviders: response schema changed
    • ~ GET /libraries/v1/artifacts/count: response schema changed
    • ~ GET /libraries/v1/aws-marketplace-subscriptions/{id}: response schema changed
    • ~ GET /libraries/v1/malware/blocklist: param deduplicateResults (query) added
    • ~ GET /libraries/v1/resolutioncache/{parentId}/entries: response schema changed
    • ~ GET /libraries/v1/resolutioncache/{parentId}/status: response schema changed
    • ~ PATCH /libraries/v1/aws-marketplace-subscriptions/{id}: request body changed; response schema changed
    • ~ POST /iam/v1/identityProviders/{id}: request body changed; response schema changed
    • ~ POST /libraries/v1/aws-marketplace-subscriptions/{id}: request body changed; response schema changed
    • ~ POST /libraries/v1/aws-marketplace-subscriptions/{id}:cancel: response schema changed
    • ~ POST /libraries/v1/entitlements/{id}: request body changed
    • ~ POST /libraries/v1/resolutioncache/{parentId}:optout: response schema changed
    • ~ POST /libraries/v1/resolutioncache/{parentId}:zap: response schema changed
    • ~ PUT /iam/v1/identityProviders/{id}: request body changed; response schema changed
    • − DELETE /events/v2beta1/subscriptions/{uid} (breaking)
    • − DELETE /iam/v2beta1/accountAssociations/{uid} (breaking)
    • − DELETE /iam/v2beta1/externalGroupRoleMappings/{uid} (breaking)
    • − DELETE /iam/v2beta1/groupInvites/{uid} (breaking)
    • − DELETE /iam/v2beta1/groups/{uid} (breaking)
    • − DELETE /iam/v2beta1/identities/{uid} (breaking)
    • − DELETE /iam/v2beta1/identityProviders/{uid} (breaking)
    • − DELETE /iam/v2beta1/roleBindings/{uid} (breaking)
    • − DELETE /iam/v2beta1/roles/{uid} (breaking)
    • − DELETE /registry/v2beta1/repos/{uid} (breaking)
    • − DELETE /registry/v2beta1/tags/{uid} (breaking)
    • − GET /advisory/v2beta1/documents (breaking)
    • − GET /advisory/v2beta1/images/resolvedVulns (breaking)
    • − GET /advisory/v2beta1/metadata (breaking)
    • − GET /events/v2beta1/subscriptions (breaking)
    • − GET /events/v2beta1/subscriptions/{uid} (breaking)
    • − GET /iam/v2beta1/accountAssociations (breaking)
    • − GET /iam/v2beta1/accountAssociations/{uid} (breaking)
    • − GET /iam/v2beta1/externalGroupRoleMappings (breaking)
    • − GET /iam/v2beta1/externalGroupRoleMappings/{uid} (breaking)
    • − GET /iam/v2beta1/groupInvites (breaking)
    • − GET /iam/v2beta1/groupInvites/{uid} (breaking)
    • − GET /iam/v2beta1/groups (breaking)
    • − GET /iam/v2beta1/groups/{uid} (breaking)
    • − GET /iam/v2beta1/groups:checkEligibility (breaking)
    • − GET /iam/v2beta1/groups:lookupGroup (breaking)
    • − GET /iam/v2beta1/identities (breaking)
    • − GET /iam/v2beta1/identities/{uid} (breaking)
    • − GET /iam/v2beta1/identities:lookupIdentity (breaking)
    • − GET /iam/v2beta1/identityProviders (breaking)
    • − GET /iam/v2beta1/identityProviders/{uid} (breaking)
    • − GET /iam/v2beta1/roleBindings (breaking)
    • − GET /iam/v2beta1/roleBindings/{uid} (breaking)
    • − GET /iam/v2beta1/roles (breaking)
    • − GET /iam/v2beta1/roles/{uid} (breaking)
    • − GET /iam/v2beta1/terms/{group} (breaking)
    • − GET /libraries/v2beta1/artifacts (breaking)
    • − GET /libraries/v2beta1/artifacts/count (breaking)
    • − GET /libraries/v2beta1/artifacts/{artifactId}/versions (breaking)
    • − GET /ping/v2beta1/ping (breaking)
    • − GET /registry/v2beta1/repos (breaking)
    • − GET /registry/v2beta1/repos/{repoReadme.uid}/readme (breaking)
    • − GET /registry/v2beta1/repos/{repoUid}/digests/{digest}/architectures (breaking)
    • − GET /registry/v2beta1/repos/{repoUid}/digests/{digest}/size (breaking)
    • − GET /registry/v2beta1/repos/{uid} (breaking)
    • − GET /registry/v2beta1/tags (breaking)
    • − GET /registry/v2beta1/tags/{uid} (breaking)
    • − GET /vulnerabilities/v2beta1/advisories (breaking)
    • − GET /vulnerabilities/v2beta1/advisories/{uid} (breaking)
    • − PATCH /iam/v2beta1/accountAssociations/{uid} (breaking)
    • − PATCH /iam/v2beta1/groups/{uid} (breaking)
    • − PATCH /iam/v2beta1/identities/{uid} (breaking)
    • − PATCH /iam/v2beta1/identities:updateIdentityMetadata (breaking)
    • − PATCH /iam/v2beta1/identityProviders/{uid} (breaking)
    • − PATCH /iam/v2beta1/roleBindings/{uid} (breaking)
    • − PATCH /iam/v2beta1/roles/{uid} (breaking)
    • − PATCH /registry/v2beta1/repos/{repoReadme.uid}/readme (breaking)
    • − PATCH /registry/v2beta1/repos/{uid} (breaking)
    • − POST /events/v2beta1/subscriptions/{uid} (breaking)
    • − POST /iam/v2beta1/accountAssociations/{uid} (breaking)
    • − POST /iam/v2beta1/accountAssociations/{uid}:checkAccountAssociation (breaking)
    • − POST /iam/v2beta1/externalGroupRoleMappings/{uid} (breaking)
    • − POST /iam/v2beta1/externalGroupRoleMappings:batchDelete (breaking)
    • − POST /iam/v2beta1/groupInvites/{uid} (breaking)
    • − POST /iam/v2beta1/groups/{groupUid}:requestGroupAccess (breaking)
    • − POST /iam/v2beta1/groups/{uid} (breaking)
    • − POST /iam/v2beta1/identities/{uid} (breaking)
    • − POST /iam/v2beta1/identityProviders/{identityProviderUid}:generateScimToken (breaking)
    • − POST /iam/v2beta1/identityProviders/{identityProviderUid}:regenerateScimToken (breaking)
    • − POST /iam/v2beta1/identityProviders/{identityProviderUid}:revokeScimToken (breaking)
    • − POST /iam/v2beta1/identityProviders/{identityProviderUid}:setScimEnabled (breaking)
    • − POST /iam/v2beta1/identityProviders/{uid} (breaking)
    • − POST /iam/v2beta1/roleBindings/{uid} (breaking)
    • − POST /iam/v2beta1/roleBindings:batchCreate (breaking)
    • − POST /iam/v2beta1/roles/{uid} (breaking)
    • − POST /iam/v2beta1/terms/{group} (breaking)
    • − POST /registry/v2beta1/repos/{uid} (breaking)
    • − POST /registry/v2beta1/tags/{uid} (breaking)
    • New endpoint DELETE /events/v2/subscriptions/{uid}
    • New endpoint DELETE /iam/v2/accountAssociations/{uid}
    • New endpoint DELETE /iam/v2/externalGroupRoleMappings/{uid}
    • New endpoint DELETE /iam/v2/groupInvites/{uid}
    • New endpoint DELETE /iam/v2/groups/{uid}

    +88 more show less

    • New endpoint DELETE /iam/v2/identities/{uid}
    • New endpoint DELETE /iam/v2/identityProviders/{uid}
    • New endpoint DELETE /iam/v2/roleBindings/{uid}
    • New endpoint DELETE /iam/v2/roles/{uid}
    • New endpoint DELETE /registry/v2/repos/{uid}
    • New endpoint DELETE /registry/v2/tags/{uid}
    • New endpoint GET /advisory/v2/documents
    • New endpoint GET /advisory/v2/images/resolvedVulns
    • New endpoint GET /advisory/v2/metadata
    • New endpoint GET /events/v2/subscriptions
    • New endpoint GET /events/v2/subscriptions/{uid}
    • New endpoint GET /iam/v2/accountAssociations
    • New endpoint GET /iam/v2/accountAssociations/{uid}
    • New endpoint GET /iam/v2/externalGroupRoleMappings
    • New endpoint GET /iam/v2/externalGroupRoleMappings/{uid}
    • New endpoint GET /iam/v2/groupInvites
    • New endpoint GET /iam/v2/groupInvites/{uid}
    • New endpoint GET /iam/v2/groups
    • New endpoint GET /iam/v2/groups/{uid}
    • New endpoint GET /iam/v2/groups:checkEligibility
    • New endpoint GET /iam/v2/groups:lookupGroup
    • New endpoint GET /iam/v2/identities
    • New endpoint GET /iam/v2/identities/{uid}
    • New endpoint GET /iam/v2/identities:lookupIdentity
    • New endpoint GET /iam/v2/identityProviders
    • New endpoint GET /iam/v2/identityProviders/{uid}
    • New endpoint GET /iam/v2/roleBindings
    • New endpoint GET /iam/v2/roleBindings/{uid}
    • New endpoint GET /iam/v2/roles
    • New endpoint GET /iam/v2/roles/{uid}
    • New endpoint GET /iam/v2/terms/{group}
    • New endpoint GET /libraries/v2/artifacts
    • New endpoint GET /libraries/v2/artifacts/count
    • New endpoint GET /libraries/v2/artifacts/{artifactId}/versions
    • New endpoint GET /ping/v2/ping
    • New endpoint GET /registry/v1/repotagssummary/{repoId}
    • New endpoint GET /registry/v2/repos
    • New endpoint GET /registry/v2/repos/{repoReadme.uid}/readme
    • New endpoint GET /registry/v2/repos/{repoUid}/digests/{digest}/architectures
    • New endpoint GET /registry/v2/repos/{repoUid}/digests/{digest}/size
    • New endpoint GET /registry/v2/repos/{uid}
    • New endpoint GET /registry/v2/tags
    • New endpoint GET /registry/v2/tags/{uid}
    • New endpoint GET /vulnerabilities/v2/advisories
    • New endpoint GET /vulnerabilities/v2/advisories/{uid}
    • New endpoint PATCH /iam/v2/accountAssociations/{uid}
    • New endpoint PATCH /iam/v2/groups/{uid}
    • New endpoint PATCH /iam/v2/identities/{uid}
    • New endpoint PATCH /iam/v2/identities:updateIdentityMetadata
    • New endpoint PATCH /iam/v2/identityProviders/{uid}
    • New endpoint PATCH /iam/v2/roleBindings/{uid}
    • New endpoint PATCH /iam/v2/roles/{uid}
    • New endpoint PATCH /registry/v2/repos/{repoReadme.uid}/readme
    • New endpoint PATCH /registry/v2/repos/{uid}
    • New endpoint POST /events/v2/subscriptions/{uid}
    • New endpoint POST /iam/v2/accountAssociations/{uid}
    • New endpoint POST /iam/v2/accountAssociations/{uid}:checkAccountAssociation
    • New endpoint POST /iam/v2/externalGroupRoleMappings/{uid}
    • New endpoint POST /iam/v2/externalGroupRoleMappings:batchDelete
    • New endpoint POST /iam/v2/groupInvites/{uid}
    • New endpoint POST /iam/v2/groups/{groupUid}:requestGroupAccess
    • New endpoint POST /iam/v2/groups/{uid}
    • New endpoint POST /iam/v2/identities/{uid}
    • New endpoint POST /iam/v2/identityProviders/{identityProviderUid}:generateScimToken
    • New endpoint POST /iam/v2/identityProviders/{identityProviderUid}:regenerateScimToken
    • New endpoint POST /iam/v2/identityProviders/{identityProviderUid}:revokeScimToken
    • New endpoint POST /iam/v2/identityProviders/{identityProviderUid}:setScimEnabled
    • New endpoint POST /iam/v2/identityProviders/{uid}
    • New endpoint POST /iam/v2/roleBindings/{uid}
    • New endpoint POST /iam/v2/roleBindings:batchCreate
    • New endpoint POST /iam/v2/roles/{uid}
    • New endpoint POST /iam/v2/terms/{group}
    • New endpoint POST /registry/v2/repos/{uid}
    • New endpoint POST /registry/v2/tags/{uid}
    • GET /iam/v1/identityProviders: response schema changed
    • GET /libraries/v1/artifacts/count: response schema changed
    • GET /libraries/v1/aws-marketplace-subscriptions/{id}: response schema changed
    • GET /libraries/v1/malware/blocklist: param deduplicateResults (query) added
    • GET /libraries/v1/resolutioncache/{parentId}/entries: response schema changed
    • GET /libraries/v1/resolutioncache/{parentId}/status: response schema changed
    • PATCH /libraries/v1/aws-marketplace-subscriptions/{id}: request body changed; response schema changed
    • POST /iam/v1/identityProviders/{id}: request body changed; response schema changed
    • POST /libraries/v1/aws-marketplace-subscriptions/{id}: request body changed; response schema changed
    • POST /libraries/v1/aws-marketplace-subscriptions/{id} response schema changed
    • POST /libraries/v1/entitlements/{id}: request body changed
    • POST /libraries/v1/resolutioncache/{parentId} response schema changed
    • POST /libraries/v1/resolutioncache/{parentId} response schema changed
    • PUT /iam/v1/identityProviders/{id}: request body changed; response schema changed

    93 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Removed endpoint DELETE /events/v2beta1/subscriptions/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/accountAssociations/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/externalGroupRoleMappings/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/groupInvites/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/groups/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/identities/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/identityProviders/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/roleBindings/{uid}
    • !Removed endpoint DELETE /iam/v2beta1/roles/{uid}
    • !Removed endpoint DELETE /registry/v2beta1/repos/{uid}
    • !Removed endpoint DELETE /registry/v2beta1/tags/{uid}
    • !Removed endpoint GET /advisory/v2beta1/documents
    • !Removed endpoint GET /advisory/v2beta1/images/resolvedVulns
    • !Removed endpoint GET /advisory/v2beta1/metadata
    • !Removed endpoint GET /events/v2beta1/subscriptions
    • !Removed endpoint GET /events/v2beta1/subscriptions/{uid}
    • !Removed endpoint GET /iam/v2beta1/accountAssociations
    • !Removed endpoint GET /iam/v2beta1/accountAssociations/{uid}
    • !Removed endpoint GET /iam/v2beta1/externalGroupRoleMappings
    • !Removed endpoint GET /iam/v2beta1/externalGroupRoleMappings/{uid}
    • !Removed endpoint GET /iam/v2beta1/groupInvites
    • !Removed endpoint GET /iam/v2beta1/groupInvites/{uid}
    • !Removed endpoint GET /iam/v2beta1/groups
    • !Removed endpoint GET /iam/v2beta1/groups/{uid}
    • !Removed endpoint GET /iam/v2beta1/groups:checkEligibility
    • !Removed endpoint GET /iam/v2beta1/groups:lookupGroup
    • !Removed endpoint GET /iam/v2beta1/identities
    • !Removed endpoint GET /iam/v2beta1/identities/{uid}
    • !Removed endpoint GET /iam/v2beta1/identities:lookupIdentity
    • !Removed endpoint GET /iam/v2beta1/identityProviders
    • !Removed endpoint GET /iam/v2beta1/identityProviders/{uid}
    • !Removed endpoint GET /iam/v2beta1/roleBindings
    • !Removed endpoint GET /iam/v2beta1/roleBindings/{uid}
    • !Removed endpoint GET /iam/v2beta1/roles
    • !Removed endpoint GET /iam/v2beta1/roles/{uid}
    • !Removed endpoint GET /iam/v2beta1/terms/{group}
    • !Removed endpoint GET /libraries/v2beta1/artifacts
    • !Removed endpoint GET /libraries/v2beta1/artifacts/count
    • !Removed endpoint GET /libraries/v2beta1/artifacts/{artifactId}/versions
    • !Removed endpoint GET /ping/v2beta1/ping
    • !Removed endpoint GET /registry/v2beta1/repos
    • !Removed endpoint GET /registry/v2beta1/repos/{repoReadme.uid}/readme
    • !Removed endpoint GET /registry/v2beta1/repos/{repoUid}/digests/{digest}/architectures
    • !Removed endpoint GET /registry/v2beta1/repos/{repoUid}/digests/{digest}/size
    • !Removed endpoint GET /registry/v2beta1/repos/{uid}
    • !Removed endpoint GET /registry/v2beta1/tags
    • !Removed endpoint GET /registry/v2beta1/tags/{uid}
    • !Removed endpoint GET /vulnerabilities/v2beta1/advisories
    • !Removed endpoint GET /vulnerabilities/v2beta1/advisories/{uid}
    • !Removed endpoint PATCH /iam/v2beta1/accountAssociations/{uid}
    • !Removed endpoint PATCH /iam/v2beta1/groups/{uid}
    • !Removed endpoint PATCH /iam/v2beta1/identities/{uid}
    • !Removed endpoint PATCH /iam/v2beta1/identities:updateIdentityMetadata
    • !Removed endpoint PATCH /iam/v2beta1/identityProviders/{uid}
    • !Removed endpoint PATCH /iam/v2beta1/roleBindings/{uid}
    • !Removed endpoint PATCH /iam/v2beta1/roles/{uid}
    • !Removed endpoint PATCH /registry/v2beta1/repos/{repoReadme.uid}/readme
    • !Removed endpoint PATCH /registry/v2beta1/repos/{uid}
    • !Removed endpoint POST /events/v2beta1/subscriptions/{uid}
    • !Removed endpoint POST /iam/v2beta1/accountAssociations/{uid}
    • !Removed endpoint POST /iam/v2beta1/accountAssociations/{uid}:checkAccountAssociation
    • !Removed endpoint POST /iam/v2beta1/externalGroupRoleMappings/{uid}
    • !Removed endpoint POST /iam/v2beta1/externalGroupRoleMappings:batchDelete
    • !Removed endpoint POST /iam/v2beta1/groupInvites/{uid}
    • !Removed endpoint POST /iam/v2beta1/groups/{groupUid}:requestGroupAccess
    • !Removed endpoint POST /iam/v2beta1/groups/{uid}
    • !Removed endpoint POST /iam/v2beta1/identities/{uid}
    • !Removed endpoint POST /iam/v2beta1/identityProviders/{identityProviderUid}:generateScimToken
    • !Removed endpoint POST /iam/v2beta1/identityProviders/{identityProviderUid}:regenerateScimToken
    • !Removed endpoint POST /iam/v2beta1/identityProviders/{identityProviderUid}:revokeScimToken
    • !Removed endpoint POST /iam/v2beta1/identityProviders/{identityProviderUid}:setScimEnabled
    • !Removed endpoint POST /iam/v2beta1/identityProviders/{uid}
    • !Removed endpoint POST /iam/v2beta1/roleBindings/{uid}
    • !Removed endpoint POST /iam/v2beta1/roleBindings:batchCreate
    • !Removed endpoint POST /iam/v2beta1/roles/{uid}
    • !Removed endpoint POST /iam/v2beta1/terms/{group}
    • !Removed endpoint POST /registry/v2beta1/repos/{uid}
    • !Removed endpoint POST /registry/v2beta1/tags/{uid}
80. docs update Aug 18, 2026 · issue 049

    Chainguard adds an Agent Skills Public Skills MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server with five tools for searching, inspecting, and running hardened images.

81. docs update Aug 18, 2026 · issue 049

    Chainguard launches a Public Skills MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server at skills.cgr.dev/mcp with five tools for agents to search, inspect, and run hardened skills

    └──▷ TRY IT
    Add the hardened skill catalog to Claude Code so it is available across all your projects and authenticate via OAuth.
    copy

    $ claude mcp add --transport http --scope user cgr-skills https://skills.cgr.dev/mcp
    claude
    /mcp

    Share the Public Skills MCP server with everyone working in a repo by committing a project-scoped config file.
    .mcp.json copy

    {
      "mcpServers": {
        "cgr-skills": {
          "type": "http",
          "url": "https://skills.cgr.dev/mcp"
        }
      }
    }

    • New Public Skills MCP server reachable at https://skills.cgr.dev/mcp over Streamable HTTPStreamable HTTPAn MCP transport protocol that lets a client send JSON-RPC requests over HTTP POST while the server streams responses back using Server-Sent Events, replacing the older stdio and SSE transports for remote tool communication. with OAuth 2.0OAuth 2.0An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms., letting any MCP-capable agent discover and load hardened agent skills without a separate install step.
    • Exposes five MCP tools — search_skills, list_skills, read_skill, read_skill_reference, and run_skill — covering ranked keyword search, paginated catalog browsing, skill manifest inspection, single-file fetching, and full skill bundle loading.
    • search_skills accepts query (required), page_size (default 50, max 200), and page_token parameters, returning ranked { name, description } matches plus next_page_token and total; signals the agent to ask before sourcing skills outside the hardened catalog when no match is found.
    • run_skill loads a skill's full bundle — SKILL.md plus all scripts and references — in a single call, returning { name, files, instructions } keyed by relative path; preferred over chaining read_skill + repeated read_skill_reference when execution is intended.
    • read_skill_reference fetches a single supporting file (script, doc, or template) by name and path relative to the skill directory; path-traversal attempts (e.g. ../another-skill/...) are rejected.

    +3 more show less

    • list_skills paginates the entire catalog as name + description with page_size (default 50, max 200) and page_token parameters; an empty next_page_token signals the last page.
    • Supports adding the server to Claude Code via claude mcp add --transport http --scope user cgr-skills https://skills.cgr.dev/mcp, with local, project, and user scope options; project-wide sharing is done by committing .mcp.json at the repo root.
    • Skills served are sourced from skills.cgr.dev/public (upstream hardened skills) and skills.cgr.dev/chainguard (Chainguard-authored skills), pinned to the upstream commit they were hardened from.

    8 details in Everything

82. v1 Aug 17, 2026 · issue 048

    Chainguard now publishes an API — 260 endpoints across 59 areas: Registry, Registryentitlements, Identityprovidersservice, …

    • Registry (33 endpoints) — create, read, update, delete
    • Registryentitlements (11 endpoints) — Registry Entitlements API
    • Identityprovidersservice (9 endpoints) — create, read, update, delete
    • Groupsservice (8 endpoints) — create, read, update, delete
    • Identityproviders (8 endpoints) — create, read, update, delete

    +4 more show less

    • Advisories (7 endpoints) — create, read, update, delete
    • Groups (7 endpoints) — create, read, update, delete
    • Identitiesservice (7 endpoints) — create, read, update, delete
    • 51 more areas: Reposservice, Accountassociationsservice, Policies, Rolebindingsservice, Awsmarketplacesubscriptions, Actionsauthorization, Externalgrouprolemappings, Externalgrouprolemappingsservice, Groupaccountassociations, Iamidentities, Rolebindings, Rolesservice, Argosdocuments, Argososv, Auth, Bindings, Groupinvitesservice, Librariesresolutioncache, Librarypolicies, Librarypolicybindings, Roles, Subscriptionsservice, Tagsservice, Vulnerabilities, Artifacts, Artifactsservice, Groupinvites, Librariesentitlements, Overrides, Securityadvisory, Securityadvisoryservice, Securitytokenservice, Skillsentitlements, Subscriptions, Apk, Advisoriesservice, Apko, Argosvulns, Charts, Imagesservice, Npmpackages, Pingservice, Terms, Termsservice, Actions, Decisions, Eventidentities, Imagematcher, Librarypolicyblockevents, Malware, Packagesentitlements

    9 details in Everything

83. Week of 2026-08-17 Aug 17, 2026 · issue 049

    Chainguard adds npm 403 error codes for blocked packages, GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. migration via Guardener, and build pinning for Libraries cache.

    └──▷ TRY IT
    Check which copy (upstream mirror vs. Chainguard rebuild) your org has pinned for each cached package version, to audit lockfile consistency before the August 24 build-pinning cutover.
    copy

    $ chainctl libraries cache list

    Opt out of build pinning for the npm ecosystem if your org relies on receiving the latest Chainguard rebuild of a version rather than staying on the first copy resolved.
    copy

    $ chainctl libraries cache opt-out --ecosystem javascript

    • Chainguard Libraries now returns a 403 HTTP status with a named reason code (e.g., MALWARE_DETECTED) when npm requests a blocked package or version, replacing the previously unexplained 404.
    • Chainguard Guardener GitHub App (beta) extends automated migration to GitHub Actions: inventories Actions across org repositories, maps them to hardened Chainguard equivalents, and opens pull requests pinned to a specific SHA rather than a mutable tag.
    • Guardener runs in two modes: an upfront pass that surfaces existing Actions usage and opens migration PRs, and an ongoing standardization mode that watches workflow files and suggests equivalents as new upstream Actions appear.
    • New chainctl libraries cache build-pinning feature records which copy (upstream mirror or Chainguard rebuild) an org first received for a package version and keeps resolving that version to the same copy, preventing EINTEGRITY checksum mismatches in npm.
    • Adds chainctl libraries cache opt-out and chainctl libraries cache opt-in commands, both accepting --ecosystem, to control per-organization, per-ecosystem pinning behavior.

    +2 more show less

    • Adds chainctl libraries cache list to show which copy (upstream or Chainguard rebuild) each held version was sourced from.
    • Adds 17 new container images including azurite, k0s-cni-node, peerdb-ui, scc, zitadel-login, aws-lambda-nodejs, localstack, kserve-router-fips, jdk-openssl-fips, jre-openssl-fips, kube-router, and commercial-nginx-ingress-plus, with FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. variants available for several.

    7 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !As of August 24, 2026, Chainguard Libraries build pinning is enabled by default for organizations using Chainguard Libraries with upstream fallback (JavaScript, Python, and Java ecosystems): the first copy of a package version an org downloads is locked in, and subsequent resolutions will no longer silently switch between the upstream mirror and a Chainguard rebuild. To preserve the previous behavior (no pinning), run chainctl libraries cache opt-out. Organizations without upstream fallback are unaffected.
    • !The prometheus:3.9 container image is no longer available as of 2026-08-17 (grace period ended).
84. Week of 2026-08-10 Aug 10, 2026 · issue 048

    Chainguard adds AWS Security Hub Extended integration, console malware visibility, PKCEPKCEProof Key for Code Exchange, an OAuth safeguard that binds an authorization code to the client that requested it. An intercepted code cannot be redeemed without the client's matching verifier. for custom IdPs, and 23 new container images.

    └──▷ HOW TO FIND IT
    Review malware and greyware blocked across your Libraries-entitled organization directly in the Console.
    📍In the Console, go to Libraries › Malware tab to view the weekly blocked-package chart and search for any flagged package to see the reason it was marked unsafe.
    • Adds Chainguard Libraries distribution through AWS Security Hub Extended, with findings normalized to the Open Cybersecurity Schema Framework (OCSFOCSFAn open schema standard, maintained by the OCSF community under CISA and industry backing, that defines a common event format so cyber tools can share and ingest log data without per-source normalization work.) and AWS Enterprise Support (Level 1) for eligible customers; subscribe and pay via existing AWS account from the Security Hub console.
    • New Malware tab in the Libraries section of the Console (beta) shows malicious and suspicious packages blocked before reaching your environment, with a weekly chart covering Python and JavaScript ecosystems and a per-package search explaining why a package was flagged; enabled by default for all Libraries-entitled organizations.
    • Adds Proof Key for Code ExchangeProof Key for Code ExchangeProof Key for Code Exchange, an OAuth safeguard that binds an authorization code to the client that requested it. An intercepted code cannot be redeemed without the client's matching verifier. (PKCE) support for the OAuth token exchangeOAuth token exchangeAn OAuth 2.0 extension (RFC 8693) that lets a service swap one token for another with different scopes, audience, or type, so cyber tools can delegate access across service boundaries without re-authenticating the user. with custom OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. (aligned with OAuth 2.1OAuth 2.1A consolidated draft of the OAuth authorization framework that merges OAuth 2.0 with its most important security BCP updates, dropping unsafe flows so tools can delegate user access without handling credentials directly.), configurable via chainctl or the Chainguard API, usable alongside an existing client secret or as a secret-free public client.
    • Adds 23 new container images including prometheus-stackdriver-exporter (+FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments.), crossplane-azure-keyvault, crossplane-azure-kusto, influxdb-fips, moodle-iamguarded, pypiserver-fips, kubevirt-cdi-cloner (+FIPS), yopass, acm-controller (+FIPS), gremlin-server, rollouts-plugin-trafficrouter-gatewayapi (+FIPS), claude, codex, cruise-control (+FIPS), dotstatsuite-supercore, opencode, and zalando-pgbouncer (+FIPS).

    4 details in Everything

85. Week of 2026-08-03 Aug 3, 2026 · release notes

    18 new container images including atlas and crossplane-azure variants; ingress-nginx entrypoint/user changes.

    • Adds atlas, azure-metrics-exporter, crossplane-azure-solutions, crossplane-azure-streamanalytics, crossplane-azure-web, dns-controller-manager, instrumentisto-haraka, openstack-kolla-toolbox, sftpgo, traccar, and metacontroller-fips as new container images.
    • Adds flink-kubernetes-operator-fips as a new FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. tier container image.
    • Changes ingress-nginx-controller entrypoint, command, and default runtime user to www-data (UID 101) for non-iamguarded variants.
    • Initiates grace period for end-of-life images eks-distro:1.33, mongo:8.2, prometheus:3.5, cockroach:26.1, and cockroach-openssl:26.1.

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The default runtime user for non-iamguarded ingress-nginx-controller variants is changed from root (UID 0) to www-data (UID 101).
86. Week of 2026-07-28 Jul 28, 2026 · release notes

    SUSE NeuVector native support for Chainguard Containers; Group-based role mapping GA

    • Adds native support in SUSE NeuVector vulnerability scanner to ingest Chainguard’s OSVOSVOpen Source Vulnerabilities, a vulnerability database and schema maintained by Google that gives cyber tools a machine-readable, cross-ecosystem format for querying and sharing CVE-style advisories. advisory feed for Chainguard Container images, suppressing false positives and reporting more accurate results.
    • Enables group-based role mapping to identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. (Okta, Microsoft Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments.), allowing administrators to map groups directly to Chainguard roles so all users in the group receive that role for the session.
    • Adds 15 new container images this week: coder (+fips), flink-kubernetes-operator, pghero (+fips), kargo, nuclio-controller (+fips), phpmyadmin (+fips), apache-exporter-iamguarded, glab (+fips), metabase, crossplane-azure-relay.

    3 details in Everything