chainloop-dev / labs

Chainloop Labs

Chainloop Labs

Warning

The Chainloop Labs project is meant to test new UX and experimental features. This project is under active development, and you should expect breaking changes. Use at your own risk.

Welcome to Chainloop Labs - where we innovate, experiment, and educate to shape the future of Chainloop.

About Chainloop Labs

Chainloop Labs is a space where we collaborate, research, and develop new features and resources for Chainloop. Our mission is to Automate Trust for Secure Software Supply Chain.

Key Objectives

• Innovation: Explore and experiment.

• Education: Create educational materials, resources, and demos to help users understand and utilize Chainloop effectively.

• Collaboration

Getting Started

• Reusable Github Worflows
• Tools

Community / Discussion / Support

Got a question, comment, or idea? Please don't hesitate to reach out via:

• GitHub Issues
• Discord Community Server

Contributing

Want to get involved? Contributions are welcome.

If you are ready to jump in and test, add code, or help with documentation, please follow the instructions on our Contribution page. At all times, follow our Code of Conduct.

See the issue tracker if you're unsure where to start, especially the Good first issue label.

Changelog

Take a look at the list of releases to stay tuned for the latest features and changes.

License

Chainloop is released under the Apache License, Version 2.0. Please see the LICENSE file for more information.

labs's Issues

Dagger Module (preview)

Explore the creation of a Dagger.io module for Chainloop.

This module should follow the new version of the Dagger engine that seems to improve encapsulation and composition.

As a first step, we could focus on a module written in Go, that could perform Chainloop attestations.

Once we have the module, we should look into publishing it into the daggerverse

Some useful links

• daggerverse
• module building docs
• Discord Channel

issue failing the attestation in reusable workflow

Our failure callbacks might not be finding the attestation_id since for example this job should have been marked as failed

https://github.com/chainloop-dev/chainloop/actions/runs/8848550250/job/24298667196

cc/ @danlishka @javirln