Locations

See the AI in every scanned repository: coding assistants, MCP servers, models, AI packages, AI services, agent skills and AI provider keys

Container Image locations model the image a finding was found in, identified by registry, repository and digest, and the assets that run it

Domain, IP address and certificate locations describe an organization's internet-facing attack surface: the DNS names, addresses and TLS certificates that parsers and connectors report

Export an Asset's AI inventory as a CycloneDX 1.6 AI bill of materials, with evidence and authorization decisions

Export an Asset's dependency inventory as CycloneDX or SPDX, and its finding statuses as a CycloneDX or OpenVEX VEX document

Test what you know about Locations with 19 multiple-choice questions

See every Location an Asset has on one map, grouped by what the Locations share, with active finding counts on every node

What Locations are and why they replace Endpoints

What happens when you migrate existing Endpoint data to Locations

Code locations model where a static-analysis finding lives in source, and record its movement history as code evolves

Manage software dependencies and SBOMs as Locations

Day-to-day use of URL Locations as the Endpoints replacement