Add security regression coverage and reporter credit - #5
Merged
Merged
Conversation
gomission
marked this pull request as ready for review
September 27, 2026 10:36
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.
The classification and receipt fixes on main need broader regression coverage and the security reporter’s requested attribution. This adds tests for compound read/write names, ordinary read tools, proxy traversal and symlink rejection, and standalone receipt reads. SECURITY.md records the patched releases and credits Syed Anas Mohiuddin, Independent Researcher, Maintainer of mcp-safeguard.
Validation: all 90 tests pass on the reconciled branch; git diff --check passes. The PR changes only SECURITY.md and test/security-regressions.test.mjs relative to current main. Runtime code, version 0.3.0-beta.3, and the existing CI workflow remain as on main.