Most net stars, last 30 days
mozihe/z-localizationTranslated2026 Northeastern University T-DT Lab RoboMaster Robotics Competition (RoboMaster University Championship) Sentry Localization Open Source
+123
21% of the net stars of this Tag
Tags / Hardware and IoT /
Package, node, or tool for the Robot Operating System, ROS or ROS 2.
The 106repositories with this Tag gained +588 net stars in the last 30 days, 47% more than the 30 days before.
1 created in the last 90 days · 4 published a release in the last 30 days · 92K stars in total
Oct 6, 2026Nov 4, 2026
Most net stars, last 30 days
mozihe/z-localizationTranslated2026 Northeastern University T-DT Lab RoboMaster Robotics Competition (RoboMaster University Championship) Sentry Localization Open Source
+123
21% of the net stars of this Tag
Largest Pace, last 30 days
No other repository gained 2 or more times the net stars of the 30 days before.
Most stars, created in the last 90 days
No other repository with this Tag was created in the last 90 days.
Net stars gained each week. The repositories that gained the most have their own color.
mozihe/z-localization gained 8% of the net stars of this Tag in the last 13 weeks. It was created on Oct 22, 2026.
31 of 106 repositories: The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list. Select a column name to change the order.
| # | Repository | Stars | Gained, 30 days | Pace | |
|---|---|---|---|---|---|
| 1 | ANYbotics/grid_map Universal grid map library for mobile robotic mapping | 3.3K | +22 | – | |
| 2 | leggedrobotics/darknet_ros YOLO ROS: Real-Time Object Detection for ROS | 2.4K | +2 | – | |
| 3 | moveit/moveit :robot: The MoveIt motion planning framework | 2.1K | +3 | – | |
| 4 | cra-ros-pkg/robot_localization robot_localization is a package of nonlinear state estimation nodes. The package was developed by Charles River Analytics, Inc. Please ask questions on answers.ros.org. | 2K | +21 | – | |
| 5 | cartographer-project/cartographer_ros Provides ROS integration for Cartographer. | 1.9K | +2 | – | |
| 6 | ankitdhall/lidar_camera_calibration ROS package to find a rigid-body transformation between a LiDAR and a camera for "LiDAR-Camera Calibration using 3D-3D Point correspondences" | 1.8K | +6 | – | |
| 7 | rst-tu-dortmund/teb_local_planner An optimal trajectory planner considering distinctive topologies for mobile robots based on Timed-Elastic-Bands (ROS Package) | 1.4K | +14 | – | |
| 8 | PRBonn/depth_clustering :taxi: Fast and robust clustering of point clouds generated with a Velodyne sensor. | 1.3K | +7 | – | |
| 9 | uzh-rpg/rpg_trajectory_evaluation Toolbox for quantitative trajectory evaluation of VO/VIO | 1.2K | +3 | – | |
| 10 | IFL-CAMP/easy_handeye Automated, hardware-independent Hand-Eye Calibration | 1.2K | +9 | – | |
| 11 | ros-perception/image_pipeline An image processing pipeline for ROS. | 973 | +7 | – | |
| 12 | praveen-palanisamy/multiple-object-tracking-lidar C++ implementation to Detect, track and classify multiple objects using LIDAR scans or point cloud | 910 | +2 | – | |
| 13 | carlosmccosta/dynamic_robot_localization Point cloud registration pipeline for robot localization and 3D perception | 903 | +3 | – | |
| 14 | MapIV/eagleye Precise localization based on GNSS and IMU. | 776 | +2 | – | |
| 15 | CopterExpress/clover ROS-based framework and RPi image to control PX4-powered drones 🍀 | 694 | +5 | – | |
| 16 | nobleo/rviz_satellite Display internet satellite imagery in RViz | 666 | 0 | – | |
| 17 | carla-simulator/ros-bridge ROS bridge for CARLA Simulator | 646 | +1 | – | |
| 18 | RoboStack/jupyter-ros Jupyter widget helpers for ROS, the Robot Operating System | 614 | 0 | – | |
| 19 | at-wat/mcl_3dl A ROS node to perform a probabilistic 3-D/6-DOF localization system for mobile robots with 3-D LIDAR(s). It implements pointcloud based Monte Carlo localization that uses a reference pointcloud as a map. | 604 | +3 | – | |
| 20 | srl-freiburg/pedsim_ros Pedestrian simulator powered by the social force model | 593 | +3 | – |
Net stars of the last 30 days are 2 or more times those of the 30 days before.
No repository with this Tag meets this rule now.
Net stars of the last 30 days are 50% or less of those of the 30 days before.
No repository with this Tag meets this rule now.
Created on GitHub in the last 90 days.
Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.
The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.
All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.
For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.
The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.
The chart at the top adds up the net stars of all the repositories with the Tag. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time.
The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.