Skip to content

CI: gitleaks secret-scan (BYO-keys trust signal) #13

Closed

Description

@ernestprovo23

For a BYO-keys tool whose entire pitch is "never leak keys," a secret-scan step is on-brand, cheap, and a trust signal. mcp-warden already runs gitleaks in CI.

Scope

  • Add a gitleaks GitHub Action on PRs.
  • Config is keys-free by construction, so it should find nothing — this is a guardrail/parity item.

Acceptance

  • gitleaks runs on PRs and reports no secrets.

Source: pre-dev planning audit 2026-06-08 (finding C-4).

Activity

  1. added
    ciCI/CD, test infra, lint, secret-scan
    securityKey handling, leak prevention, secrets
    on Jun 8, 2026
  2. ernestprovo23 commented on Jun 9, 2026

    @ernestprovo23
    MemberAuthor

    Done — gitleaks secret-scan workflow landed in PR #26 (hard-fail; BYO-keys trust signal).

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    ciCI/CD, test infra, lint, secret-scansecurityKey handling, leak prevention, secrets

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions