Skip to content

ci: supply chain scanning, Docker builds, and documentation - #148

Open
morgonpeters-cyber wants to merge 4 commits into
RWA-ToolKit:mainfrom
morgonpeters-cyber:fix/ci-supply-chain-and-docs
Open

ci: supply chain scanning, Docker builds, and documentation#148
morgonpeters-cyber wants to merge 4 commits into
RWA-ToolKit:mainfrom
morgonpeters-cyber:fix/ci-supply-chain-and-docs

Conversation

@morgonpeters-cyber

Copy link
Copy Markdown

Summary

Implements four fixes for CI/CD and documentation gaps:

  1. Supply chain scanning — Add cargo audit to catch known vulnerabilities
  2. Docker build verification — Build Docker image in CI to catch Dockerfile regressions early
  3. Cargo.lock handling — Ensure Cargo.lock is copied during Docker builds for reproducible builds
  4. CI status aggregation — Add always-run check-status job so branch protection can require a single stable status

Changes

  • .github/workflows/api.yml: Add cargo audit step, Docker build, and check-status aggregator job
  • .github/workflows/docs.yml: Add check-status aggregator job for consistent status reporting
  • api/Dockerfile: Copy Cargo.lock if present to ensure dependency consistency
  • README.md: Expand repository layout section with detailed build commands and project structure

Testing

  • All changes are CI configuration and documentation; no runtime code changes
  • Docker build step will validate Dockerfile syntax and dependencies
  • cargo audit will report any known vulnerabilities

Closes #82
Closes #84
Closes #81
Closes #83

Add cargo audit step to catch known vulnerabilities in dependencies.
Also add Docker image build step to catch Dockerfile regressions early.

Closes RWA-ToolKit#82
Copy Cargo.lock if it exists to prevent dependency resolution changes
between build stages and ensure reproducible builds.

Closes RWA-ToolKit#81
Add check-status job to both api and docs workflows that always reports
a status regardless of whether the path filter triggers. This enables
branch protection to require a single stable status check that applies
to all PRs.

Closes RWA-ToolKit#83
Expand repository layout section with clear descriptions of both api/
and docs/ subprojects, their purposes, build/development commands,
and directory structures. Helps new contributors understand the dual
project setup.

Closes RWA-ToolKit#84
@drips-wave

drips-wave Bot commented Jul 26, 2026

Copy link
Copy Markdown

@morgonpeters-cyber Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment