Decodify fails to detect Base64 encoded string when lacking padding symbol if it could also be hex-encoded about decodify HOT 5 CLOSED

Is there a way to specify non-recursive operation? I like the simple operation of identifying the encoding scheme automatically, but there are many values which are only encoded once, but result in a "valid" encoding scheme after the first decode operation and the tool attempts to decode again and fails.

from decodify.

I'm assuming it prioritizes hex first, and when the input is ambiguous, I understand it's difficult. Obviously checking the content for a non-hex character would allow you to identify that it is Base64, but if the input is actually valid in both, maybe present both possible outputs?

from decodify.

What we can do is to either change the order of checks for Base64 and hex or include an option to specify the encoding.

from decodify.

Yes we can do that.

from decodify.

Can you verify if the patch is working?

from decodify.