PAGES
← all tools
◆ Container & Image Security

cri-tools

v1.37.0 open-source

The cri-tools project provides command-line and validation tools for the Kubelet Container Runtime Interface (CRI).

Summary

cri-tools is an open-source command-line toolset, free to use, bundling crictl for inspecting a running container runtime and critest for validating that a runtime correctly implements the Kubelet Container Runtime Interface. It runs as a binary on the node alongside the kubelet, and is aimed at the people who build or operate CRI-compatible runtimes (containerd, CRI-O and similar) rather than application developers deploying workloads. Recent releases add OTELOTELAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. tracing flags, TLS-secured exec/attach/portforward sessions, and a metricdescs subcommand for discovering what metrics a runtime exposes, reflecting its role as the reference debugging layer the Kubernetes project itself maintains for CRI compliance. It follows Kubernetes's own minor-version release cycle, and with 155 contributors and a release cut 32 days ago, it is actively maintained.

The cri-tools project provides command-line and validation tools for the Kubelet Container Runtime Interface (CRI).

How cri-tools helps

What is actually running on this node right now, pod by pod and container by container?

lists every pod, container, and image the runtime currently knows about, independent of what the Kubernetes API server thinks is scheduled there

Why is a container on this node behaving differently than the runtime itself reports?

inspects and execs directly into the container through the runtime's own interface, bypassing the kubelet so the runtime's view can be compared against the kubelet's

Is a new or patched container runtime actually implementing the interface kubelet expects?

runs a conformance suite against the runtime's CRI endpoint and reports which required behaviors pass or fail against the spec

Where did a container's output go, and can it be recovered after the fact?

pulls stdout and stderr logs straight from the runtime, including reopening rotated log files or isolating a single stream

Which images and resources on a node are actually consuming space or memory?

queries the runtime for image lists, per-container stats, and CPU/memory/swap usage without going through the API server

Did a recent change to a runtime's CRI implementation break something a previous version supported?

runs the same validation suite against both versions and shows which spec checks now fail that used to pass

all 39 features, with the evidence for each →

Languages

Not documented

Features

39 capabilities · 3 backed by code, an API document or a real run

Built from cri-tools's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What cri-tools offers you

  • Command-line interface21
All capabilities 39 capabilities
Container Image Management (renamed from Sandbox/Image Service Endpoint Configur shipped Provides capabilities to pull, inspect, filter, and manage container images including credentials, annotations, and filesystem info. 18 releases · 2 other sources · first seen Sep 2017

previously: Container Image Management

release 18 total

  • Adds a warning to crictl rmi when removing a multi-tagged image, since the CRI API removes all tags, not just the specified one. v1.36.0 · Apr 2026 · source · release history
  • Emits a warning when the cgroup_parent field is left empty in pod config.json. v1.34.0 · Aug 2025 · source · release history
  • Automatically generates a pod UUID when none is provided in the pod config JSON. v1.34.0 · Aug 2025 · source · release history
  • Enables parallel container removal via crictl rm. v1.32.0 · Dec 2024 · source · release history
  • Enables parallel image removal via crictl rmi. v1.32.0 · Dec 2024 · source · release history
  • Implements --filter flag for crictl images with support for dangling, reference, before, and since filters. v1.30.0 · Apr 2024 · source · release history

example

  • Bulk remove all dangling or unreferenced container images to reclaim disk space. crictl rmi --prune v1.17.0 · Dec 2019 · source
  • List only containers running a specific image, filtering out all others crictl ps --image nginx:latest v1.14.0 · Mar 2019 · source
Benchmark Testing shipped Executes and manages CRI conformance benchmarks with custom parameters, parallelism, and output directories. 11 releases · 5 other sources · first seen Jun 2017

release 11 total

  • Adds --benchmarking-output-dir CLI flag to specify a pre-existing directory where benchmark results are saved v1.25.0 · Aug 2022 · source · release history
  • Adds --benchmarking-params-file CLI flag to specify a YAML file with custom benchmark parameters controlling total and parallel execution counts v1.25.0 · Aug 2022 · source · release history
  • Adds optional --benchmarking-output-dir CLI flag to critest for saving benchmark results to a pre-existing directory. v1.24.2 · May 2022 · source · release history
  • Adds optional --benchmarking-params-file CLI flag to critest for specifying a YAML file with custom benchmark parameters. v1.24.2 · May 2022 · source · release history
  • critest now accepts --benchmarking-params-file to specify a YAML file defining custom benchmark parameters controlling total and parallel execution counts v1.24.1 · May 2022 · source · release history
  • critest now accepts --benchmarking-output-dir to save benchmark results into a pre-existing directory v1.24.1 · May 2022 · source · release history

example

  • Store benchmark output logs and metrics in a specific directory for later analysis or CI integration. critest --benchmarking-output-dir=/var/log/critest-benchmarks v1.25.0 · Aug 2022 · source
  • Run benchmarks using custom parallelism settings defined in an external YAML file instead of defaults. critest --benchmarking-params-file=custom-bench.yaml v1.25.0 · Aug 2022 · source
  • Run critest benchmarks using custom parallelism and timing parameters defined in a YAML file, with results saved to a specific folder. critest --benchmarking-params-file /path/to/params.yaml --benchmarking-output-dir /tmp/benchmarks v1.24.2 · May 2022 · source
  • Run critest with custom parallelism limits defined in a config file instead of defaults. critest --benchmarking-params-file /path/to/custom-params.yaml v1.24.1 · May 2022 · source
  • Save benchmark output to a specific directory for archival or analysis. critest --benchmarking-output-dir /var/log/critest-benchmarks v1.24.1 · May 2022 · source
Pod and Sandbox Metrics shipped Retrieves resource usage statistics and metrics for pods and sandboxes. 8 releases · 6 other sources · first seen Dec 2017

Also counts toward: Command-line interface

release 8 total

  • Adds metricdescs subcommand to crictl for querying the ListMetricDescriptors API. v1.34.0 · Aug 2025 · source · release history
  • New crictl metricdescs subcommand exposes the ListMetricDescriptors API for querying available metric descriptors from the runtime. v1.33.0 · Apr 2025 · source · release history
  • Adds swap usage to crictl stats default output. v1.32.0 · Dec 2024 · source · release history
  • Adds --profile-cpu and --profile-mem flags to crictl for on-demand CPU and memory profiling. v1.32.0 · Dec 2024 · source · release history
  • crictl can now display Windows pod statistics v1.27.0 · Apr 2023 · source · release history
  • crictl stats adds a NAME column to its output table v1.27.0 · Apr 2023 · source · release history

example

  • List all metric descriptors exposed by the container runtime to discover available metrics. crictl metricdescs v1.34.0 · Aug 2025 · source
  • List all metric descriptors supported by the container runtime to understand what metrics are available before scraping. crictl metricdescs v1.33.0 · Apr 2025 · source
  • Profile crictl's own CPU usage while diagnosing a slow stats call, writing a pprof file for offline analysis. crictl --profile-cpu /tmp/crictl-cpu.pprof stats v1.32.0 · Dec 2024 · source
  • Retrieve real-time resource usage metrics for pods via the CRI interface. crictl metricsp v1.28.0 · Aug 2023 · source
  • Monitor resource usage for the sandbox of a specific pod. crictl statsp --pod-sandbox-id <POD_SANDBOX_ID> v1.24.0 · May 2022 · source
  • View resource usage stats for containers via the new crictl subcommand. crictl stats v1.0.0-alpha.0 · Dec 2017 · source
Runtime Configuration Management shipped Displays, inspects, and updates container runtime configurations. 7 releases · 3 other sources · first seen Dec 2017

Also counts toward: Command-line interface

release 7 total

  • Adds crictl info now surfaces a RuntimeFeatures object under the .features field (KEP-3619), showing which capabilities the runtime supports. v1.33.0 · Apr 2025 · source · release history
  • Enables crictl exec to run a single command across multiple containers simultaneously using new --image, --label, --last, --latest, --name, --pod, or --state filter flags. v1.32.0 · Dec 2024 · source · release history
  • Adds --quiet/-q, --ignore-error/-e, and --parallel/-x flags to crictl exec for quieter, fault-tolerant, parallel execution. v1.32.0 · Dec 2024 · source · release history
  • Adds crictl update-runtime-config subcommand to update the runtime configuration. v1.31.0 · Aug 2024 · source · release history
  • crictl runtime-config command added v1.28.0 · Aug 2023 · source · release history
  • crictl config gains a list flag to display the current configuration values v1.27.0 · Apr 2023 · source · release history

example

  • Inspect container runtime configuration to verify default settings or limits. crictl runtime-config v1.28.0 · Aug 2023 · source
  • Filter containers by their state (e.g., created) using the new short flag. crictl ps -s created v1.19.0 · Aug 2020 · source
  • Configure runtime options for a specific sandbox using the new config command. crictl config --help v1.0.0-alpha.0 · Dec 2017 · source
WebSocket streaming tests verified Tests attach, exec, and port-forward streaming using WebSocket connections over SPDY. 2 releases · 6 other sources · first seen Apr 2024

release

  • Adds critest flags --websocket-attach, --websocket-exec, and --websocket-portforward to run streaming tests over WebSockets. v1.34.0 · Aug 2025 · source · release history
  • Adds TLS support for crictl exec, portforward, and attach via --tls-ca, --tls-cert, --tls-key, and --tls-server-name flags. v1.32.0 · Dec 2024 · source · release history

command line

  • -websocket-attach — Use websocket connections over SPDY for attach streaming tests. v1.35.0 · Dec 2025 · command-line history
  • -websocket-portforward — Use websocket connections over SPDY for portforward streaming tests. v1.35.0 · Dec 2025 · command-line history
  • -websocket-exec — Use websocket connections over SPDY for exec streaming tests. v1.35.0 · Dec 2025 · command-line history

example

  • Run CRI streaming conformance tests using WebSocket transport instead of the default HTTP streaming, useful for validating WebSocket support in a runtime. critest --websocket-attach --websocket-exec --websocket-portforward v1.34.0 · Aug 2025 · source
  • Secure a streaming session to a container when the CRI runtime requires mutual TLS authentication. crictl exec --tls-ca /etc/cri/ca.crt --tls-cert /etc/cri/client.crt --tls-key /etc/cri/client.key --tls-server-name cri-runtime <container-id> /bin/sh v1.32.0 · Dec 2024 · source
  • Connect via WebSocket for better firewall compatibility when executing into a container. crictl exec --transport websocket <container-id> sh v1.30.0 · Apr 2024 · source
Bulk Removal Support shipped Enables the forceful or bulk removal of multiple containers and images in single operations. 5 releases · 2 other sources · first seen Jul 2019

Also counts toward: Command-line interface

release

  • Enables parallel removal of pod sandboxes for improved performance v1.19.0 · Aug 2020 · source · release history
  • Adds -a (remove all) option to rmp command for removing all containers at once v1.16.0 · Sep 2019 · source · release history
  • Adds --all, -a flag to the crictl rmi subcommand for bulk image removal v1.16.0 · Sep 2019 · source · release history
  • Adds --force, -f and --all, -a flags to the crictl rm subcommand v1.16.0 · Sep 2019 · source · release history
  • Adds --force, -f flags to crictl rmp command to allow removing containers that are still running v1.15.0 · Jul 2019 · source · release history

example

  • Force remove all running or stopped containers immediately, bypassing graceful shutdown. crictl rm -f -a v1.16.0 · Sep 2019 · source
  • Bulk remove all images from the local store to free up disk space. crictl rmi -a v1.16.0 · Sep 2019 · source
Connection Resilience Management verified Controls retry behavior and backoff policies for establishing connections to the container runtime. 2 releases · 1 other source · first seen Sep 2026

Also counts toward: Command-line interface

release

  • Adds --max-retries flag to crictl to control connection retry attempts with exponential backoff (default: 3). v1.37.0 · Sep 2026 · source · release history
  • crictl now retries failed runtime connections using the --max-retries flag (default: 3) with exponential backoff v1.37.0 · Sep 2026 · source · release history

command line

  • --max-retries — Max retries for connecting to an explicitly set endpoint with exponential backoff (0 to disable, negative for infinite) v1.37.0 · Sep 2026 · command-line history
Container Event Monitoring shipped Streams and retrieves real-time container lifecycle events. 2 releases · 1 other source · first seen Dec 2023

Also counts toward: Command-line interface

release

  • OpenTelemetry tracing now emits a root span per crictl execution that groups all gRPC calls made to the runtime during that invocation. v1.37.0 · Sep 2026 · source · release history
  • Added crictl events command to fetch and print container events v1.29.0 · Dec 2023 · source · release history

example

  • Stream container events in real-time to monitor lifecycle changes across pods and containers. crictl events --container-id <container_id> v1.29.0 · Dec 2023 · source
Tracing and Diagnostics shipped Enables OpenTelemetry tracing and displays resolved configuration details. 2 releases · 1 other source · first seen Apr 2023

Also counts toward: Command-line interface

release

  • crictl execution now includes an OpenTelemetry root span that aggregates all underlying gRPC calls to the runtime v1.37.0 · Sep 2026 · source · release history
  • Adds OTEL tracing via CLI flags --enable-tracing, --tracing-endpoint, and --tracing-sampling-rate-per-million. v1.30.0 · Apr 2024 · source · release history

example

  • Print the resolved crictl configuration (e.g., runtime endpoint, timeout) to stdout without editing config files. crictl config list v1.27.0 · Apr 2023 · source
Container Namespace Visibility shipped Displays pod namespace information in list and inspection outputs to clarify container placement. 3 releases · first seen Sep 2018

Also counts toward: Command-line interface

release

  • Outputs container namespace in crictl ps table and verbose output. v1.32.0 · Dec 2024 · source · release history
  • The inspect command now prints annotations and labels for containers and pods. v1.13.0 · Dec 2018 · source · release history
  • Extends crictl ps output to include the pod ID in its list view 1.12.0 · Sep 2018 · source · release history
Image Filesystem and Cgroup Support shipped Reports detailed container filesystem metrics and supports systemd cgroups. 3 releases · first seen Jul 2023

Also counts toward: Command-line interface

release

  • Allow for imagefsinfo to report container_filesystem and image_filesystem v1.29.0 · Dec 2023 · source · release history
  • Added support for container runtime use systemd cgroups v1.29.0 · Dec 2023 · source · release history
  • crictl imagefsinfo -o table output adds InodesUsed and UsedBytes (human-readable size) columns v1.27.1 · Jul 2023 · source · release history
Operational Timeout Configuration shipped Allows configuring timeout durations for container operations such as stopping. 2 releases · 1 other source · first seen Sep 2017

Also counts toward: Command-line interface

release

  • Adds --timeout option to crictl create, crictl run, and crictl runp requests to cancel long-running CRI operations. v1.20.0 · Jan 2021 · source · release history
  • crictl adds timeout support for container stop (new argument/flag capability to control operation duration) v0.2 · Sep 2017 · source · release history

example

  • Cancel a CRI container create request if it hangs for more than 30 seconds. crictl --timeout 30s create sandbox-id container-config.json sandbox-config.json v1.20.0 · Jan 2021 · source
Container Host Path Validation shipped Executes tests to ensure CRI compliance for volume mounts and host path handling. 2 releases · 1 other source · first seen Jun 2018

release

  • Adds container host path validation tests to the critest suite. v1.11.0 · Jun 2018 · source · release history
  • Adds container host path validation tests in critest 1.11.0 · Jun 2018 · source · release history

example

  • Run the new container host path validation tests to ensure CRI compliance for volume mounts. critest --ginkgo.focus="[Container Host Path Validation]" 1.11.0 · Jun 2018 · source
CRI Conformance for Image Consistency shipped Executes conformance tests to verify that image ID and reference handling remains consistent across CRI operations. 2 releases · first seen Apr 2026

release

  • Adds critest cases to validate CRI API image ID and image ref consistency across operations. v1.36.0 · Apr 2026 · source · release history
  • Adds critest cases to validate image operation consistency end-to-end. v1.36.0 · Apr 2026 · source · release history
Log Stream Selection shipped Provides functionality to retrieve specific log streams such as stdout or stderr from a container. 2 releases · first seen Dec 2019

release

  • New --stream flag on crictl logs allows fetching a specific log stream (stdout/stderr) from a container. v1.33.0 · Apr 2025 · source · release history
  • Enables crictl logs --previous (or -p) to retrieve the previous log output of a container v1.17.0 · Dec 2019 · source · release history
Image Pull Control (renamed from Runtime Handler Support in Pull) shipped Configures timeouts for downloading container images during creation, execution, or direct pull operations. 2 releases · first seen Aug 2020

previously: Image Pull Control

Also counts toward: Command-line interface

release

  • Adds --pull-timeout flag to crictl create, run, and pull commands to cap image pull duration. v1.31.0 · Aug 2024 · source · release history
  • Adds --pull flag to crictl create and crictl run commands to control image pulling behavior v1.19.0 · Aug 2020 · source · release history
Interactive Container Creation shipped Allows the creation and starting of a container in a single command step. 1 release · 1 other source · first seen Sep 2019

Also counts toward: Command-line interface

release

  • Adds crictl container run subcommand to create and start a container in one step v1.16.0 · Sep 2019 · source · release history

example

  • Create and start a new container from an image in a single command without separate run steps. crictl container run --image nginx:latest v1.16.0 · Sep 2019 · source
Image Filesystem Inspection shipped Retrieves detailed filesystem usage statistics and metrics for the container runtime image store. 1 release · 1 other source · first seen Mar 2019

Also counts toward: Command-line interface

release

  • Adds the imagefsinfo subcommand to crictl for querying CRI ImageFSInfo() method details v1.14.0 · Mar 2019 · source · release history

example

  • Check filesystem usage stats for the container runtime via the CRI API crictl imagefsinfo v1.14.0 · Mar 2019 · source
Windows Platform Support shipped Enables the cyber tool to operate on Windows platforms with npipe protocol support for runtime connections. 2 releases · first seen Mar 2018

release

  • Enables connection to the Windows Dockershim endpoint via the new npipe protocol support 1.12.0 · Sep 2018 · source · release history
  • Adds Windows platform support for the crictl CLI v1.0.0-beta.0 · Mar 2018 · source · release history
Container ID Output Mode shipped Outputs only container IDs to simplify script parsing. 1 release · 1 other source · first seen Mar 2018

release

  • Adds crictl ps -q flag to output only container IDs v1.0.0-beta.0 · Mar 2018 · source · release history

example

  • Get a clean list of container IDs for script parsing. crictl ps -q v1.0.0-beta.0 · Mar 2018 · source
Log Stream Filtering and Formatting shipped Allows filtering logs by time duration and displaying timestamps, including supporting log selection for specific streams. 1 release · 1 other source · first seen Dec 2017

Also counts toward: Command-line interface

release

  • Adds --timestamps and --since flags to crictl logs command v1.0.0-alpha.0 · Dec 2017 · source · release history

example

  • Filter pod logs to show only entries from the last 10 minutes with timestamps. crictl logs --since 10m --timestamps <container_id> v1.0.0-alpha.0 · Dec 2017 · source
Container Process Execution Filters shipped Enables targeted execution of commands within containers using filters like name, label, state, or namespace. 1 other source · first seen Sep 2026

example

  • Pull and run a container from a private registry using credentials via environment variables, matching the behaviour already available in crictl pull. CRICTL_CREDS='myuser:mypassword' crictl run container-config.json pod-config.json v1.37.0 · Sep 2026 · source
Version reporting verified Displays the current version of the critest binary. 1 other source · first seen Dec 2025

command line

Container Resource Tuning shipped Allows operators to adjust runtime resource parameters such as OOM scores for running containers. 1 release · first seen Apr 2025

release

  • New --oom-score-adj flag on crictl update lets operators tune the OOM score of a running container. v1.33.0 · Apr 2025 · source · release history
Namespace Filtering shipped Allows filtering queries for pods, containers, or images by their specific namespace. 1 release · first seen Dec 2024

release

  • Adds --namespace flag to crictl ps and crictl inspect for filtering by pod namespace. v1.32.0 · Dec 2024 · source · release history
JSON Schema Inspection shipped Displays JSON schemas for pod, container, and image configurations. 1 release · first seen Aug 2024

Also counts toward: Command-line interface

release

  • Adds crictl [create,runp,run,pull] jsonschema subcommands to display the pod and/or container config JSON schema. v1.31.0 · Aug 2024 · source · release history
Windows Container Resource Limits shipped Allows updating resource limits for containers running on Windows platforms. 1 release · first seen Aug 2021

Also counts toward: Command-line interface

release

  • crictl adds support to update the resource limits to Windows Containers. v1.22.0 · Aug 2021 · source · release history
Multi-architecture Distribution shipped Supports generating release download URLs and builds for additional CPU architectures such as mips64le. 1 release · first seen Apr 2021

release

  • Adds support for mips64le architecture in release download URLs v1.21.0 · Apr 2021 · source · release history
Release Checksum Generation shipped Provides cryptographic checksum files for release artifacts to verify download integrity. 1 release · first seen Apr 2021

release

  • Adds *.sha256 sum files to release artifacts for integrity verification v1.21.0 · Apr 2021 · source · release history
Live Resource Monitoring shipped Provides the ability to watch and stream real-time resource usage statistics for containers. 1 release · first seen Jul 2019

Also counts toward: Command-line interface

release

  • Adds --watch, -w flag to crictl stats command for live monitoring of container resource usage v1.15.0 · Jul 2019 · source · release history
Runtime Handler Configuration shipped Allows specifying a runtime handler via sandbox configuration when pulling images. 1 release · first seen Sep 2018

release

  • Adds runtimeHandler flag to crictl pull via new sandbox config option 1.12.0 · Sep 2018 · source · release history
CRI Protocol Version Compatibility shipped Enables communication with container runtimes using the v1alpha2 version of the Container Runtime Interface protocol. 1 release · first seen Jun 2018

release

  • Updates cri-tools to GA status with CRI protocol version v1alpha2 compatibility. v1.11.0 · Jun 2018 · source · release history
Host Network Pod Port Forwarding shipped Validates pod networking capabilities by forwarding ports within the host network namespace. 1 release · first seen May 2018

release

  • Adds host network pod portforward test to critest for validating pod networking with the host network namespace. 1.0.0-beta.1 · May 2018 · source · release history
Statically Linked Binary Deployment shipped Provides statically linked binaries for critest and crictl to remove external library dependencies. 1 release · first seen May 2018

release

  • Makes both critest and crictl binaries statically linked, removing external library dependencies for binary deployment. 1.0.0-beta.1 · May 2018 · source · release history
Image Digest Retrieval shipped Retrieves the cryptographic digest of container images during inspection or listing. 1 release · first seen Dec 2017

Also counts toward: Command-line interface

release

Result Ordering and Selection shipped Retrieves the most recently created pod or container using specific flags. 1 release · first seen Dec 2017

Also counts toward: Command-line interface

release

  • Adds --latest and --last flags to crictl ps and crictl sandboxes commands v1.0.0-alpha.0 · Dec 2017 · source · release history
Result Truncation Control shipped Controls whether output for pods, containers, and images is truncated or fully displayed. 1 release · first seen Dec 2017

Also counts toward: Command-line interface

release

  • Adds --no-trunc flag to crictl ps, crictl images, and crictl sandboxes commands v1.0.0-alpha.0 · Dec 2017 · source · release history
Shell Auto-completion shipped Provides shell auto-completion scripts for the CLI to improve workflow efficiency. 1 release · first seen Dec 2017

Also counts toward: Command-line interface

release

  • Adds the completion command to crictl for shell auto-completion v1.0.0-alpha.0 · Dec 2017 · source · release history
Verbose Output Support shipped Displays detailed and verbose information for status, inspect, and list commands. 1 release · first seen Dec 2017

Also counts toward: Command-line interface

release

  • Adds verbose output support to crictl status, crictl inspect, and crictl inspects commands v1.0.0-alpha.0 · Dec 2017 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for cri-tools, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail cri-tools puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Website history

kubernetes.io, every change

Kubernetes's home page and 22 more pages as they looked each month from August 2021 to October 2026: 33 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

35 entries

  1. September 20261
  2. April 20261
  3. August 20251
  4. April 20251
  5. December 20241
  6. August 20241
  7. April 20241
  8. December 20231
  9. August 20231
  10. July 20231
  11. April 20231
  12. March 20231
  13. December 20221
  14. August 20221
  15. May 20223
  16. January 20221
  17. August 20211
  18. April 20211
  19. January 20211
  20. August 20201
  21. December 20191
  22. September 20191
  23. July 20191
  24. March 20191
  25. December 20181
  26. September 20181
  27. July 20181
  28. June 20181
  29. May 20181
  30. March 20181
  31. December 20171
  32. September 20171
  33. June 20171
    Show

    35 entries

    Project health

    Issue, contributor and maintainer activity in kubernetes-sigs/cri-tools, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 14 −3 vs prior 12 months
    2. Maintainers 2 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 86% of issues opened, last 12 months
    5. Median time to close 27 days first maintainer reply 28 hours
    6. Open backlog 6 of 422 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 6
    3. Contributors / month 2
    4. Commits / month 7
    5. Stars 2,014
    Issue themes, last 12 months
    • bugs 29%
    • features 28%
    • other 43%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →