{"id":13472998,"url":"https://github.com/crashappsec/chalk","last_synced_at":"2026-01-18T05:37:59.521Z","repository":{"id":196654466,"uuid":"696723696","full_name":"crashappsec/chalk","owner":"crashappsec","description":"Chalk allows you to follow code from development, through builds and into production.","archived":false,"fork":false,"pushed_at":"2026-01-12T16:57:56.000Z","size":66608,"stargazers_count":414,"open_issues_count":48,"forks_count":23,"subscribers_count":13,"default_branch":"main","last_synced_at":"2026-01-12T22:24:26.472Z","etag":null,"topics":["cicd","containers","docker","elf","metadata","observability","security-tools"],"latest_commit_sha":null,"homepage":"https://chalkproject.io","language":"Nim","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/crashappsec.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2023-09-26T10:08:06.000Z","updated_at":"2026-01-12T10:52:45.000Z","dependencies_parsed_at":"2024-04-15T15:11:59.887Z","dependency_job_id":"4470b398-9a20-4d31-b006-6d241b346a14","html_url":"https://github.com/crashappsec/chalk","commit_stats":null,"previous_names":["crashappsec/chalk"],"tags_count":43,"template":false,"template_full_name":null,"purl":"pkg:github/crashappsec/chalk","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/crashappsec%2Fchalk","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/crashappsec%2Fchalk/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/crashappsec%2Fchalk/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/crashappsec%2Fchalk/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/crashappsec","download_url":"https://codeload.github.com/crashappsec/chalk/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/crashappsec%2Fchalk/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28531059,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-18T00:39:45.795Z","status":"online","status_checked_at":"2026-01-18T02:00:07.578Z","response_time":98,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cicd","containers","docker","elf","metadata","observability","security-tools"],"created_at":"2024-07-31T16:00:59.838Z","updated_at":"2026-01-18T05:37:59.515Z","avatar_url":"https://github.com/crashappsec.png","language":"Nim","funding_links":[],"categories":["Nim"],"sub_categories":[],"readme":"![Chalk Logo](https://chalkproject.io/logo.svg)\n\n[![tests](https://github.com/crashappsec/chalk/actions/workflows/tests.yml/badge.svg?branch=main\u0026event=push)](https://github.com/crashappsec/chalk/actions/workflows/tests.yml?query=branch%3Amain)\n\n## About Chalk\n\nChalk™ captures metadata at build time, and can add a small 'chalk mark' (metadata) to any\nartifacts, so they can be identified in production. Chalk can also extract chalk marks and collect\nadditional metadata about the operating environment when it does this.\n\nUsing Chalk, you can build a graph connecting people, development, builds and production, so that\ndevops engineers understand what is happening in the development process, and so that developers\ncan understand what is happening in the infrastructure.\n\n## How-tos\n\nYou can use Chalk to solve a variety of specific use cases such as:\n\n### Create software security supply chain compliance reports automatically\n\nMany companies and the US Government are now mandating suppliers to provide supply chain statements\nwhen delivering software. This how to is an easy button to deliver the\n[software bill of materials (SBOM)](https://www.cisa.gov/sbom), code and\nbuilds provenance and supports [SLSA](https://www.slsa.dev), Supply-chain Levels for Software\nArtifacts, [level 2](https://slsa.dev/spec/v1.0/levels) compliance (an emerging supply chain\nstandard) before SLSA [level 1](https://slsa.dev/spec/v1.0/levels) has been mandated. Follow this\nhow-to on our docs site [here](https://chalkproject.io/docs/advanced-topics/sbom/).\n\n### Gathering runtime information using exec reports\n\nFrom a code base, easily understand the environments where code and even particular branches are\nrunning. Gather code owners for the applications and code repos. Follow this how-to on our docs\nsite [here](https://chalkproject.io/docs/getting-started/exec/).\n\n### Deploy Chalk globally using Docker\n\nYou can deploy Chalk by setting a global symlink for Docker and having it call Chalk, so that every\nbuild that runs through your build server using Docker, will automatically be 'chalked'. It's a\ntechnique that can be combined with chalks ability to deploy tools and configure monitoring, to\nautomatically add security controls and collect information for every application. Follow this\nhow-to on our docs site [here](https://chalkproject.io/docs/getting-started/ci-cd/)]\n\n## Getting started\n\nWe recommend following the [getting started guide](https://chalkproject.io/docs/getting-started/)\non our documentation web site. Full documentation is also available directly inside the CLI.\n\nWe provide free binary downloads on our [release page](https://chalkproject.io/download/).\n\n## Issues\n\nIf you encounter any issues with Chalk please submit a GitHub issue to\n[this repo](https://github.com/crashappsec/chalk/issues).\n\n## Ideas and feedback\n\nWe are constantly learning about emerging use cases for Chalk, and are always interested in hearing\nabout how others are using it. We are also interested in ideas and feature requests.If you would\nlike to talk, please get in touch using hello@crashoverride.com.\n\n## Making contributions\n\nWe welcome contributions but do require you to complete a contributor license agreement or CLA. You\ncan read the CLA and about our process [here](https://crashoverride.com/docs/other/contributing).\n\n## Getting additional help\n\nIf you need additional help including a demo of the cloud platform, please contact us using\nhello@crashoverride.com\n\n## License\n\nChalk is licensed under the GPL version 3 license.\n\n## Try our cloud platform.\n\nOur cloud hosted platform is built using Chalk. It makes enterprise deployments easy, and provides\nadditional functionality including prebuilt integrations to enrich your data.\n\nYou can learn more at [crashoverride.com](https://crashoverride.com/).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcrashappsec%2Fchalk","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcrashappsec%2Fchalk","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcrashappsec%2Fchalk/lists"}