Skip to content
Back to search

nvidia-cuopt-skills

SkillGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/NVIDIA/cuOpt with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/NVIDIA/cuOpt'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/nvidia--cuopt/badge.svg)](/listings/nvidia--cuopt)

HTML

<a href="/listings/nvidia--cuopt"><img src="/api/listings/nvidia--cuopt/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

CUDA/GPU requirements

* CUDA 12.0+ or CUDA 13.0+ * NVIDIA driver >= 525.60.13 (Linux) and >= 527.41 (Windows) * Volta architecture or better (Compute Capability >=7.0)

Python requirements

* Python >=3.12, <=3.14

OS requirements

* Only Linux is supported and Windows via WSL2 * x86_64 (64-bit) * aarch64 (64-bit)

Note: WSL2 is tested to run cuOpt, but not for building.

More details on system requirements can be found [here](https://docs.nvidia.com/cuopt/user-guide/latest/system-requirements.html)

[Latest release branch](https://github.com/NVIDIA/cuopt/tree/release/26.10)

The sections below cover installing the latest release and nightly builds.

Latest release

Pip

Pip wheels are easy to install and easy to configure. Users with existing workflows who uses pip as base to build their workflows can use pip to install cuOpt.

cuOpt can be installed via `pip` from the NVIDIA Python Package Index. Be sure to select the appropriate cuOpt package depending on the major version of CUDA available in your environment:

For CUDA 12.x:

pip install \
  --extra-index-url=https://pypi.nvidia.com \
  nvidia-cuda-runtime-cu12==12.9.* \
  cuopt-server-cu12 cuopt-sh-client

For CUDA 13.x:

pip install \
  --extra-index-url=https://pypi.nvidia.com \
  cuopt-server-cu13 cuopt-sh-client

Conda

cuOpt can be installed with conda (via [miniforge](https://github.com/conda-forge/miniforge)):

All other dependencies are installed automatically when `cuopt-server` and `cuopt-sh-client` are installed.

conda install -c rapidsai -c conda-forge -c nvidia cuopt-server cuopt-sh-client

Container

cuOpt ships two container variants on Docker Hub — an Ubuntu-based image for general use and a Red Hat Universal Base Image 10 (UBI10) image for FIPS 140-3 compliant environments.

Ubuntu image

# For CUDA 12.x
docker pull nvidia/cuopt:latest-cu12

# For CUDA 13.x
docker pull nvidia/cuopt:latest-cu13

The `latest` tag is the latest stable release. To pin a specific version use `<version>-cu12` / `<version>-cu13` (e.g. `26.6.0-cu13`). See the [cuOpt Docker Hub page](https://hub.docker.com/r/nvidia/cuopt/tags) for the full list.

UBI10 image (FIPS 140-3)

Based on Red Hat Universal Base Image 10 (RHEL 10), which ships OpenSSL 3.5 validated under FIPS 140-3. Use this image in environments with strict FIPS or RHEL compliance requirements. UBI10 images are available for CUDA 13.x only.

docker pull nvidia/cuopt:latest-cu13-ubi10

Nightly

Nightly packages are built from the HEAD of the development branch (26.12) and are not as stable as the latest release.

Pip

# For CUDA 12.x
pip install --pre \
  --extra-index-url=https://pypi.nvidia.com \
  --extra-index-url=https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/ \
  nvidia-cuda-runtime-cu12==12.9.* \
  cuopt-server-cu12==26.12.* cuopt-sh-client==26.12.*

# For CUDA 13.x
pip install --pre \
  --extra-index-url=https://pypi.nvidia.com \
  --extra-index-url=https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/ \
  cuopt-server-cu13==26.12.* cuopt-sh-client==26.12.*

Conda

conda install -c rapidsai-nightly -c conda-forge -c nvidia cuopt-server=26.12.* cuopt-sh-client=26.12.*

See the [nightly conda packages](https://anaconda.org/rapidsai-nightly) for the full list.

Container

Nightly images are tagged `<version>a-cu12` / `<version>a-cu13` (Ubuntu) and `<version>a-cu13-ubi10` (UBI10, CUDA 13.x only):

# For CUDA 12.x
docker pull nvidia/cuopt:26.12.0a-cu12

# For CUDA 13.x
docker pull nvidia/cuopt:26.12.0a-cu13

# UBI10, CUDA 13.x only
docker pull nvidia/cuopt:26.12.0a-cu13-ubi10

See the [cuOpt Docker Hub page](https://hub.docker.com/r/nvidia/cuopt/tags) for the full list.

Container notes

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 66 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "nvidia-cuopt-skills",
  3. "owner": {
  4. "name": "NVIDIA"
  5. },
  6. "metadata": {
  7. "description": "Agent skills for NVIDIA cuOpt: routing (VRP, TSP, PDP), LP/MILP/QP, installation (user/developer), and REST server.",
  8. "version": "26.12.00"
  9. },
  10. "plugins": [
  11. {
  12. "name": "cuopt-user-rules",
  13. "source": "./skills/cuopt-user-rules",
  14. "skills": "./",
  15. "description": "Base rules for end users calling NVIDIA cuOpt (routing/LP/MILP/QP/install/server). Not for cuOpt internals — use cuopt-developer for those."
  16. },
  17. {
  18. "name": "cuopt-developer",
  19. "source": "./skills/cuopt-developer",
  20. "skills": "./",
  21. "description": "Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions."
  22. },
  23. {
  24. "name": "cuopt-install",
  25. "source": "./skills/cuopt-install",
  26. "skills": "./",
  27. "description": "Install cuOpt for Python, C, or as a server (pip, conda, Docker) — system requirements, install commands, and verification. Use when the user wants to install or verify cuOpt for any user-facing interface."
  28. },
  29. {
  30. "name": "cuopt-numerical-optimization-formulation",
  31. "source": "./skills/cuopt-numerical-optimization-formulation",
  32. "skills": "./",
  33. "description": "Numerical optimization (LP, MILP, QP) — concepts, problem-text parsing, and formulation patterns. What LP, MILP, and QP are, required formulation questions, modeling elements, common patterns, and how to parse problem statements (parameters, constraints, decisions, objective). Domain concepts; no API or interface."
  34. },
  35. {
  36. "name": "cuopt-numerical-optimization-api",
  37. "source": "./skills/cuopt-numerical-optimization-api",
  38. "skills": "./",
  39. "description": "LP, MILP, and QP (beta) with cuOpt — Python, C, and CLI. Use when the user is solving LP, MILP, or QP with any cuOpt interface."
  40. },
  41. {
  42. "name": "cuopt-multi-objective-exploration",
  43. "source": "./skills/cuopt-multi-objective-exploration",
  44. "skills": "./",
  45. "description": "Trace and interpret the Pareto frontier across competing objectives using repeated single-objective cuOpt solves (weighted-sum and ε-constraint)."
  46. },
  47. {
  48. "name": "cuopt-routing-api-python",
  49. "source": "./skills/cuopt-routing-api-python",
  50. "skills": "./",
  51. "description": "Vehicle routing (VRP, TSP, PDP) with cuOpt — Python API only. Use when the user is building or solving routing in Python."
  52. },
  53. {
  54. "name": "cuopt-server-api-python",
  55. "source": "./skills/cuopt-server-api-python",
  56. "skills": "./",
  57. "description": "cuOpt REST server — start server, endpoints, Python/curl client examples. Use when the user is deploying or calling the REST API."
  58. },
  59. {
  60. "name": "cuopt-skill-evolution",
  61. "source": "./skills/cuopt-skill-evolution",
  62. "skills": "./",
  63. "description": "After solving a non-trivial problem, detect generalizable learnings and propose skill updates. Always active."
  64. }
  65. ]
  66. }
README.md · README · 217 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <!-- AI agents: Start by reading AGENTS.md -->
  2. # cuOpt - GPU-accelerated Optimization
  3. [![Build Status](https://github.com/NVIDIA/cuopt/actions/workflows/build.yaml/badge.svg)](https://github.com/NVIDIA/cuopt/actions/workflows/build.yaml)
  4. [![Dev](https://img.shields.io/badge/dev-26.12.00-blue)](https://github.com/NVIDIA/cuopt/tree/main)
  5. [![Release](https://img.shields.io/github/v/release/NVIDIA/cuopt?label=release&color=blue)](#latest-release)
  6. [![Documentation](https://img.shields.io/badge/docs-latest-brightgreen)](https://docs.nvidia.com/cuopt/user-guide/latest/introduction.html)
  7. [![Docker Hub](https://img.shields.io/badge/docker-nvidia%2Fcuopt-blue?logo=docker)](https://hub.docker.com/r/nvidia/cuopt)
  8. [![Examples](https://img.shields.io/badge/examples-cuopt--examples-orange)](https://github.com/NVIDIA/cuopt-examples)
  9. [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/NVIDIA/cuopt-examples/blob/cuopt_examples_launcher/cuopt_examples_launcher.ipynb)
  10. [![NVIDIA Launchable](https://img.shields.io/badge/NVIDIA-Launchable-76b900?logo=nvidia)](https://brev.nvidia.com/launchable/deploy?launchableID=env-2qIG6yjGKDtdMSjXHcuZX12mDNJ)
  11. [![Videos and Tutorials](https://img.shields.io/badge/Videos_and_Tutorials-red?logo=youtube)](https://docs.nvidia.com/cuopt/user-guide/latest/resources.html#cuopt-examples-and-tutorials-videos)
  12. NVIDIA® cuOpt™ is a GPU-accelerated optimization engine that excels in linear programming (LP), quadratic programming (QP), and vehicle routing problems (VRP), with support for quadratically constrained quadratic programming (QCQP) (beta), second-order cone programming (SOCP) (beta), and mixed integer programming (MIP) (beta). cuOpt enables near real-time solutions for large-scale LPs with millions of variables and constraints and offers easy integration into existing modeling languages with seamless deployment across hybrid and multi-cloud environments.
  13. The cuOpt MIP solver is in beta and under active development. The solver currently excels at finding high-quality feasible solutions quickly with GPU-accelerated primal heuristics. Proving feasible solutions optimal remains under active development.
  14. cuOpt offers easy integration into existing solvers, and seamlessly extends into agent-first optimization workflows through open-source cuOpt agent skills.
  15. The core engine is written in C++ and wrapped with a C API, Python API and Server API.
  16. For the latest version, ensure you are on the `main` branch.
  17. ## Latest Documentation
  18. [cuOpt Documentation](https://docs.nvidia.com/cuopt/user-guide/latest/introduction.html)
  19. ## Supported APIs
  20. cuOpt supports the following APIs:
  21. - C API support
  22. - Linear Programming (LP)
  23. - Quadratic Programming (QP)
  24. - Quadratically Constrained Quadratic Programming (QCQP) (beta)
  25. - Second-Order Cone Programming (SOCP) (beta)
  26. - Mixed Integer Programming (MIP) (beta)
  27. - C++ API support
  28. - cuOpt is written in C++ and includes a native C++ API. However, we do not provide documentation for the C++ API at this time. We anticipate that the C++ API will change significantly in the future. Use it at your own risk.
  29. - Python support
  30. - Routing (TSP, VRP, and PDP)
  31. - Linear Programming (LP)
  32. - Quadratic Programming (QP)
  33. - Quadratically Constrained Quadratic Programming (QCQP) (beta)
  34. - Second-Order Cone Programming (SOCP) (beta)
  35. - Mixed Integer Programming (MIP) (beta)
  36. - Algebraic modeling Python API allows users to easily build constraints and objectives
  37. - Server support
  38. - Linear Programming (LP)
  39. - Routing (TSP, VRP, and PDP)
  40. - Mixed Integer Programming (MIP) (beta)
  41. This repo is also hosted as a [COIN-OR](http://github.com/coin-or/cuopt/) project.
  42. ## Latest Release Notes:
  43. [RELEASE-NOTES.md](RELEASE-NOTES.md)
  44. ## Installation
  45. ### CUDA/GPU requirements
  46. * CUDA 12.0+ or CUDA 13.0+
  47. * NVIDIA driver >= 525.60.13 (Linux) and >= 527.41 (Windows)
  48. * Volta architecture or better (Compute Capability >=7.0)
  49. ### Python requirements
  50. * Python >=3.12, <=3.14
  51. ### OS requirements
  52. * Only Linux is supported and Windows via WSL2
  53. * x86_64 (64-bit)
  54. * aarch64 (64-bit)
  55. Note: WSL2 is tested to run cuOpt, but not for building.
  56. More details on system requirements can be found [here](https://docs.nvidia.com/cuopt/user-guide/latest/system-requirements.html)
  57. ### Latest Release
  58. **[Latest release](https://github.com/NVIDIA/cuopt/releases/latest)** | [Release notes](RELEASE-NOTES.md) | [Documentation](https://docs.nvidia.com/cuopt/user-guide/latest/introduction.html)
  59. > [!TIP]
  60. > **Want a different interface or install method?** The [install selector](https://docs.nvidia.com/cuopt/user-guide/latest/install.html#install-selector) in the docs builds the exact command for the C API, CLI, server, Java, pip, conda or Docker, for your CUDA version.
  61. #### Pip
  62. Pip wheels are easy to install and easy to configure. Users with existing workflows who uses pip as base to build their workflows can use pip to install cuOpt.
  63. cuOpt can be installed via `pip` from [PyPI](https://pypi.org/project/cuopt-cu13/).
  64. Be sure to select the appropriate cuOpt package depending
  65. on the major version of CUDA available in your environment:
  66. For CUDA 12.x:
  67. ```bash
  68. pip install nvidia-cuda-runtime-cu12==12.9.* cuopt-cu12
  69. ```
  70. For CUDA 13.x:
  71. ```bash
  72. pip install cuopt-cu13
  73. ```
  74. #### Conda
  75. cuOpt can be installed with conda (via [miniforge](https://github.com/conda-forge/miniforge)):
  76. All other dependencies are installed automatically when `cuopt` is installed.
  77. ```bash
  78. conda install -c rapidsai -c conda-forge -c nvidia cuopt
  79. ```
  80. #### Container
  81. cuOpt ships two container variants on Docker Hub — an Ubuntu-based image for general use and a Red Hat Universal Base Image 10 (UBI10) image for FIPS 140-3 compliant environments.
  82. ##### Ubuntu image
  83. ```bash
  84. # For CUDA 12.x
  85. docker pull nvidia/cuopt:latest-cu12
  86. # For CUDA 13.x
  87. docker pull nvidia/cuopt:latest-cu13
  88. ```
  89. The `latest` tag is the latest stable release. To pin a specific version use `<version>-cu12` / `<version>-cu13` (e.g. `26.6.0-cu13`). See the [cuOpt Docker Hub page](https://hub.docker.com/r/nvidia/cuopt/tags) for the full list.
  90. ##### UBI10 image (FIPS 140-3)
  91. Based on Red Hat Universal Base Image 10 (RHEL 10), which ships OpenSSL 3.5 validated under FIPS 140-3. Use this image in environments with strict FIPS or RHEL compliance requirements. UBI10 images are available for CUDA 13.x only.
  92. ```bash
  93. docker pull nvidia/cuopt:latest-cu13-ubi10
  94. ```
  95. ### Nightly
  96. Nightly packages are built from the HEAD of the development branch (26.12) and are not as stable as the latest release.
  97. #### Pip
  98. ```bash
  99. # For CUDA 12.x
  100. pip install --pre \
  101. --extra-index-url=https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/ \
  102. nvidia-cuda-runtime-cu12==12.9.* \
  103. cuopt-cu12==26.12.*
  104. # For CUDA 13.x
  105. pip install --pre \
  106. --extra-index-url=https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/ \
  107. cuopt-cu13==26.12.*
  108. ```
  109. #### Conda
  110. ```bash
  111. conda install -c rapidsai-nightly -c conda-forge -c nvidia cuopt=26.12.*
  112. ```
  113. See the [nightly conda packages](https://anaconda.org/rapidsai-nightly) for the full list.
  114. #### Container
  115. Nightly images are tagged `<version>a-cu12` / `<version>a-cu13` (Ubuntu) and `<version>a-cu13-ubi10` (UBI10, CUDA 13.x only):
  116. ```bash
  117. # For CUDA 12.x
  118. docker pull nvidia/cuopt:26.12.0a-cu12
  119. # For CUDA 13.x
  120. docker pull nvidia/cuopt:26.12.0a-cu13
  121. # UBI10, CUDA 13.x only
  122. docker pull nvidia/cuopt:26.12.0a-cu13-ubi10
  123. ```
  124. See the [cuOpt Docker Hub page](https://hub.docker.com/r/nvidia/cuopt/tags) for the full list.
  125. ### Container notes
  126. Both container variants include the same cuOpt packages (`libcuopt`, `cuopt`, `cuopt-server`, `cuopt-sh-client`) and expose the same server entrypoint. They are built and tested for x86-64 and ARM64.
  127. More information about the cuOpt container can be found [here](https://docs.nvidia.com/cuopt/user-guide/latest/cuopt-server/quick-start.html#container-from-docker-hub).
  128. Users who are using cuOpt for quick testing or research can use the cuOpt container. Alternatively, users who are planning to plug cuOpt as a service in their workflow can quickly start with the cuOpt container. But users are required to build security layers around the service to safeguard the service from untrusted users.
  129. ## Build from Source and Test
  130. Please see our [guide for building cuOpt from source](CONTRIBUTING.md#setting-up-your-build-environment). This will be helpful if users want to add new features or fix bugs for cuOpt. This would also be very helpful in case users want to customize cuOpt for their own use cases which require changes to the cuOpt source code.
  131. ## Release Timeline
  132. cuOpt follows the RAPIDS release schedule and is part of the **"others"** category in the release timeline. The release cycle consists of:
  133. - **Development**: Active feature development and bug fixes targeting `main`
  134. - **Burn Down**: Focus shifts to stabilization; new features should target the next release
  135. - **Code Freeze**: Only critical bug fixes allowed; PRs require admin approval
  136. - **Release**: Final testing, tagging, and official release
  137. For current release timelines and dates, refer to the [RAPIDS Maintainers Docs](https://docs.rapids.ai/maintainers/).
  138. ## For AI Coding Agents
  139. See [AGENTS.md](./AGENTS.md) for agent-specific guidelines.
  140. ## Contributing Guide
  141. Review the [CONTRIBUTING.md](CONTRIBUTING.md) file for information on how to contribute code and issues to the project.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.