Skip to content
Container Security Scan

Container Security Scan #33

Sign in to view logs

Container Security Scan

Container Security Scan #33

Triggered via schedule August 29, 2025 02:30
@sattvikcsattvikc
⁠ 58956c3
master
Status Success
Total duration 39s
Artifacts 1

container-check.yml

on: schedule
Scan SuperTokens PostgreSQL Container
35s
Scan SuperTokens PostgreSQL Container
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Scan SuperTokens PostgreSQL Container
Vulnerabilities were detected in the container image
Scan SuperTokens PostgreSQL Container
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
Scan SuperTokens PostgreSQL Container
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 SuperTokens PostgreSQL Container
An error occurred while creating the check run for container scan. Error: Error: An error occurred while creating scan result. Statuscode: 404, StatusMessage: Not Found, head_sha: 58956c36759074431566b6979992243bcb0fca43

Artifacts

Produced during runtime
Name Size Digest
container-scan-results
8.58 KB
sha256:93626f4dfbc95b37c4ac10b36c6b90c02d8516fb876761651453cc5befd14600