Add LICENSE and better README (crytic#48)

Author: Xenomega

CONTRIBUTING.md

@@ -13,16 +13,16 @@ To better understand how to make responsible open source contributions, consider
 ### Overview
 When introducing changes to the project, note the following requirements:
 - All changes to the main branch should be introduced via pull requests.
-- Every pull request **MUST** be reviewed by at least one other peer prior to being merged into the main branch.
-- Code **MUST** be supported on Linux, macOS, and Windows.
-- Code **MUST** be sufficiently commented:
+- Every pull request **must** be reviewed by at least one other peer prior to being merged into the main branch.
+- Code **must** be supported on Linux, macOS, and Windows.
+- Code **must** be sufficiently commented:
   - Every type, function, const, and other variables should be accompanied by [doc comments](https://tip.golang.org/doc/comment).
   - Inline comments should be provided for every block of code. These should explain what the block of code is aiming to achieve in plain english.
   - Inline comments should specify any non-trivial caveats with a given piece of code, considerations to make when maintaining it, etc.
   - Any considerations regarding potential weaknesses or future improvements to be made within your code should be accompanied by an inline comment prefixed with `// TODO: `
   - Comments should provide some value to a new contributor and improve code readability.
-- Your changes **MUST NOT** contain copyrighted or licensed works without ensuring copyright law or licenses have not been violated.
-- **Code MUST be compliant with the considerations laid out in the subsections below**.
+- Your changes **must not** contain copyrighted or licensed works without ensuring copyright law or licenses have not been violated.
+- **Code must be compliant with the considerations laid out in the subsections below**.
 
 If any of these requirements are violated, you should expect your pull request to be denied merging until appropriately remediated. 
 
@@ -40,4 +40,4 @@ Pull request reviewers have a responsibility to uphold these standards. Even if
 - Ensure JSON keys are `camelCase` rather than `snake_case`, where possible.
 
 ## License
-TODO
+The license for this software can be found [here](./LICENSE).