feat(*): Adds additional documentation to the top level

CODE_OF_CONDUCT.md

@@ -0,0 +1,5 @@
+# Code of Conduct
+
+This project adheres to the [Bytecode Alliance Code of
+Conduct](https://github.com/bytecodealliance/governance/blob/main/CODE_OF_CONDUCT.md). Any
+violations of the code of conduct should be reported to [email protected]

CONTRIBUTING.md

@@ -0,0 +1,23 @@
+# Contributing to Rust OCI Wasm
+
+Thanks for your interest in contributing to Rust OCI Wasm! Our process for contribution is fairly
+straightforward as this is a small project. Bug fixes and new features must be submitted using a
+pull request. For new features, it is also recommended to first open an issue to discuss the feature
+before submitting a pull request.
+
+## Working with the code
+
+The only required tooling outside of a standard development tool chain is 
+
+- A valid [Rust installation](https://www.rust-lang.org/tools/install)
+- Docker installed (for running integration tests)
+
+As this is a wrapper around another crate, most of our tests are done via integration tests, which
+can be found in the `tests/` directory. Please note that these tests are run as part of the CI 
+pipeline, so they must pass before a pull request can be merged.
+
+## Releasing the project
+
+Releases are done by project maintainers as deemed necessary. Releases are entirely automated and
+can be triggered by tagging the desired commit with a tag of the form `vX.Y.Z`. This will
+automatically trigger the release process, which pushes the crate to crates.io.

README.md

@@ -4,3 +4,5 @@ This repo contains a Rust crate implementing the [OCI Wasm
 Specification](https://tag-runtime.cncf.io/wgs/wasm/deliverables/wasm-oci-artifact/). It is a thin
 wrapper around the [oci-distribution](https://crates.io/crates/oci-distribution) crate with the
 specific config types needed for the OCI Wasm specification.
+
+**A [Bytecode Alliance](https://bytecodealliance.org/) hosted project**

SECURITY.md

@@ -0,0 +1,13 @@
+# Security
+
+## Supply chain security
+
+This project uses GitHub's dependabot to file automatic issues for dependency security updates.
+Maintainers will review and apply these updates as soon as possible.
+
+## Reporting a security vulnerability
+
+If you believe you have found a security vulnerability in this project, please report it using the
+"Security" tab at the top of the repo. This project uses the GitHub security features to allow for
+confidential vulnerability reporting and fixes. Any security bugs will receive a CVE number and be
+tracked through the GitHub security feature.