Chalk
v1.2.0 open-sourceThe section your link pointed to isn't on Chalk's page any more, so we've brought you to the top.
Chalk allows you to follow code from development, through builds and into production.
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"
require_chalk_mark: true
normalize._COMMIT_ID.callback: func trunc16
}
subscribe("report", "my_dns_beacon")
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: "https://api.eu-west-1.example.com/report"
disable_after_errors: 3
}
subscribe("report", "primary_api")
CHALK_CALLER_ATTESTATION='{"daemon": "crayon", "uid": 1001}' chalk exec ./myapp
chalk insert --inject-binary-into-zip <archive.zip>
chalk exec --no-env-vars <command>
grep '_IMAGE_LAYERS' chalkmark.json
jq '._REPO_URLS' chalkmark.json
jq '.DOCKER_ANNOTATIONS' chalkmark.json
echo "Build exit code: $_OP_EXIT_CODE"
echo "${FAILED_KEYS}" | jq .
echo "$DOCKERFILE_PATH_WITHIN_VCTL"
chalk dump all | chalk load --replace --all -
chalk setup
chalk exec my-image
chalk setup --no-api-login
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
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
Website history
crashoverride.com, every changeCrash 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 → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
28 entries
No entries match these filters.
- August 20261
- July 20261
- June 20262
- March 20261
- February 20261
- December 20251
- September 20252
- August 20251
- April 20252
- February 20251
- January 20251
- November 20241
- October 20241
- July 20241
- June 20242
- May 20242
- March 20241
- February 20241
- January 20245
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.
- Contributors 9 ±0 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 20 days
- Open backlog 48 of 202 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 48
- Contributors / month 3
- Commits / month 3
- Stars 436
- 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.