Erwan

This issue still stand and was updated when the taint changes came out. I've just updated my priority list, which is now basically: - ~~The ability to specify the source...

Wohop, that's actually awesome, I've edited my post about this!

Such behaviour happens with basically any uppercased keywords, for example: - TRUE - FALSE - INT - NULL

I have the same issue with the below examples: ```ruby # frozen_string_literal: true def valid_credentials?(response) response.code == 302 && [*response.headers['Set-Cookie']]&.any? { |cookie| cookie =~ /wordpress_logged_in_/i } end def errored_response?(response) response.code...