Vulnerability Static Analysis for Containers
afd7fe2554
Some features do not exist in set locations, but can be anywhere in the layer. This allows those featurefmt to specify the filenames to be scanned by regexp, as opposed to purely by path prefix. If any current users of this express paths which use regexp special characters this could be a breaking change for them (with the exception of . which will continue to work as it matches against the literal character .), however none of the code in this repo does that. fixes #456 |
||
|---|---|---|
| .github | ||
| api | ||
| cmd/clair | ||
| contrib | ||
| database | ||
| Documentation | ||
| ext | ||
| pkg | ||
| testdata/DistUpgrade | ||
| vendor | ||
| .dockerignore | ||
| .travis.yml | ||
| analyzer.go | ||
| ancestry_test.go | ||
| ancestry.go | ||
| bill-of-materials.json | ||
| blob.go | ||
| code-of-conduct.md | ||
| config.yaml.sample | ||
| DCO | ||
| Dockerfile | ||
| glide.lock | ||
| glide.yaml | ||
| LICENSE | ||
| license_header_test.go | ||
| NOTICE | ||
| notifier.go | ||
| README.md | ||
| ROADMAP.md | ||
| updater_test.go | ||
| updater.go | ||
Clair
Note: The master branch may be in an unstable or even broken state during development.
Please use releases instead of the master branch in order to get stable binaries.
Clair is an open source project for the static analysis of vulnerabilities in application containers (currently including appc and docker).
- In regular intervals, Clair ingests vulnerability metadata from a configured set of sources and stores it in the database.
- Clients use the Clair API to index their container images; this creates a list of features present in the image and stores them in the database.
- Clients use the Clair API to query the database for vulnerabilities of a particular image; correlating vulnerabilities and features is done for each request, avoiding the need to rescan images.
- When updates to vulnerability metadata occur, a notification can be sent to alert systems that a change has occured.
Our goal is to enable a more transparent view of the security of container-based infrastructure.
Thus, the project was named Clair after the French term which translates to clear, bright, transparent.
Getting Started
- Learn the terminology and about the drivers and data sources that power Clair
- Watch presentations on the high-level goals and design of Clair
- Follow instructions to get Clair up and running
- Explore the API on SwaggerHub
- Discover third party integrations that help integrate Clair with your infrastructure
- Read the rest of the documentation on the CoreOS website or in the Documentation directory
Contact
Contributing
See CONTRIBUTING for details on submitting patches and the contribution workflow.
License
Clair is under the Apache 2.0 license. See the LICENSE file for details.