elad_pt

Hey @Yggdrasill501, and thank you for responding to this issue! Currently, there is no active branch for this issue, but feel free to fork the project and submit a PR.

This is a good idea! Isn't the environment should be a job property and not an entirely new node? Or maybe each job can have a `review_required` boolean property so...

When we handle https://github.com/CycodeLabs/raven/issues/78 we can move to this. Multi-processing will cause a rate-limit very quickly.

If you think this is a good idea, I can submit a PR to implement it.

I agree, but this still does not address my main concern. When downloading packages from PyPI or other package managers, I can see the digests of the artifacts, but there...

I agree that build logs are not a place to put security information and that this does not come any close to creating a proper SLSA attestation, but maybe it...

Hey and thank you soo much for opening this PR. I think we could leave the `library` folder in the root folder instead of moving it to `src`. Also, Please...

Hey! A few points about the changes: I'm not sure if the `src/raven_cycode` approach is the best one here. I think we should keep the `library` folder outside the `src`...

@BastienFaure Thank you again for taking the time! Regarding the second point, I think it’s a good idea to place the `library` inside the package. I am considering an approach...

@BastienFaure I think that both `src/raven_cycode` and `raven_cycode` make sense when publishing a single package. I see that both approaches are acceptable, so I am ok with the `src/raven_cycode` approach....