Skip to content

CCM-18631: stabilise component tests (#602) #4769

CCM-18631: stabilise component tests (#602)

CCM-18631: stabilise component tests (#602) #4769

Triggered via push June 1, 2026 11:19
Status Success
Total duration 22m 49s
Artifacts 20
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
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
10s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
6s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
1m 10s
Commit stage / Scan dependencies
Commit stage  /  Check for changes to event schema package compared to main branch
6s
Commit stage / Check for changes to event schema package compared to main branch
Commit stage  /  Detect Terraform Changes
5s
Commit stage / Detect Terraform Changes
Commit stage  /  Check event schema version has been updated
Commit stage / Check event schema version has been updated
Commit stage  /  Check for event schemas package version change
Commit stage / Check for event schemas package version change
Commit stage  /  Run terraform-docs
0s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
0s
Commit stage / Lint Terraform
Test stage  /  Check generated dependencies
54s
Test stage / Check generated dependencies
Test stage  /  Pact tests
53s
Test stage / Pact tests
Test stage  /  Linting
3m 15s
Test stage / Linting
Test stage  /  Typecheck
2m 3s
Test stage / Typecheck
Test stage  /  Unit tests
2m 56s
Test stage / Unit tests
Test stage  /  Test coverage
4s
Test stage / Test coverage
Test stage  /  Perform static analysis
1m 0s
Test stage / Perform static analysis
Build stage  /  Build Docs
1m 38s
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
5m 15s
Build stage / Create Dynamic Environment
Matrix: Build stage / Build OAS spec for main
Build stage  /  Build OAS spec for sandbox
1m 2s
Build stage / Build OAS spec for sandbox
Build stage  /  Build OAS spec for PR
0s
Build stage / Build OAS spec for PR
Build stage  /  Populate Supplier Config
38s
Build stage / Populate Supplier Config
Build stage  /  OAS spec ready
3s
Build stage / OAS spec ready
Build stage  /  Build proxies
1m 32s
Build stage / Build proxies
Build stage  /  Build SDKs
1m 21s
Build stage / Build SDKs
Acceptance stage  /  Run Acceptance Tests
9m 47s
Acceptance stage / Run Acceptance Tests
Publish stage  /  Publish packages
18s
Publish stage / Publish packages
Publish stage  /  Publish npm packages to npm.pkg.github.com
17s
Publish stage / Publish npm packages to npm.pkg.github.com
Publish stage  /  Publish nuget packages to nuget.pkg.github.com
8s
Publish stage / Publish nuget packages to nuget.pkg.github.com
Matrix: Publish stage / publish-oas-specs
Publish stage  /  Success notification
4s
Publish stage / Success notification
Fit to window
Zoom out
Zoom in

Annotations

50 warnings
Test stage / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Typecheck
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Typecheck
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Unit tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Unit tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Linting
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Linting: lambdas/api-handler/src/handlers/__tests__/post-mi.test.ts#L7
Caution: `mi-operations.ts` has a default export `postMI`. This imports `postMI` as `postMiOperation`. Check if you meant to write `import postMI from '../../services/mi-operations'` instead
Test stage / Linting: internal/helpers/src/id-ref.ts#L54
Variable Assigned to Object Injection Sink
Test stage / Linting
asyncapi-unused-components-schema Potentially unused components schema has been detected.
Test stage / Linting
asyncapi-unused-components-schema Potentially unused components schema has been detected.
Test stage / Linting
asyncapi-info-license Info object must have "license" object.
Test stage / Linting
asyncapi-info-contact Info object must have "contact" object.
Test stage / Linting
asyncapi-3-tags AsyncAPI document must have non-empty "tags" array.
Test stage / Linting: internal/datastore/src/letter-repository.ts#L64
Variable Assigned to Object Injection Sink
Test stage / Linting
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Build stage / Build Docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@v4, ruby/setup-ruby@3783f195e29b74ae398d7caca108814bbafde90e. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0WmwdagAAAABdEfyI59P0Sa0WDqgy4UozUEhYMzFFREdFMDYwOQBFZGdl
Build stage / Build Docs
Failed to restore: Cache service responded with 400
Build stage / Build OAS spec for main (internal-dev-pr)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build OAS spec for main (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build OAS spec for main (ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build OAS spec for main (int)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build OAS spec for sandbox
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build OAS spec for main (internal-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build SDKs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build stage / Build proxies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Publish stage / Publish packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-release@0cb9c9b65d5d1901c1f53e5e66eaf4afd303e70e, actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (internal-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Publish stage / Publish OAS spec (internal-dev)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Publish stage / Publish OAS spec (ref)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (int)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Publish stage / Publish OAS spec (int)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Publish stage / Publish OAS spec (prod)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Artifacts

Produced during runtime
Name Size Digest
api-oas-specification-int-1.1.6-20260601.112004+fc6ef15
20.9 KB
sha256:d46b71e0518643060f18ab10eb53dac70ff8ebfb351277e6f7d4441277cd3231
api-oas-specification-internal-dev-1.1.6-20260601.112004+fc6ef15
21 KB
sha256:c9f2960ff392a9b09228f8a64e808b2c5875e917552ec6cc40b18a11ce450b2c
api-oas-specification-internal-dev-pr-1.1.6-20260601.112004+fc6ef15
20.7 KB
sha256:b59d08df6cc5ecada08f7df7707597a1c3ed30750cb018e9c7737e00feb8c8cb
api-oas-specification-internal-dev-sandbox-1.1.6-20260601.112004+fc6ef15
20.9 KB
sha256:d10e4d4aa8835167f08b83ce286c47ebe58941658415bbaa1c4cbd02a9e63984
api-oas-specification-prod-1.1.6-20260601.112004+fc6ef15
20.9 KB
sha256:37bd66916a1b5e6910eb4180d511e6ca82b3d299d0b5c8d0c80120b6d15a5148
api-oas-specification-ref-1.1.6-20260601.112004+fc6ef15
20.9 KB
sha256:14561d49667d1e25af196b410506bdd7f34735f6e620dfa13f7d6edaaa3ab6db
code-coverage-report
5.41 KB
sha256:bb124b19e7fadb5199b15eb4e8c3e45fca1fa29ca52cd302f598b143fa8e8d55
internal-dev-build-output
21 KB
sha256:569484ea7dedd2ce1a3dd918ee78a1d9357d73f8473871da39666845cc2db273
jekyll-docs-1.1.6-20260601.112004+fc6ef15 Expired
1.4 MB
sha256:bd3aa4221561653e37721d9077f5e8678be072e4354754866c40a8e74135c1b2
lines-of-code-report.json.zip Expired
971 Bytes
sha256:86e18197194733321058c06404b03db1182aa6687e858e947b704a768f26565e
sbom-repository-report.json.zip Expired
127 KB
sha256:56763536f4f38b2c12d3b2df74f5ee5e7cf5fd3cf66e5b854a610a62e822a636
sdk-csharp-1.1.6-20260601.112004+fc6ef15
1 MB
sha256:f8d450b445c1fe4cb833c18b0be666c19c1cfda6051c48dc4f0e8dff7585a1ba
sdk-html-1.1.6-20260601.112004+fc6ef15
8.54 KB
sha256:f6a2c3f0ba9647dd7aadf614caa89581e484f824342e812f935890642aad1dc2
sdk-html-docs-1.1.6-20260601.112004+fc6ef15 Expired
9.22 KB
sha256:a4d052833904770c52ae491056b4752e45887a2f0b4a03e75f10d174514b0987
sdk-python-1.1.6-20260601.112004+fc6ef15
223 KB
sha256:04a7788436523e2abc9fb6dadc0290da062abf409530360d9878a6e2ee6989e3
sdk-swagger-1.1.6-20260601.112004+fc6ef15
1.09 MB
sha256:17f0e5b6ee4bf7dbded2edf460eb26a759f308fd2e9c8fc81e1c1086761e11d1
sdk-swagger-docs-1.1.6-20260601.112004+fc6ef15 Expired
1.09 MB
sha256:49e207bd747586fdcaa0c6555b1d36dc5950979569467eb1f4310e1d32b1b36d
sdk-ts-1.1.6-20260601.112004+fc6ef15
98.8 KB
sha256:5521348ad277771bd6492418f2d6a5e8387b55353272e809cd2af7724958ba8d
unit-tests
893 KB
sha256:463ca65412fe83bbceddfbe20e31f0c17da69a761d4e1084b69c816e4f325596
vulnerabilities-repository-report.json.zip Expired
6 KB
sha256:09a44f7778f79e7759baae0ba2fef7ef0b31159c683c1dcb374bf2c78d37a09a