GitLab Orbit is a graph-based tool for quickly determining the reach of a vulnerability across an organization’s software development environment. Security scanners can identify affected components, but teams often still have to manually connect findings to projects, services, deployment pipelines, environments, and owners. Orbit combines GitLab data - including code, merge requests, pipelines, work items, and security findings - so users or AI agents can ask in plain language which projects are affected and who is responsible. Its central argument is that organizations need this map ready before a security disclosure, because attackers can exploit flaws faster than teams can assemble an exposure list from separate tools.
The PHP2Shell vulnerabilities illustrate the challenge: PHP may appear in application dependencies, operating-system packages, container images, old CI jobs, or manually managed servers. Orbit can help map repository-declared use and related ownership, while code searches and vulnerability reports help confirm images, versions, and open findings. Teams must still compare repository results with runtime inventories, since systems outside GitLab repositories may be missed. GitLab reports that, in tests using the same model and tasks, agents using Orbit were up to 11 times faster, used up to 4.5 times fewer tokens, and needed up to 45 times fewer retries. Role-based permissions govern access, and built-in and external agents can query the graph. Orbit is generally available to Premium and Ultimate customers on GitLab.com, with Self-Managed and Dedicated availability planned in the coming weeks.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.