Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is some responsive security hardening against the class of attack we just saw here: https://www.aikido.dev/blog/telnyx-pypi-compromised-teampcp-canisterworm
Pin all GitHub Actions to commit SHAs — every action in docs.yml and the new zizmor.yml is
pinned to a verified, GPG-signed commit that predates the March 19 attack window. Tags kept
as comments for readability.
Scope workflow permissions — pages:write and id-token:write moved from top-level down to
just the deploy job. The build job (which installs the full pixi env) now only has
contents:read
Dependency cooldown — added exclude-newer = "2026-03-16T00:00:00Z" to pixi.toml so the
solver can't pull in packages published during/after the attack window, even when re-solving
the lockfile - note that with feat: Relative exclude-newer configuration prefix-dev/pixi#5786 being merged we will shift to a relative-time approach which will be a bit more user-friendly, but this is very conservative in the sense that any attempted updatw will just kick and require the user to update this hardcoded datetime.
Pin devcontainer base image — ghcr.io/prefix-dev/pixi image pinned to its digest so the tag
can't be swapped out by a bad actor one day
Dependabot for Actions — new .github/dependabot.yml with monthly updates and a 14-day
cooldown on new releases, which is maybe overly conservative but I'm a bit spooked!
Zizmor audit workflow — new CI workflow that runs a GitHub Actions security audit on any
workflow file changes, results go to the Security tab!