Add LLMSecTest integration - #582
Open
wehnsdaefflae wants to merge 1 commit into
Open
Conversation
An OWASP LLM Top 10 scanner that runs against a deployed Haystack pipeline over HTTP. No component to import and no code change; it exercises the prompt assembly, retrieval, output handling and model together.
|
Someone is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
integrations/llmsectest.md.LLMSecTest scans a deployed Haystack pipeline against the OWASP Top 10 for LLM Applications and writes SARIF, HTML, JSON, Markdown and a CycloneDX SBOM. It is MIT, on PyPI, and funded by the German Prototype Fund.
It works over HTTP and adds nothing to a pipeline: no component to import, no wrapper, no code change. That is why I filed it as an Evaluation Framework rather than a Custom Component. If you would rather it sat under a different
type, or decided it does not belong on the index at all, say so and I will close this without any hard feelings.Eight Haystack pipelines are in the project's own daily regression cohort, and the entry says plainly that they are deliberately undefended fixtures rather than examples of good practice. Every report is published unedited at https://llmsec.dev/reports/.
Both
pypiandrepoare set. No logo, since the optional one I have is not sized for your index.