# Tech Stack & Vendor Risk Scanner (`zaden/tech-stack-vendor-risk-scanner`) Actor

Scan any website's technology stack -- CMS, ecommerce platform, JS framework, analytics, CDN, payments, chat widget -- and get a letter grade, severity tag, and plain-English risk/opportunity flags. No headless browser, fast parallel scanning.

- **URL**: https://apify.com/zaden/tech-stack-vendor-risk-scanner.md
- **Developed by:** [Zaden](https://apify.com/zaden) (community)
- **Categories:** Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 site scanneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Tech Stack & Vendor Risk Scanner

A fast, no-browser scan of the technology stack behind any website -- CMS, ecommerce platform, JS framework, analytics, tag manager, CDN, hosting, payments, and chat/support widget -- plus a letter grade, a severity tag, and a plain-English list of legacy/security and opportunity flags.

### What you get, per URL

- A **letter grade (A to F)** and 0-100 score summarizing stack health at a glance
- A one-line **executive summary**
- A **severity tag** -- `critical` (mixed content or unreachable), `warning` (legacy jQuery, exposed version string), or \`ok
- The full **technology list**, each tagged with its category (CMS, Analytics, CDN, Payments, Chat, etc.)
- A **generator meta tag** value when present (often reveals exact CMS version)
- **Risk and opportunity flags**: legacy jQuery 1.x, mixed HTTP content on an HTTPS page, exposed version strings, missing CDN, missing analytics
- Sites are checked **in parallel** (configurable), so a batch of 50 domains finishes in a fraction of the time a one-by-one lookup would take

### Why this instead of checking manually

| | Manual "view source" spot-check | Tech Stack & Vendor Risk Scanner |
|---|---|---|
| Coverage | Whatever page you remember to check | Every URL you list, automatically |
| Speed | View-source, scroll, repeat per page | Seconds, via parallel scanning |
| Triage | You read raw HTML/headers yourself | Pre-classified severity + letter grade |
| Output | Notes in a doc | Structured dataset, exportable to CSV/JSON/BI tools |

### Who this is for

- **Sales and SDR teams** qualifying leads by what platform a prospect runs (e.g. "still on WordPress with no CDN")
- **Agencies** doing a quick technical audit before a pitch
- **Security-minded developers** checking for legacy jQuery or exposed CMS version strings across a portfolio of sites
- **Competitive researchers** mapping what stack a set of competitors use

### How to use it

1. Add one or more URLs to scan.
2. Optionally enable "Fetch linked CSS files" to catch CSS-framework signatures (Bootstrap, Tailwind) at a small speed cost.
3. Run it once for a snapshot, or schedule it to catch a stack change (a competitor switching CMS or adding a new chat widget) over time.

### Example output (one item)

```json
{
  "url": "https://example.com/",
  "finalUrl": "https://example.com/",
  "statusCode": 200,
  "responseTimeMs": 210,
  "grade": "B+",
  "score": 90,
  "severity": "warning",
  "summary": "1 item(s) worth a look -- 6 technologies detected.",
  "technologyCount": 6,
  "technologies": [
    { "name": "WordPress", "category": "CMS", "legacy": false },
    { "name": "jQuery (legacy 1.x)", "category": "JS Library", "legacy": true },
    { "name": "Google Analytics (GA4)", "category": "Analytics", "legacy": false },
    { "name": "Cloudflare", "category": "CDN", "legacy": false }
  ],
  "issues": [
    { "severity": "warning", "message": "Legacy jQuery 1.x detected -- unsupported since 2016." }
  ],
  "generator": "WordPress 6.2",
  "checkedAt": "2026-08-25T00:00:00.000Z"
}
```

### Pricing

This Actor uses pay-per-event pricing:

- **Site scanned** -- charged once per URL successfully scanned.

Failed lookups (unreachable domains, timeouts) are not charged.

### FAQ

**Does this render JavaScript?** No. It reads the raw HTML response and HTTP headers, the same way most crawlers see a page. Technologies that are injected purely client-side after heavy JS execution may not be visible.

**How many technologies can it detect?** The current signature set covers 60+ common CMS, ecommerce, framework, analytics, CDN, hosting, payment, and chat vendors, chosen for accuracy over sheer signature count.

**Is this a security scanner?** No. It flags a small set of well-understood legacy/exposure signals (old jQuery, exposed version strings, mixed content) as a bonus, but it is not a vulnerability scanner and doesn't replace one.

**Does this send data anywhere besides your own Apify account?** No. It only fetches the URLs you provide (and, optionally, up to 2 linked stylesheets per page) and returns what it finds.

# Actor input Schema

## `urls` (type: `array`):

One or more site URLs to detect the technology stack for.

## `concurrency` (type: `integer`):

How many URLs to check in parallel.

## `checkSubresources` (type: `boolean`):

When enabled, also fetches up to 2 linked stylesheets per page to catch CSS-framework signatures (Bootstrap, Tailwind). Slightly slower.

## Actor input object example

```json
{
  "urls": [
    "https://example.com"
  ],
  "concurrency": 10,
  "checkSubresources": false
}
```

# Actor output Schema

## `results` (type: `string`):

One row per URL: detected technologies, letter grade, severity, and risk flags.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zaden/tech-stack-vendor-risk-scanner").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("zaden/tech-stack-vendor-risk-scanner").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example.com"
  ]
}' |
apify call zaden/tech-stack-vendor-risk-scanner --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zaden/tech-stack-vendor-risk-scanner"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/kGdAyC9iRqkpdiJEw/builds/qEubuyQMfzmPmwqkn/openapi.json