hadolint
grype
Our great sponsors
| hadolint | grype | |
|---|---|---|
| 18 | 44 | |
| 8,331 | 5,408 | |
| 3.2% | 5.9% | |
| 6.8 | 8.5 | |
| 14 days ago | 4 days ago | |
| Haskell | Go | |
| GNU General Public License v3.0 only | Apache License 2.0 |
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.
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.
grype
-
Show HN: Xeol – An End Of Life (EOL) package scanner for container images
Hey everyone! I open-sourced a project that finds unsupported/End of Life software in container images, systems, and SBOMs.
It's based on https://github.com/anchore/grype and uses https://endoflife.date/ as a data source for EOL packages.
-
Keeping up with dependencies like a boss
I'll continue relying on Anitya for the feed and syft/grype to build my SBOM and track vulnerabilities.
-
Is this Dockerfile ready for production? Is the container automatically secure?
You could also do CVE scanning of your container in your pipeline before you push to a registry. try Trivy https://github.com/aquasecurity/trivy or grype https://github.com/anchore/grype
-
🪄 Grype jq tricks : csv for spreadsheets 📊
Since v0.42.0, and its issue #724 it is possible to transform analysis report with templates.
-
Jetstack Paranoia: A New Open-Source Tool for Container Image Security
I was also a bit confused and expected something like grype -https://github.com/anchore/grype
-
Implement DevSecOps to Secure your CI/CD pipeline
For example, let's see how the DevSecOps process can detect and prevent zero-day vulnerabilities like log4j. Using Syft tool, we can generate SBOM for our application code and pass this SBOM report to Grype which can detect these new vulnerabilities and report to us if there is any fix or patch available. As these steps are part of our CI/CD, we can alert our developers and security team to remediate this issue as soon as it is identified.
-
🪄 Introducing jq tricks to Grype-Contribs
The aim of this repo is to summarize some resources around Grype to take the best ouf this great tool.
-
📢 Grype 0.42.0 is out... and hello grype-contribs 👶
Grype recently released a very interesting version : v0.42.0, which includes a very (very) interesting feature (and resource within the issue itself) :
-
⚖️ Kafka image : wurstmeister vs. bitnami
❔ What does Unknown mean ❔ #807
-
🛡️ Is Redmine affected by CVE-2022-32209 ?
To answer if we are affected, the question can be answered within a single line of code, thanks to grype :
What are some alternatives?
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
anchore-engine - A service that analyzes docker images and scans for vulnerabilities
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
clair - Vulnerability Static Analysis for Containers
dockle - Container Image Linter for Security, Helping build the Best-Practice Docker Image, Easy to start
opencve - CVE Alerting Platform
falco - Cloud Native Runtime Security
kubescape - Kubescape is an open-source Kubernetes security platform for your IDE, CI/CD pipelines, and clusters. It includes risk analysis, security, compliance, and misconfiguration scanning, saving Kubernetes users and administrators precious time, effort, and resources.
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