Skip to content
Back to search

elements

NVIDIA Design System and UI Agent Harness for AI/ML Factories, Robotics, and Autonomous Vehicles

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/elements 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/elements'

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--elements/badge.svg)](/listings/nvidia--elements)

HTML

<a href="/listings/nvidia--elements"><img src="/api/listings/nvidia--elements/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.

These steps run a script from the network that findsafeskills does not scan.

To set up repository dependencies and run the full build, run the following commands at the **root** of the repository:

The CI pipeline also builds Go starters. Install [Go 1.26.x](https://go.dev/doc/install) before running the full local CI pipeline.

# install dependencies https://mise.en.dev/getting-started.html
curl https://mise.run | sh
~/.local/bin/mise run setup

Troubleshooting

If you are coming from development from a different repository, you may need to refresh the repository toolchain with mise. Run `mise run install` at the root of the project to install the Node.js, pnpm, Vale, Go, Git LFS, and package versions from `mise.toml` and `pnpm-lock.yaml`.

If you actively switch between different repositories, run commands through `mise exec --` or activate mise in your shell so it switches tools automatically.

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.

README.md · README · 180 lines · 1 finding marked

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

  1. # NVIDIA Elements
  2. NVIDIA Design System and UI Agent Harness for AI/ML Factories, Robotics, and Autonomous Vehicles.
  3. - **Agent-ready tooling:** CLI and MCP expose component APIs, tokens, examples, imports, validation, and setup to terminals and AI assistants.
  4. - **Framework agnostic:** Web Components run in React, Angular, Vue, Svelte, Lit, plain HTML, server-rendered templates, and mixed stacks.
  5. - **Built for AI infrastructure:** Operational UI for AI/ML workloads, autonomous vehicle tools, and robotics consoles.
  6. - **Stable API contracts:** Skills and lint guide authoring best practices, common UI patterns, and automated static analysis.
  7. ## NVIDIA Elements Skill
  8. Install the Elements agent skill with the open [skills](https://www.skills.sh/nvidia/elements/elements) CLI:
  9. ```shell
  10. npx skills add https://github.com/nvidia/elements --skill elements
  11. ```
  12. ## Requests and Contributions
  13. - [NVIDIA Elements Documentation](https://NVIDIA.github.io/elements/)
  14. - [Contribution Guidelines](https://NVIDIA.github.io/elements/docs/about/contributions/)
  15. - [Feature request](https://github.com/NVIDIA/elements/issues/new?issuable_template=feature)
  16. - [Bug report](https://github.com/NVIDIA/elements/issues/new?issuable_template=default)
  17. - [Official NVIDIA Elements DESIGN.md](https://NVIDIA.github.io/elements/docs/design-md/)
  18. ## Organization
  19. The repository uses a top-level **repository** with individual **project** directories.
  20. Project directories have their own `package.json` and commands. Run CI and development setup at the root **repository** level.
  21. Examples of projects include:
  22. - `/projects/starters` - Suite of standardized starter apps for Elements and Patterns
  23. - `/projects/core` - Elements library: curated UI maintained by the Elements team
  24. - `/projects/themes` - Elements Theme library: provides a set of supported themes for Element based projects
  25. - `/projects/styles` - Elements Styles library: provides a set of CSS utilities for layout and typography
  26. ## Development
  27. ### Setup
  28. To set up repository dependencies and run the full build, run the following commands at the **root** of the repository:
  29. The CI pipeline also builds Go starters. Install [Go 1.26.x](https://go.dev/doc/install) before running the full local CI pipeline.
  30. ```shell
  31. # install dependencies https://mise.en.dev/getting-started.html
  32. curl https://mise.run | sh
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 49 on GitHub
  33. ~/.local/bin/mise run setup
  34. ```
  35. #### Troubleshooting
  36. If you are coming from development from a different repository, you may need to refresh the repository toolchain with mise. Run `mise run install` at the root of the project to install the Node.js, pnpm, Vale, Go, Git LFS, and package versions from `mise.toml` and `pnpm-lock.yaml`.
  37. If you actively switch between different repositories, run commands through `mise exec --` or activate mise in your shell so it switches tools automatically.
  38. ### Building
  39. Both the top-level repository and each project have a set of standardized npm scripts. To build and test all projects, run `mise exec -- pnpm run ci` at the root of the repository.
  40. #### Top-Level Repository
  41. - `ci`: run full build/lint/test
  42. - `ci:all`: entire CI process: build, lint, unit/lighthouse/visual tests
  43. - `ci:reset`: clear all caches/dependencies then reinstall dependencies
  44. #### Individual Projects
  45. Common project scripts include:
  46. - `dev`: run in watch mode
  47. - `build`: run project/library build
  48. - `test`: run unit tests
  49. - `test:lighthouse`: run lighthouse performance tests
  50. - `test:visual`: run playwright visual regression tests
  51. - `test:axe`: run axe tests for a11y
  52. The available scripts vary by project. Check the project's `package.json` before running project-specific commands.
  53. For details about the repository build and runtime flow, see the [build system documentation](https://github.com/NVIDIA/elements/blob/main/projects/internals/BUILD.md).
  54. ## Workflow
  55. Before creating a branch or pull request, make a [new issue or feature request](https://github.com/NVIDIA/elements/issues/new) first so the team can check alignment and avoid duplicate work.
  56. ### Create a Branch
  57. Use a descriptive branch name with the `topic/` prefix. Example `topic/bug-fix`.
  58. ```shell
  59. git checkout -b topic/bug-fix
  60. ```
  61. After creating your branch, make your source code changes. After you complete them, run `mise exec -- pnpm run ci` in the root of the repo to run all the builds and tests. If all tests pass, you are ready to create a PR.
  62. ### Commit Messages
  63. The repo uses [Semantic Release](https://semantic-release.gitbook.io/semantic-release/) to manage package changes. Commit messages determine the release on merge. [Commit Lint](https://commitlint.js.org/) enforces commit formatting.
  64. ```shell
  65. git commit -a -s -m "fix(core): disable multi-select"
  66. ```
  67. [Example Commit](https://github.com/NVIDIA/elements/commit/990d8f43a4a055c2f1ca1a6aa0af39f099d04649)
  68. | Types | Description |
  69. | ------- | --------------------------------------------------------------- |
  70. | `fix` | bug fixes, performance fixes |
  71. | `feat` | new features, components, APIs |
  72. | `chore` | non production code modifications, build tooling, documentation |
  73. | Scopes | Description |
  74. | ----------- | ------------------------------ |
  75. | `ci` | CI and release automation |
  76. | `cli` | `/projects/cli` |
  77. | `code` | `/projects/code` |
  78. | `core` | `/projects/core` |
  79. | `create` | `/projects/create` |
  80. | `deps` | dependency updates |
  81. | `docs` | documentation and site content |
  82. | `forms` | `/projects/forms` |
  83. | `internals` | `/projects/internals` |
  84. | `lint` | `/projects/lint` |
  85. | `markdown` | `/projects/markdown` |
  86. | `media` | `/projects/media` |
  87. | `monaco` | `/projects/monaco` |
  88. | `pages` | `/projects/pages` |
  89. | `pi` | `/projects/pi` |
  90. | `starters` | `/projects/starters` |
  91. | `styles` | `/projects/styles` |
  92. | `themes` | `/projects/themes` |
  93. Keep commit names focused on your changes. The release process uses the commit message to determine the next release and generated changelog notes.
  94. ### Opening a Pull Request
  95. Once you have committed your changes to your branch locally, push them to the remote GitHub repository.
  96. ```bash
  97. git push --set-upstream origin topic/bug-fix
  98. ```
  99. Open a new [Pull Request](https://github.com/NVIDIA/elements/pulls) in GitHub. Request review from the team members and apply the appropriate labels in the GitHub UI, for example, `type:fix` and `scope(core)`.
  100. #### Amending Commit
  101. **If there are changes requested**, make the requested changes locally and amend the commit.
  102. ```shell
  103. git commit -a --amend --no-edit
  104. ```
  105. This adds the changes to your existing commit. Then push the updated commit back to the remote branch for review.
  106. ```shell
  107. git push --force origin topic/bug-fix
  108. ```
  109. #### Rebasing Commit
  110. If main changes before PR approval, rebase your local branch to include the latest changes from main.
  111. ```shell
  112. git checkout main # Switch to main branch
  113. git pull # Pull down any new changes
  114. git checkout topic/bug-fix # Switch back to your topic branch
  115. git rebase main # Rebase your branch onto the latest main
  116. ```
  117. You may have to resolve any merge conflicts that arise from this process. Once complete, push the updated branch back to the remote repository for review.
  118. ### New Project
  119. When creating a new project, ex: `./projects/code`, make sure to add the project to the `pnpm-workspace.yaml` located at the root directory.
  120. ### Release
  121. After approval, merge your Pull Request into `main` through the GitHub UI. GitHub Actions triggers a [new release](https://github.com/NVIDIA/elements/releases) automatically. Semantic Release calculates the version from the commit type. The [changelog](https://NVIDIA.github.io/elements/docs/changelog/) also includes the commits from the PR.

Ratings and comments

Sign in to rate this skill.

Sign in

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