Feature/add scan for litllm - #18
Merged
Merged
Conversation
First of two planned LiteLLM-related features for the next release — static config scanning now, runtime guardrail hook designed separately later. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…TP endpoints, and guardrails - Implemented scanning for LiteLLM proxy config files to detect hardcoded secrets (LLC001), plaintext HTTP endpoints (LLC002), and missing guardrails (LLC003). - Added new rules to the rule catalog and updated the threat model to include LiteLLM configurations. - Created test fixtures for both safe and vulnerable LiteLLM configurations. - Added unit tests to validate the functionality of the LiteLLM config scanner. - Updated package dependencies to include js-yaml for YAML parsing. - Enhanced sitemap with new documentation links for LiteLLM scanning.
…-controlled inputs and context handling
…age for AI/LLM security reviews
Adds litellm|LLC002|litellm/proxy/_super_secret_config.yaml (reviewed, real plaintext HTTP endpoint). Drops 3 llama_index VEC001 fingerprints that no longer fire after upstream changes to those files.
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.
What and why
Detection logic changes (delete this section if not applicable)
npm run regressionwas run and everyproven/likelyfinding it printed was reviewed against its source linetest-fixtures/vulnerable/andtest-fixtures/safe/src/scanner/catalog.tsandsrc/scanner/explainer.tsboth have an entry for any new rule IDtest/corpus.test.js'sEXPECTED_VULNERABLEwas updated for any new ruleCLI changes (delete this section if not applicable)
test/cli.test.jshas a new or updated case exercising the built binary (src/cli.tschanges aren't covered by any other test file)Checklist
npm run build && npm testpasses