Skip to main content

SQ41101

Detected container images that lack HEALTHCHECK instructions.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
passlowmediumNoneNone

About the issue​

Containers typically run in one of two modes, as executables or as services. Regardless of how they are used, it's important to monitor the availability of a container, and executables or services running within it. This is also referred to as checking the container's health. The Dockerfile is a sequence of instructions that defines how an image should be built, and the HEALTHCHECK instruction can be used to define such periodic checks. In other words, depending on how the container is used, it should be possible to check that the container environment and applications within it are still running, and behaving as expected. It is important to check and monitor both, because in some situations, the running executable or service may stop working, while the container environment remains active. By failing to monitor availability, service outages may go unnoticed, which can have a significant business impact.

How to resolve the issue​

  • Make use of the HEALTHCHECK instruction in your Dockerfile, and define a set of checks to verify at regular intervals that both the container and all business-critical services within the container are running.

Incidence statistics​

ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes. Analysis results are used to calculate incidence statistics for issues (policy violations) that Spectra Assure can detect in software packages.

This section is updated when new data becomes available.

Total amount of packages analyzed

  • RubyGems: 183K
  • Nuget: 644K
  • PyPi: 628K
  • NPM: 3.72M

Total detections per repository

For every repository, the chart shows the number of packages that triggered the software assurance policy. In other words, it shows how many packages in each package repository were found to have the specific issue described on this page. This information helps you understand how common the issue is across different software communities.

If a repository is absent from the chart, that means none of the packages in that repository triggered this policy during analysis, or the policy was not used during analysis.

Distribution of total detections by project popularity

For every repository, the chart shows how many of the total detections belong to the Top 100 (1-100), Top 1000 (101-1000) and Top 10 000 (1001-10 000) most downloaded projects. This information helps you understand the impact of the issue within each community, making it clearer when the issue affects the most popular projects.

If the chart shows zero values for all of the top project groups, that means all detections were in unranked projects (lower than 10 000 on the list of most downloaded projects).