scan-action
grype
| scan-action | grype | |
|---|---|---|
| 2 | 61 | |
| 237 | 9,750 | |
| 2.5% | 2.8% | |
| 8.7 | 9.7 | |
| 4 days ago | about 9 hours ago | |
| JavaScript | Go | |
| MIT License | 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.
scan-action
-
🛡️ Docker image security scan automation with GH issues
Anchore Container Scan sourcecode on GitHub
-
Bench (and choose) Java-8 docker images with anchore/grype
I see https://github.com/anchore/scan-action supports a SARIF report. However, instead of using the grype --template option, it creates it in the code.
grype
- Deep Dive 🤿: Where Does Grype Data Come From?
- Grype: Fast and Accurate Vulnerability Scanner for Containers and Filesystems
-
Running WordPress on Containers
Grype is a popular open source CVE scanner that scans for known vulnerabilities in container images and filesystems. At the time of this writing, the latest release is 0.80.1 and you can find packages for most operating systems in their releases page.
-
Ask HN: Pragmatic way to avoid supply chain attacks as a developer
CycloneDX tools offer packages for each and every programming language. [1]
The dependency track project accumulates all dependency vulnerabilities in a dashboard. [2]
Container SBOMs can be generated with syft and grype [3] [4]
[1] https://github.com/CycloneDX
[2] https://github.com/DependencyTrack
[3] https://github.com/anchore/syft
[4] https://github.com/anchore/grype
- A vulnerability scanner for container images and filesystems
-
Introduction to the Kubernetes ecosystem
Trivy Operator : A simple and comprehensive vulnerability scanner for containers and other artifacts. It detects vulnerabilities of OS packages (Alpine, Debian, CentOS, etc.) and application dependencies (pip, npm, yarn, composer, etc.) (Alternatives : Grype, Snyk, Clair, Anchore, Twistlock)
- Suas imagens de container não estão seguras!
-
I looked through attacks in my access logs. Here's what I found
Besides pointing pentester tools like metasploit at yourself, there are some nice scanners out there.
https://github.com/quay/clair
https://github.com/anchore/grype/
-
Distroless images using melange and apko
Using Grype:
-
Scanning and remediating vulnerabilities with Grype
In the lab to follow, we'll see how vulnerability scanning can be conveniently achieved with Grype and how various systematic techniques can be applied to start securing our microservices at the container image level.
What are some alternatives?
action-download-artifact - :gear: A GitHub Action to download an artifact associated with given workflow and commit or other criteria
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
changelog-reader-action - A GitHub action to read and get data from the CHANGELOG.md file 🚀
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
issue-stats-card - Analyse a github repo's issues then generates a table of stats for quick info.
clair - Vulnerability Static Analysis for Containers