AI Supply Chain Feature(AST-127864) #742
ci-tests.yml
on: pull_request
unit-tests
37m 23s
integration-tests
3m 3s
lint
3m 17s
govulncheck
2m 37s
scan Docker Image with Trivy
3m 1s
Annotations
23 errors and 22 warnings
|
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls binary.NewELFPackageCataloger
|
|
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls binary.NewClassifierCataloger
|
|
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls binary.DefaultClassifierCatalogerConfig
|
|
govulncheck
wrappers.init calls containerResolver.init, which eventually calls artifact.init
|
|
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls artifact.IDByHash
|
|
govulncheck
kerberos.ValidateKerberosSetup calls config.Load, which eventually calls arch.newScanner
|
|
govulncheck
wrappers.init calls containerResolver.init, which eventually calls arch.init
|
|
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls arch.NewDBCataloger
|
|
govulncheck
wrappers.init calls containerResolver.init, which eventually calls alpine.init
|
|
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls alpine.NewDBCataloger
|
|
scan Docker Image with Trivy
Process completed with exit code 1.
|
|
integration-tests
Process completed with exit code ***.
|
|
integration-tests:
internal/wrappers/scan-summary-http.go#L1
invalid BOM in the middle of the file
|
|
lint:
internal/wrappers/results-summary.go#L181
exported: exported method ResultSummary.HasAISC should have comment or be unexported (revive)
|
|
lint:
internal/wrappers/results-summary.go#L78
exported: exported type AISCInfo should have comment or be unexported (revive)
|
|
lint:
internal/wrappers/mock/scan-summary-mock.go#L9
exported: exported method ScanSummaryMockWrapper.GetScanSummaryByScanID should have comment or be unexported (revive)
|
|
lint:
internal/wrappers/mock/scan-summary-mock.go#L7
exported: exported type ScanSummaryMockWrapper should have comment or be unexported (revive)
|
|
lint:
internal/wrappers/feature-flags.go#L25
exported: exported const AISupplyChainGAEnabled should have comment or be unexported (revive)
|
|
lint:
internal/wrappers/feature-flags.go#L24
exported: exported const AISupplyChainEnabled should have comment or be unexported (revive)
|
|
lint:
internal/wrappers/results.go#L47
File is not properly formatted (gofmt)
|
|
lint:
internal/wrappers/mock/scan-summary-mock.go#L24
File is not properly formatted (gofmt)
|
|
lint:
internal/commands/result_test.go#L1881
File is not properly formatted (gofmt)
|
|
lint:
internal/commands/scan_test.go#L844
string `sast,kics,sca,aisc` has 4 occurrences, make it a constant (goconst)
|
|
govulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v4.0.0. 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/
|
|
govulncheck
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>0xOHNaQAAAAC/EeYtvLsRRZh3QWmEo5RnRE0yRURHRTA4MTkARWRnZQ==
|
|
govulncheck
Failed to restore: Cache service responded with 400
|
|
scan Docker Image with Trivy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@722adc63f1aa60a57ec37892e133b1d319cae598, docker/login-action@49ed152c8eca782a232dede0303416e8f356c37b, docker/setup-buildx-action@cf09c5c41b299b55c366aff30022701412eb6ab0. 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/
|
|
scan Docker Image with Trivy
The `save-state` 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/
|
|
scan Docker Image with Trivy
The `save-state` 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/
|
|
scan Docker Image with Trivy
The `save-state` 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/
|
|
scan Docker Image with Trivy
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/
|
|
scan Docker Image with Trivy
The `save-state` 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/
|
|
scan Docker Image with Trivy
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/
|
|
scan Docker Image with Trivy
The `save-state` 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/
|
|
scan Docker Image with Trivy
The `save-state` 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/
|
|
scan Docker Image with Trivy
The `save-state` 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/
|
|
integration-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@***e3***de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c23***6fe8***22ab82dc22947d607c0c9***f9, actions/upload-artifact@c7d***93f32edcb7bfad88892***6***225aeda64e9392. 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 ***6th, 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-***9-deprecation-of-node-20-on-github-actions-runners/
|
|
integration-tests
Failed to restore: Cache service responded with 400
|
|
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@1e31de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c2316fe8122ab82dc22947d607c0c91f9. 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/
|
|
lint
Unexpected input(s) 'skip-pkg-cache', valid inputs are ['version', 'version-file', 'install-mode', 'install-only', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'args', 'skip-cache', 'skip-save-cache', 'cache-invalidation-interval', 'problem-matchers', 'debug', 'experimental']
|
|
lint
Unexpected input(s) 'skip-pkg-cache', valid inputs are ['version', 'version-file', 'install-mode', 'install-only', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'args', 'skip-cache', 'skip-save-cache', 'cache-invalidation-interval', 'problem-matchers', 'debug', 'experimental']
|
|
lint
Failed to restore: Cache service responded with 400
|
|
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@1e31de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c2316fe8122ab82dc22947d607c0c91f9. 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/
|
|
unit-tests
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>06enNaQAAAABQ0rTGXhE4RKWJKTVcVI2qUEhYMzFFREdFMDIxOQBFZGdl
|
|
unit-tests
Failed to restore: Cache service responded with 400
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Linux-coverage-latest
|
1 KB |
sha256:24172568c6b7786531234148f99fb5123ac3bae2cadc43f695b1f0fa0c4d3fc0
|
|