Skip to content

CCM-15550: Disable Trivy in CI #2193

CCM-15550: Disable Trivy in CI

CCM-15550: Disable Trivy in CI #2193

Triggered via push March 23, 2026 15:42
Status Success
Total duration 8m 10s
Artifacts 6
Set CI/CD metadata
7s
Set CI/CD metadata
Commit stage  /  Scan secrets
14s
Commit stage / Scan secrets
Commit stage  /  Check file format
6s
Commit stage / Check file format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
7s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
3s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
50s
Commit stage / Scan dependencies
Commit stage  /  Detect Terraform Changes
6s
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
7s
Test stage / Detect Schema Changes
Test stage  /  Unit tests
5m 25s
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
Build stage / Detect Documentation Changes
Build stage  /  Build Docs
Build stage / Build Docs
Trigger dynamic environment creation
0s
Trigger dynamic environment creation
Publish stage  /  Publish packages
Publish stage / Publish packages
Acceptance stage  /  Accessibility test
Acceptance stage / Accessibility test
Acceptance stage  /  Contract test
Acceptance stage / Contract test
Acceptance stage  /  Integration test
Acceptance stage / Integration test
Acceptance stage  /  Load test
Acceptance stage / Load test
Acceptance stage  /  Security test
Acceptance stage / Security test
Acceptance stage  /  UI performance test
Acceptance stage / UI performance test
Acceptance stage  /  UI test
Acceptance stage / UI test
Fit to window
Zoom out
Zoom in

Annotations

15 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/

Artifacts

Produced during runtime
Name Size Digest
code-coverage-report
16.8 KB
sha256:60495d503df93bef0de0d52deec04cbf2c94dc47821e348ce7980a118e4c0012
lines-of-code-report.json.zip Expired
996 Bytes
sha256:a921ae8f58729f8e6940caa7430dc5c8c972a3012934f68fe704a5768f851a8a
python-coverage-reports
12.8 KB
sha256:f64f659011ce7d342bda8cd339c7b658da9a98a188088b759c195cebac10e1c2
sbom-repository-report.json.zip Expired
392 KB
sha256:470e7c246e6ae2fc7984aecc57dd6ad1962af2ae705193bfe9aed7a659a1a96d
unit-tests
1.87 MB
sha256:1df49088e4632bb8d6ca8fd03293a7a510035d82f3a5eb6ea1ed76a450f0600a
vulnerabilities-repository-report.json.zip Expired
10.1 KB
sha256:5ee3d7aab152ef4fdc67d1a8291430b4b119f148b680e567dbd0b9665ce8ed07