Skip to content

Commit

Permalink
Update integration.md
Browse files Browse the repository at this point in the history
Signed-off-by: jonvnadelberg <[email protected]>
  • Loading branch information
jonvnadelberg authored Nov 15, 2023
1 parent a62a641 commit be01afc
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions content/en/system_config/integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,9 @@ There are several libraries available for developers who want to integrate Sigst
- Cosign is a legacy system that still should be used for signing, and Sigstore-go, which is recommended for use in verification. Cosign was developed with a focus on container image signing and verification, and has a rich CLI and a long legacy of features and development.
- Sigstore-go is a more minimal and friendly API for integrating Go code with Sigstore, with a focus on a unified format for Sigstore verification metadata.
- Sigstore-python is a python language based API.
- Sigstore-JS for code signing NPM packages
- Sigstore-java for Java based applications (pre-release).
- Sigstore-rs for Rust applications (pre-release).
- Sigstore-JS is for code signing NPM packages
- Sigstore-java is for Java based applications (pre-release).
- Sigstore-rs is for Rust applications (pre-release).

**NOTE:** Each of the above libraries has their own entry points. Refer to the specific documentation of each library for details. You can also get support on Slack at the "#clients" channel.

Expand Down

0 comments on commit be01afc

Please sign in to comment.