quay/clair

Vulnerability Static Analysis for Containers

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 21 minutes ago
Added to GitGenius on April 7th, 2021
Created on November 13th, 2015
Open Issues & Pull Requests: 60 (+0)
Number of forks: 1,216
Total Stargazers: 11,051 (+0)
Total Subscribers: 219 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.0 days
Mean response time: 157.0 days
90th percentile: 289.2 days
Tracked items: 29

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 4% of issues opened in the past year have been closed. Three people close 71% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 355 days
Stale 30+ days: 13
Stale 90+ days: 11

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (1)
  • kind/question (1)
  • triaged (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Clair is an open source project written in Go that performs static analysis of vulnerabilities in application containers, with support for OCI and Docker image formats. The project enables users to index container images through its API and match them against known vulnerabilities, providing transparency into the security posture of container-based infrastructure. The name derives from the French word for clear, bright, and transparent, reflecting the project's goal of offering visibility into container security.

The repository is maintained by the Quay team and serves as a critical component in the container security ecosystem. It functions as a vulnerability scanner that analyzes container images to identify potential security issues before deployment. Clients interact with Clair through its API to submit container images for analysis and retrieve vulnerability assessment results. The project's architecture and operational details are documented in an accompanying book that covers both design decisions and usage patterns.

The project's issue tracking shows engagement across multiple categories, with kind/question, help wanted, and triaged labels being most frequently applied, suggesting an active user base seeking guidance and community involvement in development.

The repository's classification spans multiple security and container-related domains including container security, software package inspection, dependency checking, image analysis, vulnerability scanning, and static analysis. This broad categorization reflects Clair's role as a comprehensive tool for assessing container image security across multiple dimensions including filesystem inspection, OS package analysis, and manifest evaluation. The project is positioned within the software supply chain security space, addressing the need for automated vulnerability detection in containerized applications.

The project maintains community engagement through multiple channels including a mailing list at [email protected] and IRC presence on freenode.org, facilitating discussion and support for users and contributors.

The README explicitly notes that the main branch may be unstable during active development, directing users to rely on official releases for stable binaries. This transparency about development status reflects the project's commitment to clear communication about code stability. Clair is licensed under Apache 2.0, making it freely available for both open source and commercial use. The project welcomes contributions through a defined workflow documented in its CONTRIBUTING guidelines, supporting community participation in ongoing development and improvement of container vulnerability analysis capabilities.