feat: add npm provenance statements for enhanced supply chain security#5014
Merged
feat: add npm provenance statements for enhanced supply chain security#5014
Conversation
- Add publishConfig.provenance: true to all 25 publishable packages - Update GitHub Actions workflows with required permissions: - attestations: write for artifact attestations - id-token: write for OIDC token generation (Sigstore signing) - Enable SLSA-compliant cryptographic proof of package build origin - Enhance supply chain security with verifiable build attestations Affects: All @reown/appkit packages and adapters Testing: Verified with successful pnpm typecheck and build 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
10 Skipped Deployments
|
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR implements npm provenance statements across all publishable packages in the AppKit monorepo to enhance supply chain security by adding cryptographic proof that packages were built from this specific GitHub repository.
- Adds
publishConfig.provenance: trueto 25 package.json files for all publishable packages - Updates GitHub Actions workflows with required permissions for provenance generation
- Provides SLSA-compliant attestations using Sigstore signatures without breaking existing workflows
Reviewed Changes
Copilot reviewed 27 out of 27 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/*/package.json | Added provenance configuration to 25 publishable packages |
| .github/workflows/release-publish.yml | Added attestations write permission for provenance |
| .github/workflows/publish-prerelease.yml | Added attestations write permission for provenance |
| .github/workflows/release-canary.yml | Added full permissions block with id-token and attestations write |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Contributor
|
Contributor
Coverage Report
File CoverageNo changed files found. |
tomiir
approved these changes
Sep 12, 2025
arein
approved these changes
Sep 12, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
This PR implements npm provenance statements across all publishable packages in the AppKit monorepo to enhance supply chain security.
Changes Made
✅ 25 package.json files updated with
publishConfig.provenance: true/packages/directory (19 packages)/packages/adapters/(5 packages)@reown/appkitpackage✅ 3 GitHub Actions workflows updated with required permissions:
release-publish.yml- Addedattestations: writepublish-prerelease.yml- Addedattestations: writerelease-canary.yml- Added full permissions block withid-token: writeandattestations: writeSecurity Benefits
Technical Details
Test Plan
pnpm typecheckpnpm buildWhat happens next
When packages are published via GitHub Actions, they will automatically include provenance statements that show exactly where and how they were built, enhancing trust and security for all AppKit consumers.