Add guard for dataset poisoning - #336
Merged
Merged
Conversation
Contributor
anatoly-scherbakov
approved these changes
Sep 8, 2026
Added a breaking change for the `maxPermutations` option in `jsonld.normalize()` and updated the changelog accordingly.
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.
This PR fixes #179 and RDFC1.0 test case
test074cmaxPermutationsfor normalization, defaulting to 100000. When exceeded, normalization raises JsonLdError with code maximum canonicalization work exceeded.Nonedisables the limit for callers that explicitly want unbounded exact canonicalization.copy.deepcopy(issuer)in canon.py withIdentifierIssuer.copy()in identifier_issuer.py to have same issuer state, but less generic copy overhead in the hot permutation loop.