PAGES
← all tools
◆ Software Supply Chain Security

Chalk

v1.2.0 open-source

Chalk allows you to follow code from development, through builds and into production.

Summary

Chalk is an open-source software-supply-chain tool that embeds a cryptographically verifiable chain of custody into software artifacts during the build process, running as a command-line tool for platform engineers. It is free under an open-source license and positions itself alongside tools for provenanceprovenanceEvidence recording where a software artifact came from and how it was built, including its source and build process. It helps a consumer check that the artifact matches a trusted build. tracking. The tool supports embeddingembeddingLists of numbers a model produces to represent the meaning of text, images or code, so similar items sit close together. They power semantic search and RAG. marks into containers, executables, and scripts, automatically collecting environmental metadata and signatures, and it is currently in active development with recent releases occurring within the tracking window.

Chalk allows you to follow code from development, through builds and into production.

How Chalk helps

Which artifact in production came from which commit, branch, and build?

reads the chalk mark embedded in the container, binary, or script and returns the correlated build metadata — committer, branch, package changes, and container base — that was captured at build time

Has this binary or container been altered since it was built?

checks the tamperproof chalk mark against the artifact to confirm whether the identifier and its signed contents still match what was recorded at build

What software components and versions actually shipped inside this artifact?

pulls the SBOM generated automatically during the build (via Docker's tooling or a Syft fallback) and ties it to the same chalk mark as the rest of the provenance data

Who or what signed off on this build, and can that signature be verified independently?

reports the Sigstore signature attached to the build attestation, pushed to the registry alongside the image, so the signer and integrity of the build can be checked outside the build environment

Where did this artifact actually run, and under what cloud context?

collects cloud-specific metadata at startup by probing common cloud metadata interfaces, giving a record of the runtime environment tied back to the same artifact

Can provenance data reach my monitoring systems when normal outbound HTTPS is blocked?

falls back to encoding chalk key values into DNS lookups when the primary delivery sink is unavailable, walking a configured chain of backup sinks until one succeeds

all 24 features, with the evidence for each →

Languages

Not documented

Features

24 capabilities

Built from Chalk'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 →

  • Chalk covers 1 of the 5 supply chain security capabilities we track.

What Chalk offers you

  • Command-line interface3
  • CI/CD pipeline integration1
  • REST API
All capabilities 24 capabilities
Artifact chalk marking shipped Inserts cryptographically verifiable chalk marks into artifacts such as binaries, containers, and scripts to track software provenance and attestation from build through production. 14 releases · 3 other sources · first seen Jan 2024

release 14 total

  • Starts populating DOCKER_CHALK_ADDED_LABELS with labels injected during docker build, keyed by original name v1.1.1 · Jun 2026 · source · release history
  • All chalk attestations now use OCI Image and Distribution 1.1 spec. v1.0.0 · Mar 2026 · source · release history
  • _OP_ANCESTOR_ARGVS reports all parent processes argv which allows to put chalk invocations within the context of CI scripts. v1.0.0 · Mar 2026 · source · release history
  • New configuration keyspec.<key>.only_object_store forces key to be only reported via object store. v1.0.0 · Mar 2026 · source · release history
  • _PROCESS_FD_INFO, _PROCESS_MOUNT_INFO, _OP_TCP_SOCKET_INFO, _OP_UDP_SOCKET_INFO, _OP_IPV4_INTERFACES, _OP_IPV4_ROUTES, _OP_IPV6_INTERFACES, _OP_IPV6_ROUTES, _OP_ARP_TABLE, and _PROCESS_DETAIL keys now have mixed-type values instead of all-strings. v1.0.0 · Mar 2026 · source · release history
  • BUILD_ID environment variable now references the GitHub Actions job ID instead of the workflow ID. v0.6.1 · Sep 2025 · source · release history

docs

  • Adds cryptographically verifiable chalk marks to artifacts (binaries, containers, scripts) to track software provenance and attestation from build through produ

example

  • Ingest caller metadata into the artifact using an external daemon's attestation envelope CHALK_CALLER_ATTESTATION='{"daemon": "crayon", "uid": 1001}' chalk exec ./myapp v1.1.0 · Jun 2026 · source
  • Insert chalk mark into compiled binary CHALK_PASSWORD=…== ./chalk insert ./hello 2>/dev/null | jq '.[]|._CHALKS[]|.'
Docker platform and command wrapping control shipped Provides granular control over Docker builds including multi-platform support, entrypoint wrapping, CMD customization, and architecture-specific binary downloads. 15 releases · 1 other source · first seen Jan 2024

Also counts toward: Command-line interface

release 15 total

  • Adds native chalking support for Mach-O binaries with automatic signing via codesign or rcodesign when available on Linux v1.1.0 · Jun 2026 · source · release history
  • Adds Docker registry push support with new docker.docker_registry, docker.docker_registry.<name>.docker_login_get, and docker.docker_registry.<name>.docker_push configuration sections v1.1.0 · Jun 2026 · source · release history
  • New configuration docker_log_level specifically to configure docker wrapping log verbosity level. v1.0.0 · Mar 2026 · source · release history
  • New configurations docker.busybox_container and docker.binfmt_container for pinning binfmt and busybox images. v1.0.0 · Mar 2026 · source · release history
  • Adds ZIP archive injection support for AWS Lambda via config zip.inject_binary, zip.inject_binary_allowed_extensions (default .zip), and zip.inject_zip_size_threshold (default 50Mb), plus CLI flag --inject-binary-into-zip. v0.6.0 · Sep 2025 · source · release history
  • docker.update_dockerignore config key to automatically update .dockerignore so files are copied during legacy builder builds that don't support --build-context. v0.5.9 · Aug 2025 · source · release history

example

  • Inject the chalk binary into a ZIP archive for AWS Lambda deployment with size threshold. chalk insert --inject-binary-into-zip <archive.zip> v0.6.0 · Sep 2025 · source
DNS sink for telemetry in restricted environments shipped Encodes chalk metadata into DNS lookup hostnames via configurable domain templates, providing a telemetry channel for air-gapped or HTTPS-restricted environments. 8 releases · 3 other sources · first seen Jan 2024

release 8 total

  • Adds dns sink type to encode chalk key values into DNS lookups for telemetry where HTTPS egress is restricted. v1.2.0 · Aug 2026 · source · release history
  • New dns sink type encodes chalk key values into DNS lookup hostnames via a domain_template with {KEY} placeholders, providing a telemetry channel for environments where HTTPS egress is restricted; supports dns_server, require_chalk_mark, and per-key normalize.<KEY>.callback fields in sink_config. v1.2.0 · Aug 2026 · source · release history
  • Adds git.fetch_connect_timeout and git.fetch_transfer_timeout config keys to control network timeouts. v1.1.3 · Jul 2026 · source · release history
  • Sanitizes git origin keys in reports to strip embedded basic auth credentials. v0.6.4 · Dec 2025 · source · release history
  • Adds _OP_ARTIFACT_MOUNTED key to indicate if an artifact file is externally mounted. v0.6.0 · Sep 2025 · source · release history
  • Configuration ignore_patterns now applies to all chalk operations, not just chalking ones. v0.6.0 · Sep 2025 · source · release history

example

  • Beacon chalk metadata over DNS in air-gapped or HTTPS-restricted environments, truncating the commit ID to fit within the 63-character DNS label limit. func trunc16(v: string) { return slice(v, 0, 16) } sink_config my_dns_beacon { sink: "dns" domain_template: "{_COMMIT_ID}.{METADATA_ID}.beacons.example.com" dns_server: "10.0.0.1:5353"… v1.2.0 · Aug 2026 · source
  • Emit telemetry over DNS when HTTPS is blocked by configuring a DNS sink with a domain template. sink_config my_dns_beacon { sink: "dns" domain_template: "{_COMMIT_ID}.{METADATA_ID}.beacons.example.com" dns_server: "10.0.0.1:5353" require_chalk_mark: true normalize._COMMIT_ID.callback: func… v1.2.0 · Aug 2026 · source
  • Disable environment variable scanning for artifacts if they contain sensitive data not relevant to the scan. chalk exec --no-env-vars <command> v0.6.0 · Sep 2025 · source
Per-chalk-mark report emission shipped Optionally emits one report per chalk mark rather than bundling all marks into a single report, configurable per output configuration section or custom report. 6 releases · 1 other source · first seen Nov 2024

release

  • outconf sections now support per_chalk_reports: true and custom_report sections support per_chalk: true to emit one report per chalk mark instead of bundling all marks into a single report. v1.2.0 · Aug 2026 · source · release history
  • Adds support for per-chalk report emission via per_chalk_reports: true in outconf sections and per_chalk: true in custom_report sections. v1.2.0 · Aug 2026 · source · release history
  • FAILED_KEYS and _OP_FAILED_KEYS now store a list of error objects per key instead of a single object; consumers must handle the new list format v1.1.1 · Jun 2026 · source · release history
  • FAILED_KEYS and _OP_FAILED_KEYS now store a list of error objects per key instead of a single object to record multiple distinct failures v1.1.1 · Jun 2026 · source · release history
  • exec.heartbeat.* configs moved to singleton exec.heartbeat.* (e.g., exec.heartbeat.run, exec.heartbeat.rate). v0.6.0 · Sep 2025 · source · release history
  • The _EXEC_ID key is now emitted on every command execution to uniquely identify the chalk process lifetime v0.4.14 · Nov 2024 · source · release history

example

  • Split reports per chalk mark for finer-grained telemetry by enabling per_chalk_reports in an outconf section. outconf my_per_chalk { per_chalk_reports: true # ... other settings ... } v1.2.0 · Aug 2026 · source
HTTP sink metadata headers and presign header forwarding shipped Sends chalk metadata as HTTP headers with every post and presign request, and optionally forwards headers from presign redirect responses into the upload PUT to enable server-side metadata injection. 5 releases · first seen Sep 2025

release

  • Adds x-forward-headers support to the presign sink for copying redirect response headers into the upload PUT. v1.2.0 · Aug 2026 · source · release history
  • Adds new X-Chalk-Version, X-Chalk-Operation, X-Chalk-Action-Id, X-Content-Length, X-Chalk-Digest-Sha256, and X-Chalk-Attempt metadata headers to post and presign sinks. v1.2.0 · Aug 2026 · source · release history
  • post and presign sinks now send chalk metadata headers with every request: X-Chalk-Version, X-Chalk-Operation, X-Chalk-Action-Id, X-Content-Length, X-Chalk-Digest-Sha256, and X-Chalk-Attempt (1-based retry counter). v1.2.0 · Aug 2026 · source · release history
  • presign sink now supports x-forward-headers: header names listed in that response header are copied from the redirect response into the upload PUT, enabling metadata injection (e.g. X-Amz-Meta-*) that cannot be encoded in the presigned URL. v1.2.0 · Aug 2026 · source · release history
  • Adds asynchronous metadata collection after chalk exec via the postexec report, using configs docker.prep_postexec, exec.postexec.run, exec.postexec.fork, exec.postexec.nice, exec.postexec.access_watch.prep_tmp_path, exec.postexec.access_watch.initial_poll_time,… v0.6.0 · Sep 2025 · source · release history
Sink failover and error-based auto-disable shipped Automatically routes chalk report delivery to a configured fallback sink chain when the primary sink is unavailable, and disables sinks that exceed a configurable consecutive-error threshold. 4 releases · 1 other source · first seen Aug 2026

release

  • Adds fallback_sink_config field to sink_config blocks for fallback chain delivery when primary sink fails or is disabled. v1.2.0 · Aug 2026 · source · release history
  • Adds automatic sink disabling on repeated errors with configurable disable_after_errors threshold for post, presign, and s3 sinks. v1.2.0 · Aug 2026 · source · release history
  • New fallback_sink_config field on all sink_config sections names a backup sink to use when the primary is unavailable or disabled; chalk walks the full fallback chain on each delivery failure, with each sink tracking its own disable_after_errors counter independently. v1.2.0 · Aug 2026 · source · release history
  • post, presign, and s3 sinks now automatically disable themselves on repeated errors via a configurable disable_after_errors: <int> threshold (default 3); 4xx responses (except 429) disable immediately, while 5xx, 429, and network errors increment a consecutive-failure counter. v1.2.0 · Aug 2026 · source · release history

example

  • Configure a fallback sink chain so that if the primary API fails, reports are delivered to a backup endpoint. sink_config primary_api { sink: "post" uri: "https://api.us-east-1.example.com/report" disable_after_errors: 3 fallback_sink_config: "backup_api" } sink_config backup_api { sink: "post" uri:… v1.2.0 · Aug 2026 · source
Cloud provider metadata collection shipped Captures metadata from AWS, GCP, and Azure cloud environments including function ARNs, instance data, and IMDSv2 information. 5 releases · first seen Jan 2024

release

  • Host operational context is accessible via _OP_HOST_SYSNAME, _OP_HOST_NODENAME, _OP_HOST_RELEASE, _OP_HOST_VERSION, and _OP_HOST_MACHINE. v0.4.0 · May 2024 · source · release history
  • Adds arm64 Linux binary support v0.3.1 · Jan 2024 · source · release history
  • Added minimal AWS lambda metadata collection. It includes only basic information about lambda function such as its ARN and its runtime environment v0.3.0 · Jan 2024 · source · release history
  • Initial metadata collection for GCP and Azure cloud providers via new metadata keys v0.2.0 · Jan 2024 · source · release history
  • Adds an AWS IMDSv2 collection module with associated metadata keys for cloud environment data v0.1.2 · Jan 2024 · source · release history
Chalk reporting process nice-level control shipped Allows configuring the OS scheduling priority (nice level) of the chalk reporting process independently for each operation phase. 4 releases · first seen Feb 2026

release

  • New exec.nice config field sets the nice level (range 0-19, default 5) for the chalk reporting process after fork, reverted before postexec and heartbeat so each phase uses its own independent value. v1.2.0 · Aug 2026 · source · release history
  • --log-format CLI argument added to match log_format configuration. v1.0.0 · Mar 2026 · source · release history
  • DOCKER_BASE_IMAGE_ID is replaced with DOCKER_BASE_IMAGE_CONFIG_DIGEST. v1.0.0 · Mar 2026 · source · release history
  • Adds log_format configuration option allowing users to force plain or JSON log output for non-interactive runs v0.6.6 · Feb 2026 · source · release history
Report template key updates shipped Report templates subscribe to extended runtime keys (e.g. `_FAILED_KEYS`) that capture failures occurring after the build step, replacing the narrower chalk-time originals. 4 releases · first seen Apr 2025

release

  • FAILED_KEYS is removed from most default report templates; they now subscribe to _FAILED_KEYS instead. v1.2.0 · Aug 2026 · source · release history
  • report_default, report_large, and insertion_default templates have had FAILED_KEYS removed and _FAILED_KEYS added; consumers reading FAILED_KEYS from these report templates must switch to _FAILED_KEYS. v1.2.0 · Aug 2026 · source · release history
  • Adds _ERR_INFO and _FAILED_KEYS runtime artifact keys that capture errors/failures occurring after the chalk mark is embedded, replacing the old ERR_INFO and FAILED_KEYS in most report templates. v1.2.0 · Aug 2026 · source · release history
  • New copy_report_template_keys("source", "dest") function to duplicate keys between report templates. v0.5.5 · Apr 2025 · source · release history
Artifact metadata collection shipped Captures specific details about artifacts including file paths, environment variables, and layer digests for deeper visibility. 4 releases · first seen Sep 2025

Also counts toward: Command-line interface

release

  • Adds VCS_MODIFIED_FILES, VCS_UNTRACKED_FILES, VCS_DIFF_STAT, and VCS_DIFF_PATCH to expose git working tree state. v1.1.3 · Jul 2026 · source · release history
  • Adds caller attestation plugin ingesting JSON envelope via CHALK_CALLER_ATTESTATION or CHALK_CALLER_ATTESTATION_FILE environment variables v1.1.0 · Jun 2026 · source · release history
  • Adds environment variable scanning for artifacts (default on) with configurable env_vars setting or --[no-]env-vars flag, and adds _OP_ARTIFACT_ENV_VAR_NAME key. v0.6.0 · Sep 2025 · source · release history
  • Adds _OP_ARTIFACT_PATH_WITHIN_VCTL key to report the path of the file in the git repo. v0.6.0 · Sep 2025 · source · release history
Build origin identification shipped Captures metadata identifying the repository and resource origin of a CI/CD build to establish software provenance. 4 releases · first seen May 2024

Also counts toward: CI/CD pipeline integration

release

  • New chalk plugins for collecting CI metadata for Jenkins, Buildkite, BitBucket, CircleCI, Azure DevOps, and TeamCity. v1.0.0 · Mar 2026 · source · release history
  • BUILD_ORIGIN_URI environment key reports the URI of the resource that originated the CI build. v0.5.5 · Apr 2025 · source · release history
  • Added the BUILD_COMMIT_ID key to report the commit ID that triggered the build in CI/CD. v0.4.5 · Jun 2024 · source · release history
  • Adds BUILD_ORIGIN_ID, BUILD_ORIGIN_KEY, BUILD_ORIGIN_OWNER_ID and BUILD_ORIGIN_OWNER_KEY chalk keys to identify the origin repository using a CI/CD-provided identifier v0.4.1 · May 2024 · source · release history
Runtime artifact and host telemetry keys shipped Captures post-mark error details, monotonic and wall-clock timing, and heartbeat counters as runtime keys available in chalk reports. 3 releases · first seen Aug 2026

release

  • Adds _MONOTIME, _SINCE_TIMESTAMP, _SINCE_MONOTIME, and _HEARTBEAT_COUNT runtime host keys for timing and heartbeat tracking in reports. v1.2.0 · Aug 2026 · source · release history
  • Two new runtime artifact keys capture post-mark errors: _ERR_INFO (superset of ERR_INFO, full error log through end of operation) and _FAILED_KEYS (superset of FAILED_KEYS, includes post-build step failures); all report templates except report_all now subscribe to these instead of the chalk-time originals. v1.2.0 · Aug 2026 · source · release history
  • Four new runtime host keys for timing and heartbeat tracking: _MONOTIME (monotonic clock at operation start, in ms), _SINCE_TIMESTAMP (wall-clock ms since process start), _SINCE_MONOTIME (monotonic ms since process start), and _HEARTBEAT_COUNT (1-based counter, present only in heartbeat reports). v1.2.0 · Aug 2026 · source · release history
Containerized runtime execution and beaconing shipped Enables running the cyber tool within containers to inject beacon data into entry points for periodic runtime metadata collection. 2 releases · 1 other source · first seen Jan 2024

Also counts toward: Command-line interface

release

  • Enables chalk.env to extract chalkmark from chalk.json in AWS Lambda environments where LAMBDA_TASK_ROOT is defined, and adds run-time keys mirroring _BUILD_* keys for non-chalking operations. v0.6.0 · Sep 2025 · source · release history
  • Adds the chalk exec command to inject beacon data into container entry points for runtime metadata collection v0.1.2 · Jan 2024 · source · release history

example

  • Run a container with Chalk to enable runtime beaconing and periodic heartbeat reports chalk exec my-image v0.1.2 · Jan 2024 · source
Post-execution metadata collection shipped Collects operational metadata such as exit codes, cloud vendor information, and error details during or after artifact operations. 3 releases · first seen Oct 2024

release

  • Reports all IMDSv2 errors in FAILED_KEYS or _OP_FAILED_KEYS. v0.6.0 · Sep 2025 · source · release history
  • Adds FAILED_KEYS and _OP_FAILED_KEYS metadata keys containing collected error details (code, message, description) for keys that could not be collected v0.4.13 · Oct 2024 · source · release history
  • Adds _OP_EXIT_CODE key to report the exit code of external commands like chalk docker build v0.4.13 · Oct 2024 · source · release history
GitLab CI collapsible log sections shipped Automatically wraps chalk report output in GitLab CI section markers so chalk reports appear as collapsible sections in the GitLab job log UI. 2 releases · first seen Aug 2026

release

  • GitLab CI log output is now automatically wrapped in section_start/section_end markers with collapsed=true when GITLAB_CI is set, making chalk reports collapsible in the GitLab job log UI. v1.2.0 · Aug 2026 · source · release history
  • Adds collapsible GitLab CI log section support when running inside a GitLab CI job (GITLAB_CI is set). v1.2.0 · Aug 2026 · source · release history
OCI attestation attachment methods shipped Supports attaching attestations via OCI Referrers API or uploading build context layers to registry. 2 releases · first seen Jun 2026

release

  • Adds support for OCI Referrers API via new attestation_use_oci_tag config key to attach attestations using the subject field instead of legacy tags v1.1.1 · Jun 2026 · source · release history
  • Adds docker_context_upload configuration under docker.docker_registry.<name>.docker_push.<name> to upload the build context as a .tar.gz layer attached to an OCI attestation manifest v1.1.1 · Jun 2026 · source · release history
Caller attestation ingestion shipped Ingests caller metadata into the artifact using an external daemon's attestation envelope. 1 release · 1 other source · first seen Jun 2026

release

  • Adds caller attestation plugin ingesting JSON envelope via CHALK_CALLER_ATTESTATION or CHALK_CALLER_ATTESTATION_FILE environment variables v1.1.0 · Jun 2026 · source · release history

example

  • Ingest caller metadata into the artifact using an external daemon's attestation envelope CHALK_CALLER_ATTESTATION='{"daemon": "crayon", "uid": 1001}' chalk exec ./myapp v1.1.0 · Jun 2026 · source
Extended CI workflow metadata shipped Exposes detailed build context fields including raw git ref, workflow name, path, hash, and attempt number. 2 releases · first seen Dec 2025

release

  • Adds BUILD_REF field to expose the raw git ref of the build (e.g. refs/pull/5/merge). v0.6.4 · Dec 2025 · source · release history
  • Adds BUILD_WORKFLOW_NAME, BUILD_WORKFLOW_PATH, and BUILD_WORKFLOW_HASH fields to describe the CI workflow used for a build. v0.6.4 · Dec 2025 · source · release history
Attestation key management refactoring shipped Implements a new configuration schema for attestation key providers, backup services, and embedded keys, replacing the legacy secret manager settings. 2 releases · first seen Jan 2024

release

  • Config keys use_signing_key_backup_service, signing_key_backup_service_url, signing_key_backup_service_auth_config_name, signing_key_backup_service_timeout, and signing_key_location are removed; use new attestation.key_provider, attestation_key_embed.location, and attestation_key_backup.* settings… v0.3.4 · Mar 2024 · source · release history
  • secret_manager_url renamed to signing_key_backup_service_url v0.3.0 · Jan 2024 · source · release history
Kubernetes deployment metadata shipped Captures environment variables for Kubernetes deployments during execution. 1 release · first seen Jun 2026

release

  • Adds Kubernetes operator integration populating _K8S_* environment variables during chalk exec for richer deployment metadata v1.1.0 · Jun 2026 · source · release history
ML model marking codecs shipped Supports marking ML model files in-place or via sidecar JSON for formats like GGUF and safetensors. 1 release · first seen Jun 2026

release

  • Adds gguf, safetensors, and sidecar codecs for marking ML model files in-place or via sidecar JSON v1.1.0 · Jun 2026 · source · release history
Process-level metadata collection shipped Captures metadata at the process level using a proc file system collection module. 1 release · first seen Jan 2024

release

  • Adds a proc file system collection module for capturing process-level metadata v0.1.2 · Jan 2024 · source · release history
Technology stack detection shipped Detects and captures information about the technologies used in the build and runtime environment, including programming languages, databases, and servers. 1 release · first seen Jan 2024

release

  • Added experimental support for detection of technologies used at chalk and runtime (programming languages, databases, servers, etc.) v0.3.0 · Jan 2024 · source · release history
Sigstore signing and key pair management shipped Sets up Sigstore signing and key pairs to cryptographically sign chalk marks. 1 other source

Shared capability: Artifact signing

example

  • Set up Sigstore signing and key pair ./chalk setup

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 Chalk, 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 Chalk 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

crashoverride.com, every change

Crash Override's home page and 9 more pages as they looked each month from November 2021 to October 2026: 20 renders, 8 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

28 entries

  1. August 20261
  2. July 20261
  3. June 20262
  4. March 20261
  5. February 20261
  6. December 20251
  7. September 20252
  8. August 20251
  9. April 20252
  10. February 20251
  11. January 20251
  12. November 20241
  13. October 20241
  14. July 20241
  15. June 20242
  16. May 20242
  17. March 20241
  18. February 20241
  19. January 20245
    Show

    28 entries

    Project health

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

    1. Contributors 9 ±0 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close < 1 day first maintainer reply 20 days
    6. Open backlog 48 of 202 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 48
    3. Contributors / month 3
    4. Commits / month 3
    5. Stars 436
    Issue themes, last 12 months
    • features 2%
    • docs 1%
    • other 97%

    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

    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 →