ci: replace gitleaks action with pinned, verified CLI in secret-scan

DO
4h ago
+112-10

User description

Problem

[Fleet Monitor] combsmith/google-app-scripts — .github/workflows/ci.yml

From the issue: | Metric | Value | |---|---| | Failure Rate | 16.7% (1 / 6 runs) | | Status | WARNING | | p50 Duration | 254s | | p95 Duration | 555s | | Successful Runs | 5 | | Cancelled Runs | 0 |

Risk

Medium — changes GitHub Actions workflow behavior, which is exercised only post-merge; verify via the affected workflow runs.

Test plan

Tests added/updated: scripts/tests/ci-workflow.test.js. Verification: bash scripts/dev-lead-lint.sh (shellcheck --severity=warning) ran pre-commit; the bats suite runs in CI.

Rollback

Revert this PR. No non-revertible side effects (no tags, migrations, or external state).

Monitoring

Watch the affected workflow run(s) in the Actions tab and this PR's Lint check for regressions.

Closes #679

Summary by CodeRabbit

  • Chores
    • Updated automated secret scanning to use a checksum-verified scanner. Scans redact detected secrets, cover the full repository history, and fail when findings are present. The scanning job uses read-only repository access.
  • Tests
    • Automated checks now run the project’s test suite.
    • Added checks for scanner verification, full-history scan coverage, redaction, failure behavior, and workflow permissions.

CodeAnt-AI Description

Allow secret scans to run on Dependabot pull requests

What Changed

  • Replaced the license-dependent scan action with a pinned gitleaks release verified before installation, so scans do not rely on Actions secrets.
  • The scan still checks full repository history, fails when it finds secrets, and redacts findings.
  • Removed the scan’s unnecessary security-events write permission.

Impact

✅ Dependabot pull requests can run the required secret scan
✅ Secret scanning no longer requires a Gitleaks license secret
✅ Secret findings remain fully redacted

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.