Skip to content

fix(security): P2-8 AES-256-GCM encryption-at-rest for on-disk secrets #138

fix(security): P2-8 AES-256-GCM encryption-at-rest for on-disk secrets

fix(security): P2-8 AES-256-GCM encryption-at-rest for on-disk secrets #138

Triggered via pull request May 11, 2026 06:16
Status Failure
Total duration 1m 3s
Artifacts 2

security.yml

on: pull_request
Go Security Scan (gosec)
47s
Go Security Scan (gosec)
Trivy Repository Scan
25s
Trivy Repository Scan
NPM Security Audit
13s
NPM Security Audit
Secret Scanning (gitleaks)
16s
Secret Scanning (gitleaks)
Dependency Review
19s
Dependency Review
Security Scan Summary
2s
Security Scan Summary
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
NPM Security Audit
The process '/usr/bin/git' failed with exit code 128
Secret Scanning (gitleaks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
Secret Scanning (gitleaks)
The process '/usr/bin/git' failed with exit code 128
Secret Scanning (gitleaks)
🛑 Leaks detected, see job summary for details
Secret Scanning (gitleaks)
Error encountered when attempting to write a comment on PR #55: 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.
Secret Scanning (gitleaks)
Error encountered when attempting to write a comment on PR #55: 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.
Secret Scanning (gitleaks)
Error encountered when attempting to write a comment on PR #55: 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.
Dependency Review
The process '/usr/bin/git' failed with exit code 128
Trivy Repository Scan
The process '/usr/bin/git' failed with exit code 128
Go Security Scan (gosec)
The process '/usr/bin/git' failed with exit code 128

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results.sarif Expired
7.64 KB
sha256:fb220e963993ca3485808ebfb8ebfd7b95f49811c9df307787e4fc2f47d82869
npm-audit-results Expired
314 Bytes
sha256:bdc9822d782d644a78fed1a93ac3b0142fd4ab4882f2fcbe2f2cd161371ccec6