ci: add automated SBOM generation with anchore/sbom-action - #839
Merged
Conversation
|
@AnzalKhan16 is attempting to deploy a commit to the Nitya Gosain's projects Team on Vercel. A member of the Team first needs to authorize it. |
Nitya-003
added
enhancement
Nitya-003
approved these changes
Jul 29, 2026
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
2 participants
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.
📌 Overview
Integrated automated Software Bill of Materials (SBOM) generation into our CI pipeline using the
anchore/sbom-action. This ensures we maintain full visibility into our software supply chain and third-party dependencies. The generated SPDX-formatted SBOM is automatically uploaded as a GitHub Actions artifact on every build. I have also added documentation for this process inSECURITY.md.🛠️ Type of Change
[ ] ⛓️ Smart Contract (Solidity changes, Gas optimization)
[ ] 💻 Frontend (UI/UX, React components, Tailwind)
[ ] ⚙️ Backend (API routes, MongoDB schemas, Middleware)
[x] 📄 Documentation (README, Roadmap updates, SECURITY.md)
[x] 🧪 Testing (Hardhat tests, Jest/Vitest, CI/CD Pipeline & Supply Chain Security)
🔗 Related Issue
Closes #838
🧪 Testing & Verification
Smart Contracts: npx hardhat test passed? (NA)
Frontend: Verified on Mobile/Desktop responsiveness? (NA)
Integration: Verified ethers.js connectivity with local/testnet node? (NA)
📸 Screenshots / Demos
(N/A - CI configuration updates only)
✅ PR Checklist
[x] My code follows the project's style guidelines.
[x] I have commented my code, particularly in complex areas (e.g., Smart Contract logic).
[x] I have updated the documentation accordingly.
[x] My changes generate no new warnings.