Source code is also obfuscated using a simple key to avoid extracting the string from the executable.

And in the home page, perhaps missed, was:

Takes a single perl script, converts the block using a simple encoding with an optionally defined key.

Which you can see from the usage involves the '-key' option.

  -key <str>         Specify key for encode/decode of embedded script

So your claim that the source code is provided intact is false.

And yes, it's weak encryption. Clearly if someone wants to attack an obfuscation like this, they'll do some sort of runtime attack rather than try to decode the script.

You also state: "Finally, there's an implicit claim that an executable can be made from the generated .c file, but it's not obvious how to do that"

And again, from the usage:

  -exe <exec>        Compile the code into an executable

I think that's pretty simple

But to help make it clearer, I've added the compilation command to the comments at the top of the C output.

And in the home page, perhaps missed, was:

Wasn't missed, just not relevant.

And yes, it's weak encryption

It's encoding, not encryption or obfuscation. There must be a secret for encryption.

So your claim that the source code is provided intact is false.

No, even when a key is specified, the code is provided intact.

Compile the code into an executable

I missed that, thanks.

It's encoding, not encryption or obfuscation.
You are in disagreement with the rest of the world with the definition of "encryption".
1. Encryption does NOT require a secret. Look up ROT13 on wikipedia
2. My weak encryption does have a secret if you use choose to hide the key properly in the source. That's up to you.

I suggest, for your perusal:

http://en.wikipedia.org/wiki/Encryption
http://en.wikipedia.org/wiki/Rot13
http://perlmonks.org/?node_id=890723