Size computation for allocation may overflow (#99)

* Size computation for allocation may overflow

Performing calculations involving the size of potentially large strings or slices can result in an overflow (for signed integer types) or a wraparound (for unsigned types). An overflow causes the result of the calculation to become negative, while a wraparound results in a small (positive) number.

internal/patterns/regex_cache.go

@@ -107,6 +107,7 @@ const (
 	JWTPattern = `^[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$`
 
 	// Bearer token pattern (Authorization header)
+	// #nosec G101 -- This is a regex pattern for validation, not a hardcoded credential
 	BearerTokenPattern = `^Bearer\s+([A-Za-z0-9._~+/-]+=*)$`
 
 	// Client ID pattern (alphanumeric with common separators)
@@ -119,6 +120,7 @@ const (
 	SessionIDPattern = `^[a-fA-F0-9]{32,128}$`
 
 	// CSRF token pattern (base64url)
+	// #nosec G101 -- This is a regex pattern for validation, not a hardcoded credential
 	CSRFTokenPattern = `^[A-Za-z0-9_-]+$`
 
 	// Nonce pattern (base64url)