guardrailsio / guardrails-engine-output-schema-validator Goto Github PK

Right now the webhook only returns the most dominant language (according to the lines of code). We want to be able to:

• Run bundles based on all supported languages in the repo.
• Always run the general bundle (separately)

How many users, repositories, and what the general feedback was.

• general @streichsbaer
• JS: in progress @pxlpnk
• Solidity: @streichsbaer
• ruby: @pxlpnk
• python @pxlpnk
• go @streichsbaer

Research on how to implement it.

Nice to have:

• make it toggleable via config

https://github.com/guardrailsio/guardrails-test-go

• Including filtering out paths and patterns.
• Define what folders to filter by default
• Make the rule mapping functional and apply to the findings.

Make the following changes:

• Ensure the path is relative (without leading ./)

• Ensure the package.json has the private attribute

• Ensure the package name is scoped

• Review whether we even need to publish engines

• Ensure the vulnerable line of code is in the output

• Ensure the raw tool output is in the output -> will be take care of with the new output format</edit andy>

references: guardrailsio/Sprint#129

https://github.com/guardrailsio/guardrails-test-solidity

this ticket helps us trackt the progress and make the work visible.

Can you please share the engines?

I think we should make sure that the engine output already gets rid of any /opt/mount file path and only shows the relative output.

references: guardrailsio/Sprint#129