Contact - Security assessment of implementation

I recently completed an independent academic security assessment of tiny-AES-c. Some of the behaviors discussed in the report may overlap with existing issues.

I would like to pass the report trough Kokke or another maintainer, but could not find a contact information besides a spam email. If somebody as a contact, I would be grateful. Otherwise I'll probably just publish it.

Thanks

No implementation file or test is identified; start by reviewing the independent academic security assessment and the behaviors it discusses. Compare those points with existing issues, then define the specific security change or report outcome with a maintainer before coding.

Written by the indexing model from the issue text.