Hi Chris!
That is a great question. I based my parser code off of the one by Patrick van Bergen on the Procurios blog How do I write my own parser? (for JSON) because it looked very clean and translated well to LabVIEW. Patrick's code was MIT Licensed which is very permissive and allows sublicensing, etc, so I think I will do the same for i3-JSON.
i3-Twitter and i3-OAuth will be BSD 3-clause because they use components from OpenG and BSD 3-clause seems to be the OpenG license of choice. BSD 3-clause is still very permissive, and as far as I can tell compatible with the MIT License so I don't really expect any problems there.
I'll make sure to update the packages to reflect this in the next release and let me know if you have any other suggestions!
Milan