
StackRadar is now open source – Kubernetes SBoM vulnerability tracking
The vulnerabilities on the images running in your Kubernetes cluster,
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
The vulnerabilities on the images running in your Kubernetes cluster,
ranked by what to fix first, with the upgrade that fixes them.
Live demo · Quick start · Documentation · Website · Cloud
A scanner tells you your cluster has four thousand CVEs. StackRadar tells you which of them are on images that are running right now, which of those are being exploited in the wild, and which chart version or image tag makes them go away. When a new advisory is published, the dashboard already knows which pods run it, without pulling or scanning anything again.
StackRadar is open source under AGPL-3.0. Self-host it with one helm install, or use the hosted version at app.stackradar.io.
Scans what runs, once. A read-only agent watches the pods of the cluster it runs in, pulls each image once per digest and writes its SBOM with Syft. No scan Job per workload, no report objects in etcd.
Re-matches instead of re-scanning. The server mirrors OSV.dev, EPSS and the CISA KEV catalogue locally and matches every stored SBOM again whenever the mirror changes.
Ranks by exploitability. The Radar Score folds CVSS, EPSS and KEV into one number per finding and sums them per image, container, release and cluster. The top of every list is what to fix first.
Tells base image from application layer, so a finding in your own code is not buried under the ones in debian:bookworm.
Knows how the image got there. The Helm release that packaged a workload and the Argo CD application that delivers it are on the page, so the fix is a chart version and a helm, argocd or kubectl command.
Shows what changed. A feed of advisories that landed on running images, containers that moved between digests, and the finding delta between them. New critical and KEV findings can go to a Slack webhook.
End-of-life verdicts for base images, so a fix that cannot exist is not on the list.
CycloneDX in and out. Upload an SBOM by hand, download the stored SBOM of any image.
Sign-in your way. Local username and password, any OpenID Connect provider, GitHub or Google.
One Postgres, migrations on boot, no telemetry.
StackRadar does not do configuration audit, RBAC assessment or CIS benchmarks. Trivy Operator does, and the two run side by side without conflict.
Three components, two of them in this repository, and in a self-hosted install all of them run in your cluster from one chart. The scanner reports one SBOM per image digest plus the full workload inventory over an API key scoped to its cluster. The server stores the SBOMs, mirrors the advisory feeds, matches components by package URL and ranks every finding. The client is the dashboard and the only thing a browser talks to. One PostgreSQL database carries both, and the advisory syncs are the only traffic that leaves the cluster.
The image is the unit of identity, not the workload, and the score has two layers: a 0–100 risk per finding that is a pure function of the advisory, and an unbounded sum of those per rollup. The trust boundaries, the data model and the decisions behind them are in docs/ARCHITECTURE.md and the ADRs in docs/adr/.
Helm
Kubernetes 1.25+ and Helm 3.8+. No values file, no database to bring, and the scanner is included:
helm install stackradar oci://ghcr.io/lockdep/helm-charts/stackradar
--create-namespace -n stackradar
kubectl -n stackradar port-forward svc/stackradar-client 3000:3000
Open http://localhost:3000 and log in as admin@stackradar.local with the password admin. Your cluster's images are already being scanned; findings appear once the vulnerability mirror has bootstrapped. On a laptop cluster (kind, minikube, Docker Desktop) add -f https://raw.githubusercontent.com/lockdep/helm-charts/main/charts/stackradar/values-quickstart.yaml for trimmed resources and a two-minute, Alpine-only mirror.
The default install uses a bundled Postgres and public fixture credentials. Set your own before you rely on it; docs/self-hosting/helm.md is the walkthrough.
The try-out without a cluster. It cannot run the scanner, so you upload an SBOM yourself:
curl -LO https://raw.githubusercontent.com/lockdep/stackradar/main/deploy/compose/docker-compose.yml docker compose up -d
docs/self-hosting/docker-compose.md has the upload commands and the same warning about fixture secrets.
No install, no account: stackradar scan answers the same question for any cluster you have kubectl access to and prints the report in your terminal.
One codebase, two configurations. STACKRADAR_EDITION=community is the default; the cloud opts in. Everything sold only on the cloud lives under server/src/cloud/ and client/src/cloud/, and CI keeps the boundary mechanical.
Self-hosting: Helm walkthrough, Compose, users and local login, OIDC, your own Postgres, upgrading, backups
Chart values reference
Architecture and the ADRs
Scanner wire contract and the authorization matrix
Developing, releasing and verifying a release's signature
The hosted product: stackradar.io/docs
Related repositories
Repository What it is Licence
lockdep/stackradar This one: the server, the web client and the self-hosting docs AGPL-3.0
lockdep/helm-charts The stackradar chart: both apps, a bundled Postgres and the scanner Apache-2.0
lockdep/stackradar-scanner The in-cluster agent, the only SBOM ingestion path Apache-2.0
lockdep/stackradar-cli stackradar scan, the same answer from a laptop Apache-2.0
Security
The agent is read-only. list and watch on pods plus metadata-only get on their controllers. What leaves the cluster is an allowlist, documented in the scanner README.
No telemetry. The only outbound traffic from a self-hosted install is the advisory mirror syncs.
Cluster-scoped keys. An SBOM and its findings belong to exactly one cluster; nothing derived from an upload is shared across clusters.
Signed, attested, multi-arch releases. Images are signed with cosign keyless and carry SLSA provenance and SBOM attestations; the chart pins them by digest. RELEASING.md has the cosign verify commands.
Report a vulnerability privately through GitHub's private reporting or to security@stackradar.io. SECURITY.md has the scope, the response time and the supported versions.
Questions and ideas: GitHub Discussions
Defects and enhancements: GitHub Issues
Using StackRadar? Add yourself to ADOPTERS.md
Contributing
Contributions of every shape are welcome. CONTRIBUTING.md says how to file an issue and send a pull request (commits are signed off under the DCO; there is no CLA), DEVELOPING.md says how to build and run the two apps, and CODE_OF_CONDUCT.md is the Contributor Covenant. Issues labelled good first issue are the ones to start with.
This repository is licensed under the GNU Affero General Public License, version 3 only, except for server/src/cloud/ and client/src/cloud/, which are source-available under the StackRadar Cloud Licence. The scanner, the CLI and the Helm chart are Apache-2.0. The licence covers the code, not the name; NOTICE has the trademark terms.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。