Technology Categories: Grouping a Stack by What Each Part Does

## Why it matters

A page might detect forty technologies. Without grouping, that's noise. With categories, it becomes a map: there's the CMS, the analytics stack, the CDN, the frameworks, the e-commerce platform. When you jump to "Analytics" you skip past the infrastructure and see what's tracking. When you look at "Frameworks" you see the programming model without wading through third-party embeds.

Categories also give you scanning speed. You don't need to know every technology on every site. You need to know the role each plays. A site might use three different testing frameworks bundled inside dev dependencies (you don't care), but Playwright in production would matter (you do care). Categories help you separate the signal from the noise based on what you're actually looking for.

Because the categories come from the open fingerprint database, they mean the same thing across all the Scalpel tools. A CDN on one site is a CDN on another.

## How it works

Every technology in the fingerprint database belongs to one or more categories. WordPress is a "CMS". jQuery is a "JavaScript framework". Cloudflare is a "CDN". Google Analytics is "Analytics". The categories are predefined in the database, and every match gets tagged with the categories its technology belongs to.

Scalpel Stack orders categories by priority. On most sites you'll see CMS first (if there is one), then frameworks, then analytics, then CDN, then tag managers, then everything else. That order surfaces the most important infrastructure first and lets you scan faster.

A single technology can span multiple categories. WooCommerce is both "CMS" and "E-commerce". A JavaScript framework might be both "JavaScript" and "Web framework". When you expand the category in the popup, you see all technologies in that category, regardless of how many categories they belong to.

## What does not matter

The category taxonomy is fixed by the fingerprint database. You can't add custom categories or reorder them (the priority is global, not per-user). Also, a missing category doesn't mean the database is incomplete; many niche technologies are classified and detected but belong to a low-priority category that only appears after the major ones.

The categories are also not exhaustive. A technology might do several things, but the database labels it with its primary role. That's intentional: a CDN might offer DDoS protection and edge compute, but "CDN" is the core function you need to know.

## Code example

Here's what a site's detected technologies look like when grouped by category:

{
  "categories": [
    {
      "category": "CMS",
      "count": 1,
      "technologies": [
        {
          "name": "WordPress",
          "version": "6.4.2",
          "confidence": 100
        }
      ]
    },
    {
      "category": "JavaScript Frameworks",
      "count": 1,
      "technologies": [
        {
          "name": "jQuery",
          "version": "3.6.0",
          "confidence": 95
        }
      ]
    },
    {
      "category": "Analytics",
      "count": 2,
      "technologies": [
        {
          "name": "Google Analytics",
          "confidence": 98
        },
        {
          "name": "Mixpanel",
          "confidence": 87
        }
      ]
    },
    {
      "category": "CDN",
      "count": 1,
      "technologies": [
        {
          "name": "Cloudflare",
          "confidence": 100
        }
      ]
    }
  ]
}
Copy

The popup groups the rows this way, with category headers and the technologies underneath, ordered by the database's priority.

## How Scalpel shows it

The Scalpel Stack popup groups detected technologies under category headers. Each header shows the category name, an icon, and the count of technologies in that category. The technologies are listed in order under each header. Expanding a category header shows the full details of each technology, including version and evidence.

The category headers carry the ? for this concept's glossary entry, so a reader can jump to this page to understand what "CMS" or "Analytics" means in the context of the site they're auditing.