Isaac ROS 4.0 (#218)

Author: jaiveersinghNV

README.md

@@ -1,23 +1,13 @@
 # Isaac ROS Common
 
-Dockerfiles and scripts for development using the Isaac ROS suite.
+Essential utilities, packages, scripts, and testing infrastructure for Isaac ROS packages.
 
 ## Overview
 
 The Isaac ROS Common
-repository contains a number of scripts and Dockerfiles to help
-streamline development and testing with the Isaac ROS suite.
+repository contains an array of essential packages for building, testing, and using Isaac ROS.
 
-<div align="center"><a class="reference internal image-reference" href="https://media.githubusercontent.com/media/NVIDIA-ISAAC-ROS/.github/main/resources/isaac_ros_docs/repositories_and_packages/isaac_ros_common/isaac_ros_common_tools.png/"><img alt="Isaac ROS DevOps tools" src="https://media.githubusercontent.com/media/NVIDIA-ISAAC-ROS/.github/main/resources/isaac_ros_docs/repositories_and_packages/isaac_ros_common/isaac_ros_common_tools.png/" width="auto"/></a></div>
-
-Docker containers allow you to quickly set up a sensitive set of frameworks
-and dependencies to ensure a smooth experience with Isaac ROS packages.
-The Dockerfiles for x86_64 are based on the version 23.10 image from [Deep Learning
-Frameworks Containers](https://docs.nvidia.com/deeplearning/frameworks/support-matrix/index.html).
-On Jetson platforms, JetPack manages all of these dependencies for you.
-
-Use of Docker images enables CI|CD systems to scale with DevOps work and
-run automated testing in cloud native platforms on Kubernetes.
+<div align="center"><a class="reference internal image-reference" href="https://media.githubusercontent.com/media/NVIDIA-ISAAC-ROS/.github/release-4.0/resources/isaac_ros_docs/repositories_and_packages/isaac_ros_common/isaac_ros_common_tools.png/"><img alt="Isaac ROS DevOps tools" src="https://media.githubusercontent.com/media/NVIDIA-ISAAC-ROS/.github/release-4.0/resources/isaac_ros_docs/repositories_and_packages/isaac_ros_common/isaac_ros_common_tools.png/" width="auto"/></a></div>
 
 For solutions to known issues, see the [Troubleshooting](https://nvidia-isaac-ros.github.io/troubleshooting/index.html) section.
 
@@ -31,4 +21,4 @@ Please visit the [Isaac ROS Documentation](https://nvidia-isaac-ros.github.io/re
 
 ## Latest
 
-Update 2024-12-10: Refactored Dockerfiles
+Update 2025-10-24: Support for ROS 2 Jazzy, moved Docker dev container functionality to Isaac ROS CLI

SECURITY.md

@@ -0,0 +1,24 @@
+## Security
+
+NVIDIA is dedicated to the security and trust of our software products and services, including all source code repositories managed through our organization.
+
+If you need to report a security issue, please use the appropriate contact points outlined below. **Please do not report security vulnerabilities through GitHub.**
+
+## Reporting Potential Security Vulnerability in an NVIDIA Product
+
+To report a potential security vulnerability in any NVIDIA product:
+- Web: [Security Vulnerability Submission Form](https://www.nvidia.com/object/submit-security-vulnerability.html)
+- E-Mail: psirt@nvidia.com
+    - We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key)
+    - Please include the following information:
+      - Product/Driver name and version/branch that contains the vulnerability
+      - Type of vulnerability (code execution, denial of service, buffer overflow, etc.)
+      - Instructions to reproduce the vulnerability
+      - Proof-of-concept or exploit code
+      - Potential impact of the vulnerability, including how an attacker could exploit the vulnerability
+
+While NVIDIA currently does not have a bug bounty program, we do offer acknowledgement when an externally reported security issue is addressed under our coordinated vulnerability disclosure policy. Please visit our [Product Security Incident Response Team (PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) policies page for more information.
+
+## NVIDIA Product Security
+
+For all security-related concerns, please visit NVIDIA's Product Security portal at https://www.nvidia.com/en-us/security