Vulnerability Static Analysis for Containers
Go to file
Grégoire Unbekandt ac86a36740 vulnsrc_rhel: rhsa_ID by default
If no CVE is present, create a vulnerability with rhsa ID
2018-09-14 23:54:33 +02:00
.github
api Merge pull request #619 from KeyboardNerd/sidac/rm_layer 2018-09-13 14:36:26 -04:00
cmd/clair pkg/pagination: init 2018-09-07 16:13:51 -04:00
contrib Helm: change postgresql connection string format in configmap template 2018-08-13 15:24:33 +02:00
database database: Use LayerWithContent as Layer 2018-09-13 13:21:39 -04:00
Documentation
ext vulnsrc_rhel: rhsa_ID by default 2018-09-14 23:54:33 +02:00
pkg pkg/grpcutil: init 2018-09-11 14:46:52 -04:00
testdata/DistUpgrade
vendor vendor: regenerate after removing graceful 2018-09-06 16:56:33 -04:00
.dockerignore Adding httputil and version packages 2018-09-05 14:56:39 -04:00
.travis.yml travis: fail if not gofmt -s 2018-09-05 18:57:10 -04:00
bill-of-materials.json api: remove dependency on graceful 2018-09-06 16:56:33 -04:00
code-of-conduct.md
config.yaml.sample
DCO
Dockerfile Adding httputil and version packages 2018-09-05 14:56:39 -04:00
glide.lock api: remove dependency on graceful 2018-09-06 16:56:33 -04:00
glide.yaml api: remove dependency on graceful 2018-09-06 16:56:33 -04:00
LICENSE
NOTICE
notifier.go database: changed Notification interface name 2018-09-11 14:24:09 -04:00
README.md
ROADMAP.md
updater_test.go *: gofmt -s 2018-09-05 19:20:35 -04:00
updater.go
worker_test.go database: Use LayerWithContent as Layer 2018-09-13 13:21:39 -04:00
worker.go database: Use LayerWithContent as Layer 2018-09-13 13:21:39 -04:00

Clair

Build Status Docker Repository on Quay Go Report Card GoDoc IRC Channel

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 Logo

Clair is an open source project for the static analysis of vulnerabilities in application containers (currently including appc and docker).

  1. In regular intervals, Clair ingests vulnerability metadata from a configured set of sources and stores it in the database.
  2. 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.
  3. 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.
  4. 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

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.