Skip to content

Conversation

abhijitjavelin
Copy link
Contributor

@abhijitjavelin abhijitjavelin commented Oct 4, 2025

Title

feat: add multi guardrails endpoint for Javelin guardrails. This will make sure to support any newly added guardrails in future seamlessly without raising new prs to repo.

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • I have added a screenshot of my new test passing locally
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

🆕 New Feature
🧹 Refactoring
📖 Documentation
✅ Test

Changes

Multi guardrails endpoint support: Added logic to automatically apply all enabled guardrails in app policy when using javelin_guard as the guardrail name
URL routing enhancement: Modified the Javelin guardrail hook to use /guardrails/apply endpoint instead of /guardrail/{guard_name}/apply when javelin_guard is specified
Documentation update: Added example configuration for the new multi guardrails endpoint in the Javelin guardrails documentation
Comprehensive testing: Added test case test_javelin_guardrail_javelin_guard() to verify the multi guardrails functionality

Files Modified:
litellm/proxy/guardrails/guardrail_hooks/javelin/javelin.py - Core logic for multi guardrails endpoint
docs/my-website/docs/proxy/guardrails/javelin.md - Documentation with example configuration
tests/guardrails_tests/test_javelin_guardrails.py - Test coverage for new functionality

Copy link

vercel bot commented Oct 4, 2025

Someone is attempting to deploy a commit to the CLERKIEAI Team on Vercel.

A member of the Team first needs to authorize it.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Abhijit L seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@abhijitjavelin
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants