Skip to content
RobothecaBeta

ROS 1

  • Software
  • Middleware
  • Framework

The ros_comm repository holds the core communication packages of ROS 1, which is now archived because ROS 1 has reached end of life.

  • Licensed per package
  • Discontinued
  • Moved

Source on GitHub: github.com/ros/ros_comm (opens in a new tab). Facts read at commit 30483a9 (opens in a new tab).

Licenses

Code
Licensed per package

No license at the repository's root: each package carries its own. Read the license of each package you use.

No license file at the repository's root at commit 30483a9 (opens in a new tab), on 16 Oct 2026.

Commercial use
Yes

No single license: each ROS 1 package declares its own. The core packages read (roscpp, rospy, rosmaster) are BSD-3-Clause, which allows commercial use.

Labels

  • Licensed per packageNo license at the repository's root: each of its packages carries its own license.
  • DiscontinuedEnded on 31 May 2025: Noetic, the last ROS 1 release, reached its end of life on 2025-05-31: no more updates, bug fixes or security fixes from the ROS team. Its packages stay downloadable.
  • MovedMoved to ROS 2.

What it does: Robotheca's summary

  • Repository contains ROS 1 packages.
  • The last supported ROS 1 release, ROS Noetic, reached end of life on May 31st, 2025.
  • The repository is archived and no longer actively maintained.

Written by Robotheca from the project's README (opens in a new tab) at commit 30483a9.

Getting started

Difficulty
Intermediate

Maintenance

Status
Discontinued: its makers have ended it
Newest commit
31 May 2025 on noetic-devel
Latest release
None published on GitHub
Archived
The repository is archived on GitHub (read-only).
Discontinued
Ended on 31 May 2025: Noetic, the last ROS 1 release, reached its end of life on 2025-05-31: no more updates, bug fixes or security fixes from the ROS team. Its packages stay downloadable. Source: discourse.openrobotics.org/t/ros-noetic-end-of-life-may-31-… (opens in a new tab)
Moved
Its successor or new home: ROS 2.

Checked on GitHub on 31 Oct 2026.

Links

Robots that can run it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.