uhc-util
hadolint
Our great sponsors
| uhc-util | hadolint | |
|---|---|---|
| 0 | 19 | |
| 6 | 8,660 | |
| - | 2.3% | |
| 0.0 | 5.2 | |
| about 1 month ago | 11 days ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
uhc-util
We haven't tracked posts mentioning uhc-util yet.
Tracking mentions began in Dec 2020.
hadolint
-
Checkmake: Experimental Linter/Analyzer for Makefiles
Some discussion on that here:
https://github.com/koalaman/shellcheck/issues/58
The hadolint project does shell checking for Dockerfiles and it uses shellcheck:
https://github.com/hadolint/hadolint
So the approach is definitely feasible, but you do need a new project and probably it needs to be written in Haskell.
-
Dokter: the doctor for your Dockerfiles
how does this compare to something like hadolint?
Also, have you run across Hadolint for linting? https://github.com/hadolint/hadolint
-
Are there tools that tell you if you can optimize your dockerfiles?
Wow that's a great tool and it has a ton of integrations https://github.com/hadolint/hadolint/blob/master/docs/INTEGRATION.md
- Dhall: A Gateway Drug to Haskell
- can you recommend active Haskell open source projects?
-
Just Say No To `:Latest`
Worth noting that Hadolint[1] raises warnings the issues mentioned in the article. Some examples of warnings:
- https://github.com/hadolint/hadolint/wiki/DL3007: Using latest is prone to errors if the image will ever update. Pin the version explicitly to a release tag.
-
Kubernetes Security Checklist 2021
Dockerfile should be checked during development by automated scanners (Kics, Hadolint, Conftest)
-
CONTAINER SECURITY
Linters are an effective way to catch (security) bugs early on in your development process. For most programming languages using linters is pretty standard. Hadolint is a linter for your Dockerfiles and is found on github here.
-
Best Practices for R with Docker
Best practices for writing Dockerfiles are being followed more and more often according to this paper after mining more than 10 million Dockerfiles on Docker Hub and GitHub. However, there is still room for improvement. This is where linters come in as useful tools for static code analysis. Hadolint lists lots of rules for Dockerfiles and is available as a VS Code extension.
What are some alternatives?
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
dockle - Container Image Linter for Security, Helping build the Best-Practice Docker Image, Easy to start
docker-bench-security - The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production.
stan - 🕵️ Haskell STatic ANalyser
ormolu - A formatter for Haskell source code
grype - A vulnerability scanner for container images and filesystems
hlint - Haskell source code suggestions
leksah - Haskell IDE
podman - Podman: A tool for managing OCI containers and pods.
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
bisect-binary - Tool to determine relevant parts of binary data
ShellCheck - ShellCheck, a static analysis tool for shell scripts