Supply Chain Transparency Log

Edit Package rekor
https://github.com/sigstore/rekor

Rekor's goals are to provide an immutable tamper resistant ledger of metadata generated within a software projects supply chain. Rekor will enable software maintainers and build systems to record signed metadata to an immutable record. Other parties can then query said metadata to enable them to make informed decisions on trust and non-repudiation of an object's lifecycle. For more details visit the sigstore website

The Rekor project provides a restful API based server for validation and a transparency log for storage. A CLI application is available to make and verify entries, query the transparency log for inclusion proof, integrity verification of the transparency log or retrieval of entries by either public key or artifact.

Rekor fulfils the signature transparency role of sigstore's software signing infrastructure. However, Rekor can be run on its own and is designed to be extensible to working with different manifest schemas and PKI tooling.

Refresh
Refresh
Source Files
Filename Size Changed
rekor-0.12.2.tar.gz 0000668839 653 KB
rekor-zypper-verify.sh 0000000941 941 Bytes
rekor.changes 0000013880 13.6 KB
rekor.spec 0000003015 2.94 KB
vendor.tar.xz 0005254475 5.01 MB
Revision 11 (latest revision is 21)
Richard Brown's avatar Richard Brown (RBrownFactory) accepted request 1007909 from Marcus Meissner's avatar Marcus Meissner (msmeissn) (revision 11)
- updated to rekor 0.12.2 (jsc#SLE-23476):
  - add description on /api/v1/index/retrieve endpoint
  - Adding e2e test coverage
  - export rekor build/version information
  - Use POST instead of GET for /api/log/entries/retrieve metrics.
  - Search through all shards when searching by hash (forwarded request 1007274 from msmeissn)
Comments 0
openSUSE Build Service is sponsored by