chore: removed unused RegexMaxBlacklist, RegexMaxTimeLimit options

[petruki]

Go's regexp package is backed by RE2, which guarantees linear-time matching by construction and never uses a backtracking engine. This makes it immune to catastrophic backtracking (ReDoS) attacks regardless of how pathological the pattern is, so a blacklist cache or execution time limit adds no protection.

These two ContextOptions fields were defined and defaulted in context.go but never consumed anywhere in the codebase -
processRegexStrategy/regexMatch in local_strategies.go call regexp.Compile/MatchString directly with no cache or timeout logic wired in. Keeping them was misleading, implying a safety mechanism that doesn't exist.

Verified with a new test, "should avoid catastrophic backtracking for regex strategy" (local_strategies_test.go), which runs classic ReDoS patterns like ^(a+)+$ against adversarial input and completes instantly, confirming Go's regexp engine handles these safely without any additional guarding.

BREAKING CHANGE: RegexMaxBlacklist and RegexMaxTimeLimit removed from ContextOptions.

Public API & Configuration Simplification:

• Removed RegexMaxBlacklist and RegexMaxTimeLimit fields from ContextOptions and their associated default values, as well as related logic from context.go and references in the README. [1] [2] [3] [4] [5]
• Updated documentation to remove mentions of regex safety configuration and security features, clarifying that built-in protections are no longer user-configurable. [1] [2] [3]

Testing & Internal Safety:

• Added new tests to local_strategies_test.go to ensure the SDK still avoids catastrophic backtracking in regex strategies, despite removal of user-configurable options.

Other updates:

• Updated context_test.go to remove assertions related to the deleted regex configuration options.
• Cleaned up feature lists in documentation to reflect the current SDK roadmap and available features.

These changes make the SDK configuration simpler for users while maintaining robust internal regex protections.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud