Compliance: secret_scanning_ai_detection

[don-petry]

Compliance Finding

Category: push-protection
Severity: warning
Check: secret_scanning_ai_detection

Detail

Secret scanning AI detection should be enabled (current: null, expected: enabled)

Standard Reference

standards/push-protection.md#required-repo-level-settings

Remediation

Please review the linked standard and bring this repository into compliance.

See the full standards documentation for implementation guidance.

---

This issue was automatically created by the weekly compliance audit.

[don-petry]

Weekly Compliance Audit (2026-05-29)

This finding is still open.

Detail: Secret scanning AI detection should be enabled (current: null, expected: enabled)

Standard: standards/push-protection.md#required-repo-level-settings

[don-petry]

Dev-Lead Implementation Plan

Issue: #335 — Compliance: secret_scanning_ai_detection

Scope

Add the missing secret_scanning_ai_detection: enabled entry to .github/settings.yml so the probot/settings bot enables the feature on the repository.

Implementation Checklist

• Add secret_scanning_ai_detection with status: enabled under repository.security_and_analysis in .github/settings.yml

Tests to Write

N/A — this is a pure YAML configuration change; there is no testable application logic involved. The Phase 2 (TDD) phase is skipped per the documented exception for configuration-only changes.

Test Command

npm test (full Jest suite, to confirm no existing tests regress)

[don-petry]

Dev-Lead: Implementation Complete

Plan Execution

• Added secret_scanning_ai_detection with status: enabled under repository.security_and_analysis in .github/settings.yml

Test Results

Test Suites: 12 passed, 12 total
Tests:       301 passed, 301 total
Snapshots:   0 total
Time:        5.679 s

Coverage:
✅ statements     : 98.91% (required: 95%)
✅ branches       : 90.00% (required: 85%)
✅ functions      : 98.00% (required: 95%)
✅ lines          : 100.00% (required: 100%)

✅ All coverage metrics meet requirements.

Files Changed

• .github/settings.yml: Added secret_scanning_ai_detection: enabled under security_and_analysis, alongside the existing secret_scanning, secret_scanning_push_protection, and secret_scanning_non_provider_patterns entries

Notes

• TDD phase skipped: pure YAML configuration change with no testable application logic
• Pre-existing prettier warning on .github/workflows/ci-failure-analyst.yml exists on the branch before this change; it is unrelated to this fix

[don-petry]

Weekly Compliance Audit (2026-05-30)

This finding is still open.

Detail: Secret scanning AI detection should be enabled (current: null, expected: enabled)

Standard: standards/push-protection.md#required-repo-level-settings

[don-petry]

@don-petry-dev-lead