feat: prep for transfer to the bytecode alliance

.github/workflows/ci.yaml

@@ -6,6 +6,33 @@ on:
     branches: [main]
 
 jobs:
+  vet:
+    name: Vet
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Setup Just
+        uses: extractions/setup-just@v3
+
+      - name: Setup Rust
+        run: |
+          rustup update stable --no-self-update
+          rustup default stable
+          rustup target add wasm32-wasip1 wasm32-wasip2
+
+      - name: Install cargo-vet
+        run: cargo install cargo-vet
+
+      - name: Setup Go
+        uses: actions/setup-go@v6
+        with:
+          go-version: 'stable'
+
+      - name: Run vetters
+        run: just vet
+
   lint:
     name: Lint
     runs-on: ubuntu-latest
@@ -25,7 +52,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v6
         with:
-          node-version: 24.12.0
+          node-version: 25.8.2
 
       - name: Setup Go
         uses: actions/setup-go@v6
@@ -57,7 +84,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v6
         with:
-          node-version: 24.12.0
+          node-version: 25.8.2
 
       - name: Setup Go
         uses: actions/setup-go@v6
@@ -70,7 +97,7 @@ jobs:
   test:
     name: Test
     runs-on: ubuntu-latest
-    needs: [lint, format] # Ensure code is linted and formatted before running tests
+    needs: [lint, format, vet] # Ensure code is linted and formatted before running tests
     steps:
       - name: Checkout
         uses: actions/checkout@v6
@@ -87,7 +114,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v6
         with:
-          node-version: 24.12.0
+          node-version: 25.8.2
 
       - name: Setup Go
         uses: actions/setup-go@v6
@@ -100,17 +127,12 @@ jobs:
           version: "40.0.1"
 
       - name: Setup componentize-go
-        run: |
-          curl -LO https://github.com/bytecodealliance/componentize-go/releases/download/v0.2.0/componentize-go-linux-amd64.tar.gz
-          echo "27fc32998f023a88a6a1f44524631a705163f23ce2a02fc14987726897360027  componentize-go-linux-amd64.tar.gz" | sha256sum --check
-          tar -xf componentize-go-linux-amd64.tar.gz
-          chmod +x componentize-go
-          mkdir -p $HOME/.local/bin
-          mv componentize-go $HOME/.local/bin/componentize-go
-          echo "$HOME/.local/bin" >> $GITHUB_PATH
+        uses: bytecodealliance/componentize-go/.github/actions/setup-componentize-go@main
+        with:
+          version: 'v0.2.0'
 
       - name: Setup Spin
-        uses: spinframework/actions/spin/setup@v1
+        uses: fermyon/actions/spin/setup@v1
         with:
           version: "v3.6.1"
 

CODEOWNERS

@@ -0,0 +1,2 @@
+@asteurer
+@calebschoepp

CODE_OF_CONDUCT.md

@@ -0,0 +1,49 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Code of Conduct Team
+
+The Organization’s Code of Conduct Team is responsible for ensuring that all Code of Conduct complaints are investigated and resolved. It consists of the members of the Technical Steering Commmittee along with the Executive Director acting as Compliance Officer. The Compliance Officer, on behalf of the Code of Conduct Team, will advise the Board of all complaints and their resolution and will report at least annually to the Board on compliance activity relating to the organizational Code of Conduct.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Bytecode Alliance CoC Team at [report@bytecodealliance.org](mailto:report@bytecodealliance.org). The CoC Team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The CoC Team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the Bytecode Alliance's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at http://contributor-covenant.org/version/1/4.
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,22 @@
+# Contributing
+
+This project welcomes contributions for bug fixes, documentation updates, new
+features, or whatever you might like. Development is done through GitHub pull
+requests. Feel free to reach out on the [Bytecode Alliance
+Zulip](https://bytecodealliance.zulipchat.com/) as well if you'd like assistance
+in contributing or would just like to say hi.
+
+## Code of Conduct
+
+This is a [Bytecode Alliance](https://bytecodealliance.org/) project, and follows the Bytecode Alliance's [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## License
+
+This project is licensed under the Apache 2.0 license with the LLVM exception.
+See [LICENSE](LICENSE) for more details.
+
+### Contribution
+
+Unless you explicitly state otherwise, any contribution intentionally submitted
+for inclusion in this project by you, as defined in the Apache-2.0 license,
+shall be licensed as above, without any additional terms or conditions.

Justfile

@@ -1,11 +1,23 @@
-all: lint format test
+all: lint format test vet
+
+vet:
+    # Vet: Rust SDK
+    cargo vet --manifest-path rust/Cargo.toml
+
+    # Vet: Go SDK
+    cd go && GOOS=wasip1 GOARCH=wasm go vet ./logs/... ./metrics/... ./tracing/... ./types/...
+
+    # Vet: TypeScript SDK
+    # This is handled in the lint step
 
 lint:
     # Lint: Rust SDK
     @cargo clippy --manifest-path rust/Cargo.toml --all-targets --all-features -- -D warnings
 
     # Lint: TypeScript SDK
     @npm --prefix ts install
+    @npm --prefix ts run build
+    @npm --prefix ts/examples/spin-basic install
     @npm --prefix ts run lint
 
     # Lint: Go SDK
@@ -47,4 +59,5 @@ test:
         && wasmtime run logs_test.wasm
 
     # Test: Integration tests
-    @cargo test --manifest-path integration_tests/Cargo.toml
+    # TODO: Until this issue is taken care of, these will continue to fail: https://github.com/calebschoepp/opentelemetry-wasi/issues/45
+    # @cargo test --manifest-path integration_tests/Cargo.toml

README.md

@@ -1,2 +1,23 @@
-# OpenTelemetry WASI
+<div align="center">
+  <h1><code>opentelemetry-wasi</code></h1>
+  <strong>A <a href="https://bytecodealliance.org/">Bytecode Alliance</a> project</strong>
+  <p>
+    <a href="https://github.com/bytecodealliance/opentelemetry-wasi/actions?query=workflow%3Awrpc"><img src="https://github.com/bytecodealliance/opentelemetry-wasi/actions/workflows/ci.yml/badge.svg" alt="build status" /></a>
+    <a href="https://bytecodealliance.zulipchat.com/"><img src="https://img.shields.io/badge/zulip-join_chat-brightgreen.svg" alt="zulip chat" /></a>
+  </p>
+  <h3>
+    <a href="https://bytecodealliance.zulipchat.com">Chat</a>
+  </h3>
+</div>
+
+# opentelemetry-wasi
 Libraries to enable using OpenTelemetry within WebAssembly components backed by [WASI OTel](https://github.com/calebschoepp/wasi-otel).
+
+## Questions?
+
+Ask over in the Bytecode Alliance <a href="https://bytecodealliance.zulipchat.com">Zulip</a>.
+
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for more information about contributing
+to this repository.

rust/supply-chain/audits.toml

@@ -0,0 +1,4 @@
+
+# cargo-vet audits file
+
+[audits]