97b4d91da9* fixes the codec comparison. instead of pointer compares by name * per-platform when chalk object is copied, same codec ref is used * fixes docker image digest matching in tests * add STRACE option to tests to strace chalk calls * fixes docker warning when using CMD shell style for probe detection |
||
|---|---|---|
| .github | ||
| configs | ||
| serverless | ||
| src | ||
| tests | ||
| .clabot | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| chalk.nimble | ||
| CHANGELOG.md | ||
| CODEOWNERS | ||
| config.nims | ||
| docker-bake.hcl | ||
| docker-compose.yml | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SECURITY.md | ||
About Chalk
Chalk™ captures metadata at build time, and can add a small 'chalk mark' (metadata) to any artifacts, so they can be identified in production. Chalk can also extract chalk marks and collect additional metadata about the operating environment when it does this.
Using Chalk, you can build a graph connecting people, development, builds and production, so that devops engineers understand what is happening in the development process, and so that developers can understand what is happening in the infrastructure.
How-tos
You can use Chalk to solve a variety of specific use cases such as:
Create software security supply chain compliance reports automatically
Many companies and the US Government are now mandating suppliers to provide supply chain statements when delivering software. This how to is an easy button to deliver the software bill of materials (SBOM), code and builds provenance and supports SLSA, Supply-chain Levels for Software Artifacts, level 2 compliance (an emerging supply chain standard) before SLSA level 1 has been mandated. Follow this how-to on our docs site here.
Gathering runtime information using exec reports
From a code base, easily understand the environments where code and even particular branches are running. Gather code owners for the applications and code repos. Follow this how-to on our docs site here.
Deploy Chalk globally using Docker
You can deploy Chalk by setting a global symlink for Docker and having it call Chalk, so that every build that runs through your build server using Docker, will automatically be 'chalked'. It's a technique that can be combined with chalks ability to deploy tools and configure monitoring, to automatically add security controls and collect information for every application. Follow this how-to on our docs site here]
Getting started
We recommend following the getting started guide on our documentation web site. Full documentation is also available directly inside the CLI.
We provide free binary downloads on our release page.
Issues
If you encounter any issues with Chalk please submit a GitHub issue to this repo.
Ideas and feedback
We are constantly learning about emerging use cases for Chalk, and are always interested in hearing about how others are using it. We are also interested in ideas and feature requests.If you would like to talk, please get in touch using hello@crashoverride.com.
Making contributions
We welcome contributions but do require you to complete a contributor license agreement or CLA. You can read the CLA and about our process here.
Getting additional help
If you need additional help including a demo of the cloud platform, please contact us using hello@crashoverride.com
License
Chalk is licensed under the GPL version 3 license.
Try our cloud platform.
Our cloud hosted platform is built using Chalk. It makes enterprise deployments easy, and provides additional functionality including prebuilt integrations to enrich your data.
You can learn more at crashoverride.com.