Skip to content

CCM-15550: Disable Trivy in CI #2194

CCM-15550: Disable Trivy in CI

CCM-15550: Disable Trivy in CI #2194

Triggered via pull request March 23, 2026 15:42
Status Success
Total duration 35m 41s
Artifacts 6

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
13s
Commit stage / Scan secrets
Commit stage  /  Check file format
6s
Commit stage / Check file format
Commit stage  /  Check Markdown format
3s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
7s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
5s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
10s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
46s
Commit stage / Scan dependencies
Commit stage  /  Detect Terraform Changes
5s
Commit stage / Detect Terraform Changes
Commit stage  /  Run terraform-docs
0s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
0s
Commit stage / Lint Terraform
Test stage  /  Detect Schema Changes
5s
Test stage / Detect Schema Changes
Test stage  /  Unit tests
5m 20s
Test stage / Unit tests
Test stage  /  Check generated dependencies
0s
Test stage / Check generated dependencies
Test stage  /  Perform static analysis
1m 33s
Test stage / Perform static analysis
Build stage  /  Detect Documentation Changes
6s
Build stage / Detect Documentation Changes
Build stage  /  Build Docs
0s
Build stage / Build Docs
Trigger dynamic environment creation
15m 8s
Trigger dynamic environment creation
Publish stage  /  Publish packages
Publish stage / Publish packages
Acceptance stage  /  Contract test
4s
Acceptance stage / Contract test
Acceptance stage  /  Security test
6s
Acceptance stage / Security test
Acceptance stage  /  UI test
6s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
3s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
12m 10s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
4s
Acceptance stage / Accessibility test
Acceptance stage  /  Load test
5s
Acceptance stage / Load test
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Test stage / Detect Schema Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Test stage / Linting: utils/utils/src/event-publisher/event-publisher.ts#L101
Function Call Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L47
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L34
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/config-reader.ts#L69
Variable Assigned to Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L52
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L33
Variable Assigned to Object Injection Sink
Test stage / Linting: lambdas/print-analyser/src/__tests__/test-data.ts#L60
Found readFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: lambdas/ttl-handle-expiry-lambda/src/__tests__/app/dlq.test.ts#L183
Variable Assigned to Object Injection Sink
Test stage / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Test stage / Perform static analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build stage / Detect Documentation Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
code-coverage-report
16.8 KB
sha256:8c84b58bfdbe577c2f218f1e244b6aa80efdcd610ddd7788312f2b58f86db249
lines-of-code-report.json.zip Expired
970 Bytes
sha256:52948b39cb9aa69347daf951cb9c25ce8af6110eef6a7bf8f31af03ffd23c347
python-coverage-reports
12.8 KB
sha256:ba8fcc55ed91d62636fc6e639fdc7deee9450e585df1f76396576590c2c328c0
sbom-repository-report.json.zip Expired
392 KB
sha256:f37372915a056a605dd1debdfbfb2458d432652ecda67201658b6d0f2e24e1f9
unit-tests
1.87 MB
sha256:842d7f532ed45ad19c67ce0d43968b10c921d4549d6ce23ddaab003a757de4d5
vulnerabilities-repository-report.json.zip Expired
10.1 KB
sha256:e742fd5b90604f85bf362a8130d17c242aa4f35da014a8285b91e70e8db27b2b