A command-line interface (CLI) is required to perform attestations.
The CLI can operate with your Chainloop account as an alternative to our web user interface. Note that not all the functionality that exists in the UI has been exposed to the CLI yet.
To install the latest version for macOS, Linux or Windows (using WSL) just choose one of the following installation method.
Installation Script
Installation Script
curl -sfL https://docs.chainloop.dev/install.sh | bash -s
you can retrieve a specific version with
# You can find all the available versions at https://github.com/chainloop-dev/chainloop/releases
curl -sfL https://docs.chainloop.dev/install.sh | bash -s -- --version vx.x.x
and customize the install path (default to /usr/local/bin)
curl -sfL https://docs.chainloop.dev/install.sh | bash -s -- --path /my-path
If cosign is present in your system, in addition to the checksum check, a signature verification will be performed. This behavior can be enforced via the --force-verification flag.
curl -sfL https://docs.chainloop.dev/install.sh | bash -s -- --force-verification
From Source
From Source
git clone [email protected]:chainloop-dev/chainloop
cd chainloop && make -C app/cli build
./app/cli/bin/chainloop version
=> chainloop version v0.8.93-3-ged05b96
Configure CLI
If you are running your own instance of Chainloop Platform. You can make the CLI point to your instance by using the chainloop config save command.
chainloop config save \
--control-plane my-controlplane.acme.com \
--artifact-cas cas.acme.com
Another option would be to build a custom version of CLI with default endpoints' values pointing at your Chainloop instance. Please learn more about this method in the following doc.
Authentication
Authenticate to Chainloop Platform by running
$ chainloop auth login
Once logged in, your next step would be to create a Chainloop organization. Think of organizations as workspaces or namespaces.
$ chainloop organization create --name my-organization
# INF Organization "my-organization" created!