This could work for distribution but it's not a solution for shielding the developer(s). If you have already publicly published code with attribution I would no

This could work for distribution but it's not a solution for shielding the developer(s). If you have already publicly published code with attribution I would not consider tor + forward pawns to be 100% invulnerable to forensics to determine authorship. So now you're looking at tackling code transformation without obfuscation to cover provenance, which sounds non-trivial. (Your comment made me wonder if coPilot can also be used to fingerprint developers based on their existing code.)