compliance-scanner-agent

4 Commits

Include renames

Author	SHA1	Message	Date
Sharang ParnerkarandClaude Fable 5	fda91b6e29	fix(ci): authenticate tramiton fetch in dashboard + mcp image builds CI / Check (pull_request) Successful in 5m12s Details CI / Detect Changes (pull_request) Has been skipped Details CI / Deploy Agent (pull_request) Has been skipped Details CI / Deploy Dashboard (pull_request) Has been skipped Details CI / Deploy Docs (pull_request) Has been skipped Details CI / Deploy MCP (pull_request) Has been skipped Details The main deploy after #145 failed on Deploy Dashboard and Deploy MCP: because compliance-agent (a workspace member) depends on the private tramiton-core git repo, cargo/dx must resolve it even when building the dashboard or mcp — and those Dockerfiles had no git auth ("unknown SSH host key"). Deploy Agent (fixed in #143) succeeded. Apply the same BuildKit-secret fix to Dockerfile.dashboard (dx build) and Dockerfile.mcp (cargo build), and pass the secret in the deploy-dashboard and deploy-mcp jobs. Dockerfile.docs is node-only and unaffected. Refs #118. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-12 23:43:13 +02:00
Sharang ParnerkarandClaude Opus 4.6	69209649a5	ci: trigger first orca build for all services CI / Check (push) Has been skipped Details CI / Deploy Agent (push) Successful in 7m5s Details CI / Deploy Dashboard (push) Failing after 21m28s Details CI / Detect Changes (push) Successful in 4s Details CI / Deploy Docs (push) Successful in 30s Details CI / Deploy MCP (push) Successful in 1m31s Details Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-08 10:10:07 +02:00
Sharang ParnerkarandClaude Opus 4.6	689daa0f49	chore: upgrade Dockerfiles to Rust 1.94 CI / Security Audit (push) Successful in 1m48s Details CI / Tests (push) Successful in 5m30s Details CI / Detect Changes (push) Successful in 8s Details CI / Deploy Agent (push) Successful in 2s Details CI / Deploy Dashboard (push) Successful in 2s Details CI / Deploy Docs (push) Has been skipped Details CI / Deploy MCP (push) Failing after 3s Details CI / Format (push) Successful in 4s Details CI / Clippy (push) Successful in 4m42s Details Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-11 13:15:47 +01:00
sharangandSharang Parnerkar	32e5fc21e7	feat: add MCP server for exposing compliance data to LLMs (#5 ) CI / Format (push) Successful in 3s Details CI / Clippy (push) Successful in 4m4s Details CI / Security Audit (push) Successful in 1m42s Details CI / Tests (push) Successful in 4m38s Details CI / Deploy Agent (push) Successful in 2s Details CI / Deploy Dashboard (push) Successful in 1s Details CI / Deploy MCP (push) Failing after 2s Details CI / Detect Changes (push) Successful in 7s Details CI / Deploy Docs (push) Successful in 2s Details New `compliance-mcp` crate providing a Model Context Protocol server with 7 tools: list/get/summarize findings, list SBOM packages, SBOM vulnerability report, list DAST findings, and DAST scan summary. Supports stdio (local dev) and Streamable HTTP (deployment via MCP_PORT). Includes Dockerfile, CI clippy check, and Coolify deploy job. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Sharang Parnerkar <parnerkarsharang@gmail.com> Reviewed-on: #5	2026-03-09 08:21:04 +00:00