The idea is:
When exporting a workflow, catch common API key names and offer to encrypt the values with an encryption library, or give the ability to ignore and leave one or more fields unencrypted
I think it would be beneficial to add this because:
It would save users from having to go through their entire JSON file and blot out every sensitive field!
Any resources to support this?
See here (GitHub Secret Scanning: Importance & Best Practices) for GitHub’s approach to secret detection
Are you willing to work on this?
Yes, but I would need support with it.