Repository navigation
Fix privacy bypasses, vault data loss, and integration safety - #2
Merged
Merged
Conversation
modelpath-dev
marked this pull request as ready for review
November 6, 2026 13:23
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
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.
Fixes privacy leaks and protects recovery files.
Validation: 96 local tests pass. GitHub tests pass on Python 3.9, 3.10, 3.11 and 3.12. Live NLP inference was not tested locally.
Behavior changes: install the spaCy model explicitly; existing vaults cannot be overwritten; streaming and oversized responses keep placeholders. Middleware limits default to 1 MiB. Detection can still miss sensitive data.