healthy

0.5.105 Opens a new window with list of versions in this module.

Command healthy waits for Docker container(s) to become healthy. For more information about how to use this package see README

Latest version published 2 days ago

GitHub

Package Health Score

74 / 100

security
No known security issues
popularity
Limited
maintenance
Healthy
community
Sustainable

Popularity

Limited

Imported By: 0
GitHub Stars: 6
Forks: 0
Contributors: 4

Usage Popularity

Based on project statistics from the GitHub repository for the Golang package healthy, we found that it has been 6 times.

The popularity score for Golang modules is calculated based on the number of stars that the project has on GitHub as well as the number of imports by other modules.

Security

No known security issues

Security risks

Direct Vulnerabilities: 0
C
0
H
0
M
0
L

Indirect Vulnerabilities: Check with Snyk

Release Date

Apr 23, 2024

License

MIT

Security Policy

Yes

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

Keep your project free of vulnerabilities with Snyk

Maintenance

Healthy

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 2 days ago
Last Commit: 2 days ago

Further analysis of the maintenance status of arnested.dk/go/healthy based on released golang versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that arnested.dk/go/healthy demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Sustainable

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 4
Funding: No

This project has seen only 10 or less contributors.

Embed Package Health Score Badge

Keep your project healthy

Check your go.mod

Ensure all the packages you're using are healthy and well-maintained

Readme

healthy

-- Command healthy waits for Docker container(s) to become healthy.

The command takes one or more container ID's as argument(s) and will not exit until all of them are reported "healthy" as it Health check status.

A container with no health check defined is always considered healthy.

When all specified containers are reported healthy the command will exit with return code 0.

usage: healthy [flags] [container_id_or_name ...]

flags:
  -fail-on-unhealthy
	fail on unhealthy
  -timeout duration
	timeout after waiting (default 1h0m0s)

In a docker-compose setup you could wait for all services to be healthy by running:

healthy $(docker-compose ps -q)

Or just could wait for the database service to be healthy by running:

healthy $(docker-compose ps -q database)

To wait no longer than one and half minute for containers to be healthy:

healthy -timeout 1m30s $(docker-compose ps -q)

You can also run healthy using a Docker image:

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock:ro arnested/healthy $(docker-compose ps -q)

FAQs

What is healthy?

Command healthy waits for Docker container(s) to become healthy. Visit Snyk Advisor to see a full health score report for healthy, including popularity, security, maintenance & community analysis.

Is healthy popular?

The golang package healthy receives a total of ? weekly downloads. As such, healthy popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is healthy well maintained?

We found that healthy demonstrated a healthy version release cadence and project activity. It has a community of 4 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is healthy safe to use?

The golang package healthy was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 24 April-2024, at 16:42 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Usage Popularity

Security risks

Commit Frequency

Embed Package Health Score Badge

Keep your project healthy

Check your go.mod

Readme

healthy

FAQs

What is healthy?

Is healthy popular?

Is healthy well maintained?

Is healthy safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues