Skip to content

docs: sync audit redaction status and framing with current code #26

docs: sync audit redaction status and framing with current code

docs: sync audit redaction status and framing with current code #26

Triggered via pull request April 15, 2026 01:50
Status Success
Total duration 14s
Artifacts 1

secret-scanning.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
gitleaks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, gitleaks/gitleaks-action@ff98106e4c7b2bc287b24eaf42907196329070c7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
gitleaks
Review the above matches for potential secret exposure
gitleaks
Potential secrets found matching pattern: AKIA[0-9A-Z]{16}
gitleaks
Potential secrets found matching pattern: ghp_[A-Za-z0-9]{36}
gitleaks
🛑 Leaks detected, see job summary for details
gitleaks
Error encountered when attempting to write a comment on PR #8: HttpError: Resource not accessible by integration Likely an issue with too large of a diff for the comment to be written. All secrets that have been leaked will be reported in the summary and job artifact.

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results.sarif
7.09 KB
sha256:78f9d0b34f83565cc93b88c82154eab904f4b2aa1f57ff66de972970f0946291