← Scan another repo

github.com/0xAX/linux-insides

@ 74ea07a94214

Submitted 8/4/2026, 10:28:02 AM · Status: ok

Risk grade
B
27 / 100
Findings
9
0 critical1 high7 medium1 low0 info0 on CISA KEV0ATT&CK
Showing 9 of 9 findings

Findings

  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile:0
  • Ensure that a user for the container has been created
    Ensure that a user for the container has been created on /Dockerfile.
    checkovDockerfile:1
  • Ensure that HEALTHCHECK instructions have been added to container images
    Ensure that HEALTHCHECK instructions have been added to container images on /Dockerfile.
    checkovDockerfile:1
  • Ensure top-level permissions are not set to write-all
    Ensure top-level permissions are not set to write-all on on(Release e-books)
    checkov.github/workflows/release-e-books.yaml:17
  • Ensure top-level permissions are not set to write-all
    Ensure top-level permissions are not set to write-all on on(check code snippets)
    checkov.github/workflows/check-code-snippets.yaml:0
  • Ensure top-level permissions are not set to write-all
    Ensure top-level permissions are not set to write-all on on(check links)
    checkov.github/workflows/check-links.yaml:0
  • Ensure top-level permissions are not set to write-all
    Ensure top-level permissions are not set to write-all on on(Generate e-books)
    checkov.github/workflows/generate-e-books.yaml:13
  • lychee link checking action affected by arbitrary code injection in composite action
    grypeCVE-2024-48908EPSS 0.4%
  • No HEALTHCHECK defined
    You should add HEALTHCHECK instruction in your docker container images to perform the health check on running containers.
    trivyDockerfile:0

This report is public.