In the November 2026 Edition, 241 of the 252 answers collected in the one category where GitLab Dependency Scanning holds a standing named it neither as a first choice nor as an alternative. These are the products those answers put first, category by category and buyer by buyer. The output is the models' output.
Eighty of the eighty-four answers did not name GitLab Dependency Scanning; it was the first choice in one. The first choices in those eighty answers, eleven products in all, the eight most named:
Seventy-seven of the eighty-four answers did not name GitLab Dependency Scanning; it was the first choice in zero. The first choices in those seventy-seven answers, ten products in all, the eight most named:
Eighty-four of the eighty-four answers did not name GitLab Dependency Scanning; it was the first choice in zero. The first choices in those eighty-four answers, thirteen products in all, the eight most named:
A category is asked six ways of each of fourteen models on behalf of each buyer segment, so a segment is eighty-four answers. An answer belongs on this page when the judge labeled GitLab Dependency Scanning neither its first choice nor an alternative in it; the products listed are the first choices those answers made, counted once per answer. An answer that named nothing first, or named GitLab Dependency Scanning only in passing, is in the denominator and adds to no product. The counts are not the category standing, which is on the category page with its share and rank; they are the same record read from GitLab Dependency Scanning's side.
The output is the models' output; nothing here is a recommendation by the index, and a product named instead of GitLab Dependency Scanning was named by a model, not endorsed by anyone.