# Algorand's fork of libsodium

**URL:** https://forum.algorand.co/t/algorands-fork-of-libsodium/645
**Category:** General
**Created:** [June 13, 2019, 1:33pm UTC](https://forum.algorand.co/t/algorands-fork-of-libsodium/645 "2019-06-13T13:33:58Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![wayne](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/wayne/32/105_2.png) [@wayne](https://forum.algorand.co/u/wayne)
#### Post date: [June 13, 2019, 1:33pm UTC](https://forum.algorand.co/t/algorands-fork-of-libsodium/645/1 "2019-06-13T13:33:58Z")

</div>

Very interesting to see libsodium fork _in tree_. Forking libsodium is not entirely unusual but I have never seen it in tree before

> **[algorand/go-algorand](https://github.com/algorand/go-algorand/tree/master/crypto/libsodium-fork)**
>
> Algorand's official implementation in Go. . Contribute to algorand/go-algorand development by creating an account on GitHub.

Is there an easy way to see what you guys have changed? How about security audit reports?

---

_[View the full topic](https://forum.algorand.co/t/algorands-fork-of-libsodium/645)._