This document is relevant for: Inf1, Inf2, Trn1, Trn2, Trn3

Neuron Open Source Repositories and Contribution#

AWS Neuron provides open source code and samples for some of its components, libraries, and tools under the Apache 2.0 license. The current public repositories open to contribution at this time are listed below.

Important

This page lists the AWS Neuron repositories that are currently open to contribution. For the complete list of public AWS Neuron open source projects, see the aws-neuron GitHub organization.

Neuron Open Source GitHub Repositories#

TorchNeuron PyTorch Extension Open Source

Source code for the Neuron Native PyTorch extension and the TorchNeuron library that implements it for AWS Trainium. Note: TorchNeuron is currently in private Beta. Contact your Neuron account representative to request access.

Neuron Agentic Development Open Source

AI agents, skills, and agent-ready code samples for authoring, debugging, profiling, and analyzing NKI kernels inside agentic IDEs such as Claude Code and Kiro. See Neuron Agentic Development for the full feature overview.

Neuron Kernel Library Open Source

Source code and specifications for the pre-built kernels that ship with the NKI Library .

vLLM for Neuron Open Source

Source code for the vLLM integrations with Neuron, supporting AWS Trainium and Inferentia.

NKI Samples

Full code examples that support NKI kernel development.

How to Contribute to Neuron Open Source#

Contributions via pull requests are appreciated! Before sending us a pull request, please ensure that:

  1. You are working against the latest source on the main` branch.

  2. You check existing open and recently merged pull requests and GitHub Issues to make sure someone else hasn’t addressed the problem already.

  3. You open a GitHub Issue for the repo to discuss any significant work.

To send us a pull request:

  1. Fork the repository.

  2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.

  3. Ensure local tests pass.

  4. Commit to your fork using clear commit messages.

  5. Send us a pull request, answering any default questions in the pull request interface.

  6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.

GitHub provides documentation on forking a repository and creating a pull request.

For the specific details on licenses and contributing to each OSS repo, review the CONTRIBUTING.md pages linked below:

This document is relevant for: Inf1, Inf2, Trn1, Trn2, Trn3