docs(research): compare wolfSSL libsodium BoringSSL Botan feasibility

[Rahulatram321]

Summary

Mentorship workstream PR for C/C++ and OpenSSL expansion.

Includes

• Branch-specific scoped deliverable
• DCO-signed commit
• Ready for iterative review and follow-up commits

Checklist

• Rebased from upstream/main
• Non-empty branch diff
• Signed-off commit

[AdityaKoranga]

I don’t understand the idea behind this PR

[Rahulatram321]

I don’t understand the idea behind this PR

Hi @AdityaKoranga , thank you for taking the time to review this!
This PR is part of my LFX Mentorship application for the 'Extending language and library support in CBOMkit' project.
The idea is to provide a pre-application research document comparing the feasibility of integrating wolfSSL, libsodium, BoringSSL, and Botan into sonar-cryptography as future C/C++ cryptographic library targets — covering parser availability, API surface complexity, and mapping effort to existing model/ classes.
This is a proposal/research deliverable (not production code yet) — meant to demonstrate my understanding of the project scope and show how I would approach the research track of the mentorship.
Happy to restructure this as a GitHub Discussion or docs page if that format works better for the project. Would love your feedback on the approach!

[Rahulatram321]

Hi Aditya Koranga Sir, thank you for taking the time to review this! This PR is part of my LFX Mentorship application for the 'Extending language and library support in CBOMkit' project. The idea is to provide a pre-application research document comparing the feasibility of integrating wolfSSL, libsodium, BoringSSL, and Botan into sonar-cryptography as future C/C++ cryptographic library targets — covering parser availability, API surface complexity, and mapping effort to existing model/ classes. This is a proposal/research deliverable (not production code yet) — meant to demonstrate my understanding of the project scope and show how I would approach the research track of the mentorship. Happy to restructure this as a GitHub Discussion or docs page if that format works better for the project. Would love your feedback on the approach! Please find the cover letter and resume attached for more detailed reference.

…

On Thu, 28 May, 2026, 15:40 AddyTiv, ***@***.***> wrote: *AdityaKoranga* left a comment (cbomkit/sonar-cryptography#448) <#448 (comment)> I don’t understand the idea behind this PR — Reply to this email directly, view it on GitHub <#448?email_source=notifications&email_token=BER7XKBCEGHROBZU7O37FS345AGBFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJWGI4TKOBUGE32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4562958417>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BER7XKHHFVRCBPKM7LABIEL45AGBFAVCNFSM6AAAAACZLENCDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNRSHE2TQNBRG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>