-You can find the list of IP addresses that Patchstack uses at patchstack.com/ips-v4.
-
\ No newline at end of file
diff --git a/src/content/docs/API solutions/App API/patchstack-app-api.md b/src/content/docs/API solutions/App API/patchstack-app-api.md
index 834af31f..e138c15f 100644
--- a/src/content/docs/API solutions/App API/patchstack-app-api.md
+++ b/src/content/docs/API solutions/App API/patchstack-app-api.md
@@ -11,13 +11,17 @@ _Patchstack App API is available for the Developer and Enterprise plan users_
Patchstack App API enables users to run all the Patchstack App account actions remotely over an API. It allows you to access protection logs, generate security reports, manage site settings, add new sites, create custom rules, and much more.
+:::note[What the App API does not manage]
+The App API manages **sites and their security** on your Patchstack account — provisioning, plugin connection, protection, reporting and site settings. It does **not** manage trials, subscriptions, plan changes or billing for your own end customers. If you are reselling Patchstack (for example through WHMCS), run trials, subscriptions and invoicing in your own billing system and use the App API purely to provision and manage the underlying sites. Your Patchstack account's own subscription is handled separately in the Patchstack app UI.
+:::
+
### Documentation and endpoints
Find all the Patchstack App API endpoints with examples from the documentation here:
https://api.patchstack.com/app-api/documentation
### Example use cases
Some example use cases for Patchstack App API are listed below:
-- Integrate Patchstack to your email marketing software to send out monthly security reports to your customers.
+- Integrate Patchstack to your email marketing software to send out monthly security reports to your customers. See [Generating and downloading reports](/api-solutions/app-api/patchstack-reports-api/).
- Integrate Patchstack inside your own product and let your customers enable (and control) Patchstack directly from your platform without them leaving your service.
- Pull IP addresses of attackers that try to exploit vulnerabilities into your DNS firewall to block them on the network layer.
- Integrate with Enterprise SIEM/SOC tools and pull vulnerability data and logs directly into it.
diff --git a/src/content/docs/API solutions/App API/patchstack-integration.md b/src/content/docs/API solutions/App API/patchstack-integration.md
index bb190272..3011520b 100644
--- a/src/content/docs/API solutions/App API/patchstack-integration.md
+++ b/src/content/docs/API solutions/App API/patchstack-integration.md
@@ -44,6 +44,20 @@ To minimize API calls and reduce latency when displaying site information to you
All Patchstack API endpoints return standard HTTP status codes. Your integration should handle these appropriately to ensure reliability and provide meaningful feedback to users. E.g. handle status codes 200, 401, 422, 500.
+Failed rechecks and resyncs include a `reason`. See [Why did a recheck or resync fail?](#why-did-a-recheck-or-resync-fail)
+
+#### Rate limits & quotas
+| Endpoint | Limit |
+| --- | --- |
+| POST /site/add POST /site/exists | 100 URLs per call in `urls`. Split larger batches across several calls. |
+| POST /sites/list | 20 sites per page by default. Page through with `page` and `per_page`. |
+| POST /sites/list/basic | All sites in one response by default. Page through with `after_id` and `per_page` (default 100, max 1000). |
+| POST /site/plugin/resync/{siteid} | For many sites, use POST /site/plugin/bulk-resync. |
+
+:::note[Rate limits]
+Some App API endpoints are rate limited. If you receive `429 Too Many Requests`, wait a minute and retry. At scale, use the batch and paging options in the table above — for example, pass multiple URLs in the `urls` array on `/site/add` (and `/site/exists`) instead of looping a separate request per site.
+:::
+
## Flow of integration & plugin
Patchstack works by assigning an API key to a site that has been added to the Patchstack App. This API key is then used in the WordPress plugin to activate the connection to Patchstack.
@@ -73,6 +87,10 @@ It's also important to set the `Content-Type` HTTP header to `application/json`
### Step 2: Site provisioning
When the site should be added to Patchstack depends on your use-case scenario. If they require protection immediately then you can execute this flow the moment the website environment (the WordPress site) has been created on the infrastructure. If you upsell Patchstack then this flow can be launched upon purchase or opt-in.
+:::tip[Using WHMCS?]
+If you provision Patchstack through WHMCS, the Patchstack WHMCS module handles this flow for you. See the [WHMCS setup guide](/partners/whmcs-setup/).
+:::
+
###### 1. Determine if the site already exists in Patchstack
This step is essential as it's possible that a site may be protected already or added to Patchstack. For this, the `/site/exists` API endpoint can be utilized; it will check if a site with the given URL has already been added to Patchstack before you attempt to actually add the site to Patchstack.
@@ -119,18 +137,110 @@ The response will look something like below.
{
"success": "Successfully added the site(s).",
"count": 1,
+ "sites": {
+ "https://mywebsite.com": {
+ "siteid": 12345,
+ "oauth": {
+ "id": 12333,
+ "secret": "DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR",
+ "apikey": "DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR-12333"
+ }
+ }
+ },
"lastid": 12345,
"oauth": {
- "id": 12345,
- "secret": "DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR"
+ "id": 12333,
+ "secret": "DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR",
+ "apikey": "DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR-12333"
}
}
```
+The top-level `lastid` and `oauth` fields refer to the **last** site in the batch and are kept for backwards compatibility. New integrations should read from the per-URL `sites` map.
+
+###### Bulk provisioning
+The `urls` parameter is an **array**, so you can provision up to **100 sites in a single `/site/add` call** rather than looping one request per site. Pass every URL in the array and the response returns one entry per added URL under the `sites` map, keyed by the exact URL you sent (URLs already on the account are skipped, see below):
+
+```bash
+curl -X 'POST' \
+ 'https://api.patchstack.com/monitor/site/add' \
+ -H 'UserToken: ' \
+ -H 'Content-Type: application/json' \
+ -d '{
+ "urls": [
+ "https://site1.com",
+ "https://site2.com"
+ ],
+ "cms_id": 1
+}'
+```
+
+```json
+{
+ "success": "Successfully added the site(s).",
+ "count": 2,
+ "sites": {
+ "https://site1.com": {
+ "siteid": 12345,
+ "oauth": { "id": 12333, "secret": "…", "apikey": "…-12333" }
+ },
+ "https://site2.com": {
+ "siteid": 12346,
+ "oauth": { "id": 12334, "secret": "…", "apikey": "…-12334" }
+ }
+ },
+ "lastid": 12346,
+ "oauth": { "id": 12334, "secret": "…", "apikey": "…-12334" }
+}
+```
+
+Reconcile the results **by URL**: iterate the `sites` map and match each key back to the record on your side, rather than relying on array order or the top-level `lastid`. The `/site/exists` endpoint accepts the same `urls` array (up to 100) so you can pre-check a whole batch in one call before adding it. If you need to re-fetch the `{siteid, url}` mapping for every site on the account later, call [`POST /monitor/sites/list/basic`](https://api.patchstack.com/app-api/documentation) and match by URL.
+
+###### Sites that are already on the account
+`/site/add` never adds a site twice. A URL that is already on your account (or your team's) is skipped: it is not created again and it is not charged for again. The same goes for a URL that appears twice in one request. This makes it safe to resend a batch, for example after a timeout.
+
+When matching, `http` and `https`, a `www.` prefix, upper and lower case, and a trailing slash are ignored. A different port or path counts as a different site, so `https://mywebsite.com/shop` can still be added next to `https://mywebsite.com`.
+
+Skipped URLs are listed in `skipped` and do not appear in `sites`:
+
+```json
+{
+ "success": "Successfully added the site(s).",
+ "count": 1,
+ "sites": {
+ "https://site2.com": {
+ "siteid": 12346,
+ "oauth": { "id": 12334, "secret": "…", "apikey": "…-12334" }
+ }
+ },
+ "skipped": ["https://site1.com"],
+ "lastid": 12346,
+ "oauth": { "id": 12334, "secret": "…", "apikey": "…-12334" }
+}
+```
+
+If every URL in the request is already on the account, nothing is added and the call returns HTTP `422`:
+
+```json
+{
+ "error": "The site(s) you entered are already on your account.",
+ "skipped": ["https://site1.com", "https://site2.com"]
+}
+```
+
+To get the `siteid` of a skipped site, call [`POST /monitor/sites/list/basic`](https://api.patchstack.com/app-api/documentation) and match by URL.
+
###### 3. Store in local datastore
-It is now important to store the lastid and oauth properties into a datastore on your infrastructure. This allows you to know the site identifier of the website of the customer without having to query the Patchstack App API each time. This can then be used for most of our other API endpoints to fetch information for the site.
+Store the `siteid` and `apikey` for each URL in a datastore on your infrastructure. This avoids having to query the Patchstack App API each time you need to identify a customer's site.
+
+- **`siteid`** is the canonical Patchstack site identifier. It is what the portal displays and what every per-site API endpoint expects in the URL (`/site/view/{siteid}`, `/site/delete/{siteid}`, `/download/wordpress/{siteid}`, etc.). Store this if you ever need to cross-reference your records against the Patchstack portal.
+- **`apikey`** is the pre-formatted plugin license key (`-`). Pass it directly to the WordPress plugin during activation — you do not need to assemble it yourself.
-The API key that is used in the plugin, contains the format `oauth.secret-oauth.id`, for example in above response it would be `DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR-12345`.
+:::note[`siteid` and `oauth.id` are independent fields]
+`siteid` identifies the site, `oauth.id` identifies the OAuth credential embedded in the plugin license key. They have always been independent fields with different purposes. Do not assume they are equal — for sites provisioned before 13 May 2026 the two values often coincided as a side-effect of how rows were inserted, but they may differ for any site provisioned since.
+
+If you previously stored `oauth.id` under the assumption it equalled the site identifier, call [`POST /monitor/sites/list/basic`](https://api.patchstack.com/app-api/documentation) to fetch `[{id, url}, …]` for every site on your account, match by URL, and update your stored values to the current `siteid`.
+:::
### Step 3: Plugin deployment
Now that you have the site identifier and plugin API key stored in your local datastore, you can start the flow of installing and activating the Patchstack plugin on the website.
@@ -153,9 +263,9 @@ First we execute the command below to install and activate the Patchstack plugin
`wp plugin install patchstack --activate`
-Then we execute the command below to activate the connection to Patchstack. It is important to inject the plugin API key here we retrieved from step 2:
+Then we execute the command below to activate the connection to Patchstack. It is important to inject the plugin API key (`apikey` from step 2) here:
-`wp patchstack activate DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR-12345`
+`wp patchstack activate DOOs9DIyv2FMcURFtkB0eXOHMRhH7I2EsaNUb4aR-12333`
This command will return `The Patchstack plugin has been successfully connected.` if it succeeded.
@@ -223,6 +333,37 @@ Simply plug it in your own environment and give customers deeper insights into t
[Click here for integration and more information](/api-solutions/app-api/patchstack-iframe/)
+## Site lifecycle: removing & re-adding sites
+
+###### Removing a site
+To remove a site from the account — for example when a customer cancels or you clean up a never-activated site — call the delete endpoint with the `siteid` you stored in step 2. The path is `/site/delete/{siteid}` and it accepts both `DELETE` and `POST`.
+
+```bash
+curl -X 'DELETE' \
+ 'https://api.patchstack.com/monitor/site/delete/12345' \
+ -H 'UserToken: ' \
+ -H 'Content-Type: application/json'
+```
+
+```json
+{
+ "success": "Successfully deleted the site."
+}
+```
+
+To also uninstall the Patchstack plugin from the remote WordPress site as part of the deletion, send `{"delete": true}` in the request body. To remove several sites at once, call `DELETE /site/delete` with a body of `{"sites": [12345, 12346]}`.
+
+:::caution[Plugin removal on site deletion]
+Deleting a site with the `delete` flag also attempts to remove the Patchstack plugin from the connected WordPress site. This remote removal is best-effort and may not complete if the site connection is unstable, or if the plugin has already been deactivated or disconnected (but not deleted). For reliable removal, manage the plugin directly on the site with WP-CLI (for example `wp plugin delete patchstack`) rather than relying on the remote deletion.
+:::
+
+:::caution[Deleting a site is destructive and permanent]
+There is **no paused or suspended state** in Patchstack. Deleting a site removes it and its data, and it stops counting toward your plan. If you later re-add the same URL with `/site/add`, Patchstack provisions a **brand-new site** with **new `siteid` and new OAuth credentials** (a new plugin `apikey`) — the previous credentials are not restored. Any integration that "suspends" and "resumes" a site must therefore delete on suspend and re-provision + re-activate the plugin on resume, then overwrite the stored `siteid`/`apikey` with the new values.
+:::
+
+###### Cleaning up never-activated sites
+A site that was provisioned but whose plugin never connected will report `{"activated": false}` from [`GET /site/plugin/installed/{siteid}`](https://api.patchstack.com/app-api/documentation#/Sites/d932033c445ab06e5fd2dcb6ea8eead3). Combine that check with the delete endpoint above to periodically prune sites that were added but never came online. See the [FAQ](#how-to-determine-if-a-site-has-been-activated-and-is-connected) for the difference between the `plugin/installed` and `state` checks.
+
## Noteworthy API endpoints
The list below are noteworthy API endpoints that might be interesting to our partners.
@@ -285,4 +426,85 @@ Which outputs the following:
{
"activated": true
}
-```
\ No newline at end of file
+```
+
+### Why did a recheck or resync fail?
+On failure, [`POST /site/plugin/recheck/{siteid}`](https://api.patchstack.com/app-api/documentation) and [`POST /site/plugin/resync/{siteid}`](https://api.patchstack.com/app-api/documentation) return `422` with a `reason` code next to `error`.
+
+```json
+{
+ "error": "We could not force a resync of the site (ERR 1).",
+ "reason": "plugin_rejected_request"
+}
+```
+
+###### plugin_rejected_request
+- Plugin not active. Check with `wp plugin list`.
+- Plugin holds another site's API key, e.g. after cloning. Run `wp patchstack activate `.
+- `AUTH_KEY` salts changed, so the stored key can't be read. Run `wp patchstack activate `.
+- Stale object cache. Run `wp cache flush`.
+- Server clock more than 10 minutes off. Sync it.
+
+###### blocked_by_firewall
+- A WAF, bot protection, CDN challenge, HTTP auth or maintenance page answered instead of WordPress. Allow `POST /wp-admin/admin-ajax.php` from our [IPv4](https://patchstack.com/ips-v4/) and [IPv6](https://patchstack.com/ips-v6/) ranges, or for the `User-Agent` ending in `Patchstack/1.0 (+https://patchstack.com)`.
+
+###### plugin_endpoint_not_found
+- Site URL doesn't match the WordPress address, e.g. after a domain change or for a subdirectory install.
+- A security plugin hides `admin-ajax.php`.
+
+###### site_error
+- `5xx` from the site. Check its error log.
+
+###### site_unreachable
+- Site down or timing out.
+- Domain doesn't resolve.
+- Invalid TLS certificate.
+
+###### unexpected_response
+- Extra output on `admin-ajax.php`, e.g. from another plugin.
+- Outdated plugin. Update it.
+- Contact support if it persists.
+
+###### site_not_connected
+- No API key on our side. [Remove and re-add the site](#site-lifecycle-removing--re-adding-sites), then activate with the new `apikey`.
+
+### What's the difference between `siteid` and `oauth.id`? Can I assume they're equal?
+They are two independent fields with different purposes — do not assume they are equal.
+
+- **`siteid`** is the canonical Patchstack site identifier. It is what the portal displays and what every per-site API endpoint expects (e.g. `/site/view/{siteid}`, `/site/delete/{siteid}`, `/download/wordpress/{siteid}`). Store this for cross-referencing your records against the Patchstack portal.
+- **`oauth.id`** is the OAuth credential identifier. Its only purpose is to form the plugin license key, which the `/site/add` response already returns pre-formatted as `apikey` (`-`). You never need to read `oauth.id` as a standalone value — just pass `apikey` to the plugin.
+
+For sites provisioned before 13 May 2026, `siteid` and `oauth.id` coincidentally held the same value because of how rows were inserted in our database. They may differ for any site provisioned since. If you previously stored `oauth.id` under the assumption it equalled the site identifier, see the [callout in step 2 of integration](#3-store-in-local-datastore) for how to reconcile your stored values.
+
+### How can I reconcile site IDs in my datastore against the Patchstack portal?
+Call [`POST /monitor/sites/list/basic`](https://api.patchstack.com/app-api/documentation) with the same `UserToken` you use for `/site/add`. It returns `[{id, url}, …]` for every site on your account, where `id` is the current `siteid`. Match by URL and update your stored values.
+
+```bash
+curl -X 'POST' \
+ 'https://api.patchstack.com/monitor/sites/list/basic' \
+ -H 'UserToken: ' \
+```
+
+On large accounts, page through the list with `after_id` and `per_page` (default 100, max 1000):
+
+```bash
+curl -X 'POST' \
+ 'https://api.patchstack.com/monitor/sites/list/basic' \
+ -H 'UserToken: ' \
+ -H 'Content-Type: application/json' \
+ -d '{
+ "after_id": 0,
+ "per_page": 1000
+}'
+```
+
+Which outputs the following:
+```json
+{
+ "sites": [{ "id": 12345, "url": "https://site1.com" }, …],
+ "total": 2400,
+ "next_after_id": 13345
+}
+```
+
+Pass `next_after_id` as `after_id` in the next request until it is `null`.
\ No newline at end of file
diff --git a/src/content/docs/API solutions/App API/patchstack-reports-api.md b/src/content/docs/API solutions/App API/patchstack-reports-api.md
new file mode 100644
index 00000000..51268852
--- /dev/null
+++ b/src/content/docs/API solutions/App API/patchstack-reports-api.md
@@ -0,0 +1,88 @@
+---
+title: "Generating and downloading reports"
+hidden: false
+sidebar:
+ order: 4
+---
+
+_Generating reports through the Patchstack App API is available for the Developer and Enterprise plan users_
+
+You can generate [security reports](/patchstack-app/reports/reports-overview/) and download their PDFs over the [Patchstack App API](/api-solutions/app-api/patchstack-app-api/), for example to send monthly reports to your customers from your own platform.
+
+Reports are generated in the background, so getting a PDF takes three steps:
+
+1. Request a report with [`POST /report/generate/{site}`](https://api.patchstack.com/app-api/documentation)
+2. Find the finished report with [`POST /report/reports`](https://api.patchstack.com/app-api/documentation)
+3. Download the PDF from the report's `download_url`
+
+All examples use the App API root URL `https://api.patchstack.com/monitor/`. Replace `YOUR_APP_API_KEY` with your own [Patchstack App API key](/api-solutions/app-api/patchstack-app-api/#how-to-get-patchstack-app-api-key) and `12345` with your site identifier.
+
+### 1. Generate a report
+
+Send the report `type`, either `snapshot` or `developer`. A Developer report also needs a `from` and `to` date in the `D-M-YYYY` format.
+
+```bash
+curl -X POST "https://api.patchstack.com/monitor/report/generate/12345" \
+ -H "UserToken: YOUR_APP_API_KEY" \
+ -H "Content-Type: application/json" \
+ -d '{"type": "developer", "from": "1-9-2026", "to": "30-9-2026"}'
+```
+
+The response only confirms that the report was queued. It does not contain the PDF:
+
+```json
+{ "success": "The generation request has been sent." }
+```
+
+### 2. Find the generated report
+
+A report shows up in the report list once it is ready. A Developer report can take a few minutes. List the reports for the site, newest first:
+
+```bash
+curl -X POST "https://api.patchstack.com/monitor/report/reports" \
+ -H "UserToken: YOUR_APP_API_KEY" \
+ -H "Content-Type: application/json" \
+ -d '{"page": 1, "application": "12345"}'
+```
+
+Each report in the response has a `download_url`:
+
+```json
+{
+ "reports": [
+ {
+ "id": 1,
+ "site_id": 12345,
+ "type": "developer",
+ "hash": "1/1-eb0b4a0e-2866-436c-a7ee-cfffda415d21.pdf",
+ "raw_hash": "1-eb0b4a0e-2866-436c-a7ee-cfffda415d21",
+ "download_url": "https://api.patchstack.com/monitor/report/fetch/1-eb0b4a0e-2866-436c-a7ee-cfffda415d21",
+ "created_at": "2026-10-01 03:09:02"
+ }
+ ],
+ "total": 1
+}
+```
+
+To wait for a report you just requested, poll this endpoint until a new report for the site appears, for example once a minute. Compare its `id` with the newest report you saw before generating.
+
+### 3. Download the PDF
+
+Request the report's `download_url`. It redirects to a temporary link for the PDF, so tell your HTTP client to follow redirects:
+
+```bash
+curl -L -o report.pdf "https://api.patchstack.com/monitor/report/fetch/1-eb0b4a0e-2866-436c-a7ee-cfffda415d21"
+```
+
+- The download URL needs no API key, so you can hand it to your customer as it is.
+- The temporary link it redirects to is valid for one week. The `download_url` itself keeps working, so request it again for a fresh link.
+- If you build the URL yourself, use `raw_hash`, not `hash`. `raw_hash` is `hash` without the leading folder and the `.pdf` extension.
+- An unknown hash returns a `422` response with `{"error": "The given report could not be found."}`.
+
+:::caution[Treat download URLs like passwords]
+Anyone with a report's download URL can download that report. Only share it with the people the report is meant for.
+:::
+
+### Scheduled reports
+
+To get reports on a fixed schedule instead, create a schedule with [`POST /report/schedule/{site}/create`](https://api.patchstack.com/app-api/documentation). Scheduled reports show up in the same report list, so you can download them the same way. See [Scheduling reports](/patchstack-app/reports/scheduling-reports/) for how schedules work.
diff --git a/src/content/docs/API solutions/Threat Intelligence API/extended.md b/src/content/docs/API solutions/Threat Intelligence API/extended.md
index 732fe6b1..705efcd9 100644
--- a/src/content/docs/API solutions/Threat Intelligence API/extended.md
+++ b/src/content/docs/API solutions/Threat Intelligence API/extended.md
@@ -1,541 +1,135 @@
---
-title: "Extended tier API"
-excerpt: ""
+title: "Threat Intelligence API"
+excerpt: "WordPress vulnerability intelligence — single-product and bulk lookups, latest-24h feed, and advisory-by-id detail."
hidden: false
-metadata:
+metadata:
image: []
robots: "index"
createdAt: "Mon Jul 25 2022 09:29:10 GMT+0000 (Coordinated Universal Time)"
updatedAt: "Thu Jun 15 2023 11:25:44 GMT+0000 (Coordinated Universal Time)"
sidebar:
order: 2
+ label: "Guide"
---
-_The purpose of this document is to provide information about the Extended Threat Intelligence API functionality._
-
-## API Usage
-
-### Information
-
-The base URL of the API is
-
-All responses are in the JSON format. For performance reasons, responses are cached until we update the database after which the appropriate caches are cleared.
-
-An API key is required. This API key should be present in the **PSKey HTTP request header**. You can request an API key by reaching out to us on this page: https://patchstack.com/for-hosts/
-
-Explanation of the API response properties can be found here [here](/api-solutions/threat-intelligence-api/api-properties/).
-
-### Latest vulnerabilities
-
-**Description:** Retrieve the latest 20 vulnerabilities which have been added to the database.
-**Endpoint:** /latest
-**Method:** GET
-
-**Example response (trimmed)**
-
-```json
-{
- "vulnerabilities": [
- {
- "id": 7976,
- "product_id": 2175,
- "title": "WordPress File Upload plugin <= 4.16.2 - Contributor+ Path Traversal vulnerability leading to Remote Code Execution (RCE)",
- "description": "Contributor+ Path Traversal vulnerability leading to Remote Code Execution (RCE) discovered by apple502j in WordPress File Upload plugin (versions <= 4.16.2).",
- "disclosure_date": "2022-03-01 00:00:00",
- "disclosed_at": "2022-03-01T00:00:00+00:00",
- "created_at": "2022-03-07T11:17:05+00:00",
- "url": "wordpress-file-upload-plugin-4-16-2-contributor-path-traversal-vulnerability-leading-to-remote-code-execution-rce",
- "product_slug": "wp-file-upload",
- "product_name": "WordPress File Upload",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Directory Traversal",
- "cvss_score": 8.8,
- "cve": [
- "2021-24962"
- ],
- "is_exploited": false,
- "patch_priority": 3,
- "affected_in": "<= 4.16.2",
- "fixed_in": "4.16.3",
- "patched_in_ranges": [],
- "direct_url": "https://patchstack.com/database/vulnerability/wp-file-upload/wordpress-file-upload-plugin-4-16-2-contributor-path-traversal-vulnerability-leading-to-remote-code-execution-rce"
- },
- {
- "id": 7957,
- "product_id": 3808,
- "title": "WordPress All in One Invite Codes plugin <= 1.0.12 - Sensitive Information Disclosure vulnerability",
- "description": "Sensitive Information Disclosure vulnerability discovered in WordPress All in One Invite Codes plugin (versions <= 1.0.12).",
- "disclosure_date": "2022-02-28 00:00:00",
- "disclosed_at": "2022-02-28T00:00:00+00:00",
- "created_at": "2022-03-03T13:25:05+00:00",
- "url": "wordpress-all-in-one-invite-codes-plugin-1012-sensitive-information-disclosure-vulnerability",
- "product_slug": "all-in-one-invite-codes",
- "product_name": "All in One Invite Codes",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Information Disclosure",
- "cvss_score": 4.3,
- "cve": [],
- "is_exploited": false,
- "patch_priority": 1,
- "affected_in": "<= 1.0.12",
- "fixed_in": "",
- "patched_in_ranges": [],
- "direct_url": "https://patchstack.com/database/vulnerability/all-in-one-invite-codes/wordpress-all-in-one-invite-codes-plugin-1012-sensitive-information-disclosure-vulnerability"
- }
- ]
-}
-```
+_The Threat Intelligence API has **custom pricing and is activated on request** — [contact us](https://patchstack.com/for-hosts/)._
-### Find vulnerability
-
-**Description:** Retrieve vulnerabilities of a specific plugin, theme or WordPress core version.
-**Endpoint:** /product/TYPE/NAME/VERSION/EXISTS?
-**Method:** GET
-
-**TYPE** = theme, plugin, wordpress
-**NAME** = Slug of the theme, slug of the plugin, or “wordpress” in case TYPE is set to wordpress
-**VERSION** = Version to check for vulnerabilities
-**EXISTS** = Optional flag that will not return all vulnerabilities but only a boolean response whether or not there are vulnerabilities. This flag being present results in a faster response.
-
-**Example Response**
-
-```json
-{
- "vulnerabilities": [
- {
- "id": 4253,
- "product_id": 2642,
- "title": "WordPress Tutor LMS plugin <= 1.5.2 - Cross-Site Request Forgery (CSRF) vulnerability",
- "description": "Cross-Site Request Forgery (CSRF) vulnerability found by Jinson Varghese Behanan in WordPress Tutor LMS plugin (versions <= 1.5.2).",
- "disclosure_date": "2020-02-04 00:00:00",
- "disclosed_at": "2020-02-04T00:00:00+00:00",
- "created_at": "2021-01-08T13:50:05+00:00",
- "url": "wordpress-tutor-lms-plugin-1-5-2-cross-site-request-forgery-csrf-vulnerability",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Cross Site Request Forgery (CSRF)",
- "cvss_score": null,
- "cve": [
- "2020-8615"
- ],
- "is_exploited": false,
- "patch_priority": 1,
- "affected_in": "<= 1.5.2",
- "fixed_in": "1.5.3",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-5-2-cross-site-request-forgery-csrf-vulnerability"
- },
- {
- "id": 4386,
- "product_id": 2642,
- "title": "WordPress Tutor LMS plugin <= 1.7.6 - Multiple Blind/Time-based SQL Injection (SQLi) vulnerabilities",
- "description": "Multiple Blind/Time-based SQL Injection (SQLi) vulnerabilities were discovered by WordFence in the WordPress Tutor LMS plugin (versions <= 1.7.6).",
- "disclosure_date": "2021-03-15 00:00:00",
- "disclosed_at": "2021-03-15T00:00:00+00:00",
- "created_at": "2021-06-07T10:12:03+00:00",
- "url": "wordpress-tutor-lms-plugin-1-7-6-multiple-blind-time-based-sql-injection-sqli-vulnerabilities",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "SQL Injection",
- "cvss_score": 5.4,
- "cve": [],
- "is_exploited": false,
- "patch_priority": 2,
- "affected_in": "<= 1.7.6",
- "fixed_in": "1.7.7",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-7-6-multiple-blind-time-based-sql-injection-sqli-vulnerabilities"
- },
- {
- "id": 4387,
- "product_id": 2642,
- "title": "WordPress Tutor LMS plugin <= 1.8.2 - Multiple Union SQL Injection (SQLi) vulnerabilities",
- "description": "Multiple Union SQL Injection (SQLi) vulnerabilities were discovered by WordFence in the WordPress Tutor LMS plugin (versions <= 1.8.2).",
- "disclosure_date": "2021-03-15 00:00:00",
- "disclosed_at": "2021-03-15T00:00:00+00:00",
- "created_at": "2021-03-16T08:48:03+00:00",
- "url": "wordpress-tutor-lms-plugin-1-8-2-multiple-union-sql-injection-sqli-vulnerabilities",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "SQL Injection",
- "cvss_score": null,
- "cve": [],
- "is_exploited": false,
- "patch_priority": 2,
- "affected_in": "<= 1.8.2",
- "fixed_in": "1.8.3",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-8-2-multiple-union-sql-injection-sqli-vulnerabilities"
- },
- {
- "id": 4388,
- "product_id": 2642,
- "title": "WordPress Tutor LMS plugin <= 1.7.6 - Unprotected AJAX Action to Privilege Escalation vulnerability",
- "description": "Unprotected AJAX Action to Privilege Escalation vulnerability discovered by WordFence in WordPress Tutor LMS plugin (versions <= 1.7.6).",
- "disclosure_date": "2021-03-15 00:00:00",
- "disclosed_at": "2021-03-15T00:00:00+00:00",
- "created_at": "2021-08-31T08:00:05+00:00",
- "url": "wordpress-tutor-lms-plugin-1-7-6-unprotected-ajax-action-to-privilege-escalation-vulnerability",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Privilege Escalation",
- "cvss_score": null,
- "cve": [],
- "is_exploited": false,
- "patch_priority": 3,
- "affected_in": "<= 1.7.6",
- "fixed_in": "1.7.7",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-7-6-unprotected-ajax-action-to-privilege-escalation-vulnerability"
- },
- {
- "id": 4549,
- "product_id": 2642,
- "title": "WordPress Tutor LMS plugin <= 1.8.7 - Authenticated Local File Inclusion vulnerability",
- "description": "Authenticated Local File Inclusion vulnerability discovered by sasa in WordPress Tutor LMS plugin (versions <= 1.8.7)",
- "disclosure_date": "2021-04-05 00:00:00",
- "disclosed_at": "2021-04-05T00:00:00+00:00",
- "created_at": "2021-04-19T09:28:03+00:00",
- "url": "wordpress-tutor-lms-plugin-1-8-7-authenticated-local-file-inclusion-vulnerability",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Local File Inclusion",
- "cvss_score": 4.9,
- "cve": [
- "2021-24242"
- ],
- "is_exploited": false,
- "patch_priority": 1,
- "affected_in": "<= 1.8.7",
- "fixed_in": "1.8.8",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-8-7-authenticated-local-file-inclusion-vulnerability"
- },
- {
- "id": 5082,
- "product_id": 2642,
- "title": "WordPress Tutor LMS plugin <= 1.9.5 - Reflected Cross-Site Scripting (XSS) vulnerability",
- "description": "Reflected Cross-Site Scripting (XSS) vulnerability discovered by WPScanTeam in WordPress Tutor LMS plugin (versions <= 1.9.5).",
- "disclosure_date": "2021-08-09 00:00:00",
- "disclosed_at": "2021-08-09T00:00:00+00:00",
- "created_at": "2021-08-20T06:35:01+00:00",
- "url": "wordpress-tutor-lms-plugin-1-9-5-reflected-cross-site-scripting-xss-vulnerability",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Cross Site Scripting (XSS)",
- "cvss_score": 7.1,
- "cve": [],
- "is_exploited": false,
- "patch_priority": 2,
- "affected_in": "<= 1.9.5",
- "fixed_in": "1.9.6",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-9-5-reflected-cross-site-scripting-xss-vulnerability"
- },
- {
- "id": 5388,
- "product_id": 2642,
- "title": "WordPress Tutor LMS plugin <= 1.9.8 - Multiple Stored Cross-Site Scripting (XSS) vulnerabilities",
- "description": "Multiple Stored Cross-Site Scripting (XSS) vulnerabilities were discovered by Shivam Rai in the WordPress Tutor LMS plugin (versions <= 1.9.8).",
- "disclosure_date": "2021-09-20 00:00:00",
- "disclosed_at": "2021-09-20T00:00:00+00:00",
- "created_at": "2021-10-22T12:54:01+00:00",
- "url": "wordpress-tutor-lms-plugin-1-9-8-multiple-stored-cross-site-scripting-xss-vulnerabilities",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Cross Site Scripting (XSS)",
- "cvss_score": 6.9,
- "cve": [
- "2021-24740"
- ],
- "is_exploited": false,
- "patch_priority": 2,
- "affected_in": "<= 1.9.8",
- "fixed_in": "1.9.9",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-9-8-multiple-stored-cross-site-scripting-xss-vulnerabilities"
- }
- ]
-}
-```
+> **Interactive reference:** Every endpoint, parameter, request body and response shape is documented in the [Threat Intelligence API reference](/api-reference/threat-intelligence-extended/).
+>
+> **Tooling (Postman, SDK, LLM):** spec URLs and import instructions live on [Overview → Using the API with your tools](/api-solutions/threat-intelligence-api/overview/#using-the-api-with-your-tools).
-**Example Response**
-
-```json
-{
- "vulnerable": true
-}
-```
+This page covers the concepts you need to use the API effectively — authentication, rate limiting, errors, and code samples. Use it alongside the interactive reference.
-### Bulk find vulnerability
+## Endpoints at a glance
-**Description:** Retrieve vulnerabilities in bulk of a number of plugins, themes or WordPress versions.
-**Endpoint:** /batch
-**Method:** POST
-**Payload:** Raw JSON payload, same format as the individual vulnerability endpoint. This payload should contain no more than 50 objects.
+| Endpoint | Purpose |
+|---|---|
+| `GET /product/{type}/{name}/{version}` | Advisory list for a single product + version. |
+| `GET /product/{type}/{name}/{version}/exists` | Boolean-only exists check (faster). |
+| `GET /latest` | The 20 most recent vulnerabilities. |
+| `POST /batch` | Bulk lookup — up to 50 products per request. |
+| `GET /vulnerability/{id}` | Advisory detail (CVSS vector, OWASP, references, credit). |
-**Payload Example 1**
+Each per-item payload includes `description`, `vuln_type`, `cvss_score`, `cve`, `is_exploited`, `patch_priority`, `affected_in`, and `patched_in_ranges`. See [API properties](/api-solutions/threat-intelligence-api/api-properties/) for full field definitions.
-This payload example will determine if WooCommerce version 3.0.0 has vulnerabilities and if WordPress version 3.0.0 has vulnerabilities. It will also only return a boolean response.
+## Base URL
-```json
-[
- {"name":"easy-digital-downloads1","version":"1.0.0","type":"plugin","exists":true},
- {"name":"wordpress","version":"3.0.0","type":"wordpress","exists":true}
-]
+```
+https://patchstack.com/database/api/v2/
```
-**Example response 1**
+## Authentication
-```json
-{
- "vulnerabilities": {
- "easy-digital-downloads1": true,
- "wordpress": true
- }
-}
+Every request must include your API key in the **`PSKey`** HTTP request header. Access is activated on request — [contact us](https://patchstack.com/for-hosts/) to request a key.
+
+```
+PSKey:
```
-**Payload example 2**
+## Response format
-This payload example will determine if WooCommerce version 3.0.0 has vulnerabilities and if WordPress version 3.0.0 has vulnerabilities. For WooCommerce it will return all vulnerabilities and for WordPress if it will return a boolean response.
+All responses are JSON. Responses are cached until the Patchstack database updates, at which point the cache is cleared. `GET /vulnerability/{id}` returns a richer, differently-shaped payload documented in the [reference](/api-reference/threat-intelligence-extended/).
-```json
-[
- {"name":"easy-digital-downloads1","version":"1.0.0","type":"plugin","exists":false},
- {"name":"wordpress","version":"3.0.0","type":"wordpress","exists":true}
-]
-```
+## Batch lookups
-**Example response 2**
-
-```json
-{
- "vulnerabilities": {
- "easy-digital-downloads1": [
- {
- "id": 4532,
- "product_id": 1572,
- "title": "WordPress Easy Digital Downloads plugin <= 2.10.2 - Cross-Site Request Forgery (CSRF) vulnerability",
- "description": "Cross-Site Request Forgery (CSRF) vulnerability discovered by WPScan team in WordPress Easy Digital Downloads plugin (versions <= 2.10.2).",
- "disclosure_date": "2021-04-16 00:00:00",
- "disclosed_at": "2021-04-16T00:00:00+00:00",
- "created_at": "2021-04-19T04:43:04+00:00",
- "url": "wordpress-easy-digital-downloads-plugin-2-10-2-cross-site-request-forgery-csrf-vulnerability",
- "product_slug": "easy-digital-downloads1",
- "product_name": "Easy Digital Downloads",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Cross Site Request Forgery (CSRF)",
- "cvss_score": 6.5,
- "cve": [],
- "is_exploited": false,
- "affected_in": "<= 2.10.2",
- "fixed_in": "2.10.3",
- "direct_url": "https://patchstack.com/database/vulnerability/easy-digital-downloads1/wordpress-easy-digital-downloads-plugin-2-10-2-cross-site-request-forgery-csrf-vulnerability"
- },
- {
- "id": 5410,
- "product_id": 1572,
- "title": "WordPress Easy Digital Downloads plugin <= 2.11.2 - Authenticated Reflected Cross-Site Scripting (XSS) vulnerability",
- "description": "Authenticated Reflected Cross-Site Scripting (XSS) vulnerability discovered by Thinkland Security Team in WordPress Easy Digital Downloads plugin (versions <= 2.11.2).",
- "disclosure_date": "2021-10-21 00:00:00",
- "disclosed_at": "2021-10-21T00:00:00+00:00",
- "created_at": "2021-10-22T12:54:01+00:00",
- "url": "wordpress-easy-digital-downloads-plugin-2-11-2-authenticated-reflected-cross-site-scripting-xss-vulnerability",
- "product_slug": "easy-digital-downloads1",
- "product_name": "Easy Digital Downloads",
- "product_name_premium": null,
- "product_type": "Plugin",
- "vuln_type": "Cross Site Scripting (XSS)",
- "cvss_score": 4.8,
- "cve": [
- "2021-39354"
- ],
- "is_exploited": false,
- "affected_in": "<= 2.11.2",
- "fixed_in": "2.11.2.1",
- "direct_url": "https://patchstack.com/database/vulnerability/easy-digital-downloads1/wordpress-easy-digital-downloads-plugin-2-11-2-authenticated-reflected-cross-site-scripting-xss-vulnerability"
- }
- ],
- "wordpress": true
- }
-}
-```
+`POST /batch` accepts an array of up to 50 `{name, version, type, exists?}` items. The response is keyed by `product_slug`, not by array index — duplicate slugs in the request collapse. Per-item `exists: true` returns a boolean for that slug; `exists: false` (or omitted) returns the full advisory list.
-### Find specific vulnerability by ID
-
-**Description:** Find a specific vulnerability by vulnerability id.
-**Endpoint:** /vulnerability/ID
-**Method:** GET
-
-**ID** = Numeric identifier or PSID of the vulnerability.
-
-**Example response 1**
-
-```json
-{
- "vulnerability": {
- "title": "WordPress Spam protection, AntiSpam, FireWall by CleanTalk plugin <= 5.153.3 - Unauthenticated Time-Based Blind SQL Injection (SQLi) vulnerability",
- "description": "Unauthenticated Time-Based Blind SQL Injection (SQLi) vulnerability discovered by WordFence in WordPress Spam protection, AntiSpam, FireWall by CleanTalk plugin (versions <= 5.153.3).",
- "disclosure_date": "2021-05-03 00:00:00",
- "disclosed_at": "2021-05-03T00:00:00+00:00",
- "created_at": "2021-09-28T14:17:02+00:00",
- "is_exploited": true,
- "url": "wordpress-spam-protection-antispam-firewall-by-cleantalk-plugin-5-153-3-unauthenticated-time-based-blind-sql-injection-sqli-vulnerability",
- "direct_url": "https://patchstack.com/database/vulnerability/cleantalk-spam-protect/wordpress-spam-protection-antispam-firewall-by-cleantalk-plugin-5-153-3-unauthenticated-time-based-blind-sql-injection-sqli-vulnerability"
- },
- "product": {
- "name": "Spam protection, AntiSpam, FireWall by CleanTalk",
- "slug": "cleantalk-spam-protect",
- "type": "Plugin"
- },
- "type": "SQL Injection",
- "cvss": {
- "score": 7.5,
- "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
- "description": ""
- },
- "owasp": "A1: Injection",
- "references_url": [
- {
- "url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24295",
- "title": "CVE"
- },
- {
- "url": "https://www.wordfence.com/blog/2021/05/sql-injection-vulnerability-patched-in-cleantalk-antispam-plugin/",
- "title": "Vulnerability details"
- },
- {
- "url": "https://wordpress.org/plugins/cleantalk-spam-protect/#developers",
- "title": "Plugin changelog"
- }
- ],
- "cve": [
- "2021-24295"
- ],
- "versions": {
- "affected_in": "<= 5.153.3",
- "fixed_in": "5.153.4"
- },
- "versions_list": null,
- "credit": {
- "name": "WordFence",
- "url": "https://twitter.com/wordfence"
- },
- "submitter": null
-}
-```
+## Rate limiting
-**Example response 2**
-
-```json
-{
- "vulnerability": {
- "title": "WordPress Simple File List plugin <= 4.2.2 - Unauthenticated Arbitrary File Upload vulnerability leading to Remote Code Execution (RCE)",
- "description": "Unauthenticated Arbitrary File Upload vulnerability leading to Remote Code Execution (RCE) discovered by h00die and coiffeur in WordPress Simple File List plugin (versions <= 4.2.2).",
- "disclosure_date": "2020-04-27 00:00:00",
- "disclosed_at": "2020-04-27T00:00:00+00:00",
- "created_at": "2021-04-23T15:55:02+00:00",
- "is_exploited": false,
- "url": "wordpress-simple-file-list-plugin-4-2-2-unauthenticated-arbitrary-file-upload-vulnerability-leading-to-remote-code-execution-rce",
- "direct_url": "https://patchstack.com/database/vulnerability/simple-file-list/wordpress-simple-file-list-plugin-4-2-2-unauthenticated-arbitrary-file-upload-vulnerability-leading-to-remote-code-execution-rce"
- },
- "product": {
- "name": "Simple File List",
- "slug": "simple-file-list",
- "type": "Plugin"
- },
- "type": "SQL Injection",
- "cvss": {
- "score": 9.8,
- "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
- "description": ""
- },
- "owasp": "A1: Injection",
- "references_url": [
- {
- "url": "https://packetstormsecurity.com/files/160221/",
- "title": "Vulnerability details"
- },
- {
- "url": "https://wordpress.org/plugins/simple-file-list/#developers",
- "title": "Plugin changelog"
- }
- ],
- "cve": [],
- "versions": {
- "affected_in": "<= 4.2.2",
- "fixed_in": "4.2.3"
- },
- "versions_list": null,
- "credit": {
- "name": "coiffeur",
- "url": "https://packetstormsecurity.com/files/author/14922/"
- },
- "submitter": {
- "name": "h00die",
- "url": "https://packetstormsecurity.com/files/author/7166/"
- }
-}
+Custom, set per contract. Contact if you need a quota change.
+
+## Errors
+
+| Status | Meaning |
+|---|---|
+| `401 Unauthorized` | Missing or invalid `PSKey` header. |
+| `403 Forbidden` | API key not authorised for the requested endpoint. |
+| `404 Not Found` | Unknown product/version or vulnerability id. |
+| `422 Unprocessable Entity` | Invalid request payload (e.g. batch with more than 50 items). |
+| `429 Too Many Requests` | Rate limit exceeded. |
+| `500` | Server error — please include the request id in any bug report. |
+
+---
+
+## Testing — curl one-liners
+
+```bash
+# Latest 20 vulnerabilities
+curl 'https://patchstack.com/database/api/v2/latest' \
+ -H 'PSKey: '
+
+# Full advisory list for a plugin version
+curl 'https://patchstack.com/database/api/v2/product/plugin/tutor/1.5.2' \
+ -H 'PSKey: '
+
+# Boolean-only exists check
+curl 'https://patchstack.com/database/api/v2/product/plugin/tutor/1.5.2/exists' \
+ -H 'PSKey: '
+
+# Batch — boolean-only across two products
+curl -X POST 'https://patchstack.com/database/api/v2/batch' \
+ -H 'PSKey: ' \
+ -H 'Content-Type: application/json' \
+ -d '[
+ {"name":"easy-digital-downloads1","version":"1.0.0","type":"plugin","exists":true},
+ {"name":"wordpress","version":"3.0.0","type":"wordpress","exists":true}
+ ]'
+
+# Advisory detail by id
+curl 'https://patchstack.com/database/api/v2/vulnerability/4760' \
+ -H 'PSKey: '
```
-**Example response 3**
-
-```json
-{
- "vulnerability": {
- "title": "WordPress Redux Framework <= 4.1.23 - Cross-Site Request Forgery (CSRF) Nonce Validation Bypass vulnerability",
- "description": "Cross-Site Request Forgery (CSRF) Nonce Validation Bypass vulnerability found by ErwanLR in WordPress Redux Framework (versions 4.1.22 - 4.1.23).",
- "disclosure_date": "2020-12-15 00:00:00",
- "disclosed_at": "2020-12-15T00:00:00+00:00",
- "created_at": "2020-12-15T18:36:01+00:00",
- "is_exploited": false,
- "url": "wordpress-redux-framework-4-1-23-cross-site-request-forgery-csrf-nonce-validation-bypass-vulnerability",
- "direct_url": "https://patchstack.com/database/vulnerability/redux-framework/wordpress-redux-framework-4-1-23-cross-site-request-forgery-csrf-nonce-validation-bypass-vulnerability"
- },
- "product": {
- "name": "Redux Framework",
- "slug": "redux-framework",
- "type": "Plugin"
- },
- "type": "SQL Injection",
- "cvss": null,
- "owasp": "A1: Injection",
- "references_url": [
- {
- "url": "https://plugins.trac.wordpress.org/changeset/2437953/redux-framework/trunk/redux-core/inc/classes/class-redux-ajax-save.php?old=2405408",
- "title": "Vulnerability details"
- },
- {
- "url": "https://github.com/reduxframework/redux-framework-4/blob/master/CHANGELOG.md",
- "title": "Plugin changelog"
- }
- ],
- "cve": [],
- "versions": {
- "affected_in": "<= 4.1.23",
- "fixed_in": "4.1.24"
- },
- "versions_list": "4.1.23, 4.1.22",
- "credit": {
- "name": "ErwanLR",
- "url": "https://profiles.wordpress.org/erwanlr/"
- },
- "submitter": null
+## Batch walk (PHP)
+
+```php
+ 'easy-digital-downloads1', 'version' => '1.0.0', 'type' => 'plugin', 'exists' => false],
+ ['name' => 'wordpress', 'version' => '3.0.0', 'type' => 'wordpress', 'exists' => true],
+];
+
+$ch = curl_init('https://patchstack.com/database/api/v2/batch');
+curl_setopt_array($ch, [
+ CURLOPT_RETURNTRANSFER => true,
+ CURLOPT_POST => true,
+ CURLOPT_HTTPHEADER => ['PSKey: '.$apiKey, 'Content-Type: application/json'],
+ CURLOPT_POSTFIELDS => json_encode($components),
+]);
+$response = json_decode(curl_exec($ch), true);
+curl_close($ch);
+
+foreach ($response['vulnerabilities'] as $slug => $result) {
+ if (is_bool($result)) {
+ echo "{$slug}: ".($result ? 'vulnerable' : 'clear').PHP_EOL;
+ } else {
+ echo "{$slug}: ".count($result)." advisor".(count($result) === 1 ? 'y' : 'ies').PHP_EOL;
+ }
}
```
-## More information about the Threat Intelligence API
+## More information
-You can find more information about Threat Intelligence API here:
-https://patchstack.com/for-hosts/
+You can find more information about the Patchstack Threat Intelligence API on . If you have integration questions, email .
diff --git a/src/content/docs/API solutions/Threat Intelligence API/npm-features.md b/src/content/docs/API solutions/Threat Intelligence API/npm-features.md
new file mode 100644
index 00000000..6153a714
--- /dev/null
+++ b/src/content/docs/API solutions/Threat Intelligence API/npm-features.md
@@ -0,0 +1,202 @@
+---
+title: "NPM features"
+excerpt: "npm-ecosystem coverage and the supporting additions on top of the Threat Intelligence API — the /all endpoint, cursor pagination, ?include=details, and the nested response shape."
+hidden: false
+metadata:
+ image: []
+ robots: "index"
+createdAt: "Tue Apr 21 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+updatedAt: "Mon Aug 24 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+sidebar:
+ order: 1
+ label: "Overview"
+---
+
+_The npm features extend the Threat Intelligence API with npm-ecosystem coverage. They run at a separate base URL, ship their own OpenAPI spec, and are available to **selected partners working directly with Patchstack**. The shared endpoints (`/latest`, `/product/{type}/{name}/{version}`, `/product/{type}/{name}/{version}/exists`, `/batch`) behave the same as the stable API but accept extra parameters and return a nested response shape. This page documents only what's new — for the full spec including npm-flavour examples, see the [auto-generated reference](/api-reference/threat-intelligence-npm/). [Contact us](https://patchstack.com/for-hosts/) if you'd like access._
+
+:::note
+This partner API is not the only way to get npm vulnerability coverage. Developers can monitor their own JS/Node projects directly with [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/), Patchstack's official self-install npm connector — no partner agreement needed.
+:::
+
+## Base URL
+
+```
+https://vdp-api.patchstack.com/database/api/npm/
+```
+
+:::note
+The previous base URL `https://vdp-api.patchstack.com/database/api/beta/` remains supported as a permanent legacy alias and returns identical responses, so existing integrations don't need to change immediately.
+:::
+
+## What's new
+
+| Addition | Where it applies |
+|---|---|
+| [`GET /all`](/api-reference/threat-intelligence-npm/operations/listallvulnerabilities/) | New endpoint — cursor-paginated full listing of every advisory, scoped by `?platform=`. |
+| `?platform=npm` | List endpoints (`/all`, `/latest`, `/product/...`). Default is `wordpress`; case-insensitive. |
+| `?cursor=` | `/all` and `/latest` — cursor pagination alongside the existing `?page=&per_page=`. |
+| `?updated_since=` | `/all` in cursor mode — only entries changed since a unix time. See [Incremental sync](#incremental-sync). |
+| `product.type` | Every record. The product kind in lower case: `plugin`, `theme`, `wordpress` (core) or `npm`. |
+| `?include=details` | List endpoints — adds an `advisory_details` markdown field to each item (npm). |
+| Nested response shape | All list endpoints — `product`, `cvss`, `cwe`, `version_info` objects in place of the v2 flat shape. |
+
+The full npm-features schema (every endpoint, parameter, response example) lives in the [auto-generated reference](/api-reference/threat-intelligence-npm/).
+
+## Pagination
+
+`/all` and `/latest` support **two independent strategies**. Use whichever fits your client:
+
+- **Offset (`?page=&per_page=`)** — returns a `pagination` block with totals, `has_next_page`, `has_previous_page`, etc. Easy to jump to a specific page; slower at depth and susceptible to row-shift when new advisories land while you're paging.
+- **Cursor (`?cursor=`)** — returns a `cursor` block with `next_cursor`, `has_more`, `per_page`. Stable under concurrent inserts and faster at any depth. No `total` count (deliberately skipped to keep cursor mode fast).
+
+`cursor` and `page` are mutually exclusive; passing both returns `422 Unprocessable Entity`. To bootstrap cursor mode, send `?cursor=` with an empty value.
+
+When a cursor is malformed (invalid base64 or missing the `v1:` prefix), the endpoint returns `200` with an empty page:
+
+```json
+{
+ "vulnerabilities": [],
+ "cursor": { "next_cursor": null, "has_more": false, "per_page": 100 }
+}
+```
+
+## Incremental sync
+
+Mirroring the whole feed on every run is slow. After the first full listing, ask only for what changed:
+
+1. Every `/all` response has a `watermark`: the unix time its rows were read. Keep the oldest one from your last sync.
+2. Next time, walk `/all?cursor=&updated_since=`. You get the entries changed since then (new ones, and edits such as a new fixed version), and on the first page `removed_ids`: entries withdrawn since then. Replace changed entries by `id` and drop the removed ones.
+3. Store the new `watermark` for the run after that.
+
+Starting a minute before the watermark is safe: entries are re-sent, never lost. An entry deleted outright doesn't show up in `removed_ids`, so run a full listing now and then (daily is plenty). `updated_since` needs cursor mode; with `page` it returns `422 Unprocessable Entity`.
+
+```bash
+curl 'https://vdp-api.patchstack.com/database/api/npm/all?platform=wordpress&per_page=500&cursor=&updated_since=1793018157' \
+ -H 'PSKey: YOUR_KEY'
+```
+
+```json
+{
+ "vulnerabilities": [ { "id": 46510, "product": { "id": 37, "name": "…", "slug": "…", "type": "plugin" }, "…": "…" } ],
+ "cursor": { "next_cursor": null, "has_more": false, "per_page": 500 },
+ "watermark": 1793018399,
+ "removed_ids": [46412]
+}
+```
+
+## Scoped npm packages
+
+npm package slugs that include a `/` (e.g. `@scope/pkg`) conflict with the route separator. URL-encode the `/` as `%2F` or contact us for guidance on the encoding helper.
+
+## Errors
+
+In addition to the [stable error codes](/api-solutions/threat-intelligence-api/extended/#errors), the npm endpoints return:
+
+| Status | Meaning |
+|---|---|
+| `422 Unprocessable Entity` | Invalid parameter combination (e.g. `cursor` + `page`, or `updated_since` without `cursor`), invalid `platform`, or `per_page > 500`. |
+
+## Migration notes (stable v2 → npm endpoints)
+
+- npm responses use **nested objects** (`product`, `cvss`, `cwe`, `capec`, `version_info`) whereas the v2 shape is flat. Update parsers accordingly.
+- `ghsa_id` was renamed to `ghsa` at the top level.
+- `direct_url` was renamed to `url` (the npm-flavoured shape exposes a single URL only).
+- The `description` field was dropped for npm (the title already includes it).
+- The response body always contains a `vulnerabilities` array, plus either `pagination` (offset mode) or `cursor` (cursor mode).
+
+## Multi-span advisories and the fix to show
+
+Many npm advisories affect several majors at once. Product lookups (`GET /product/...` and `/batch`) now match the installed version against **every** affected span, not only the lowest one.
+
+When a version matches, the advisory includes a `matched_range` object beside the existing top-level `fixed_in`:
+
+| Field | Meaning |
+|---|---|
+| `matched_range.from_version` | Lower bound of the span that matched the installed version (nullable). |
+| `matched_range.to_version` | Upper bound of that span (nullable). |
+| `matched_range.to_bound` | How to read `to_version`: `exclusive`, `inclusive`, `last-affected`, or `null` when unrecorded. |
+| `matched_range.fixed_in` | The fix for **this** span. Use this when telling a user what to upgrade to. `null` means that span was never fixed. |
+
+Top-level `fixed_in` / `version_info.fixed` remain the **highest** fix across every span, for backwards compatibility. Prefer `matched_range.fixed_in` for user-facing upgrade advice so a site on `next@13` is not told to jump to a later major.
+
+---
+
+## Testing
+
+### curl — one-liners
+
+```bash
+# Latest 24h, npm
+curl 'https://vdp-api.patchstack.com/database/api/npm/latest?platform=npm&per_page=10' \
+ -H 'PSKey: '
+
+# Cursor pagination walk (bootstrap + follow)
+curl 'https://vdp-api.patchstack.com/database/api/npm/all?platform=npm&per_page=50&cursor=' \
+ -H 'PSKey: '
+
+# Check a specific npm package/version with full advisory text
+curl 'https://vdp-api.patchstack.com/database/api/npm/product/npm/axios/0.21.4?include=details' \
+ -H 'PSKey: '
+
+# Boolean-only exists check
+curl 'https://vdp-api.patchstack.com/database/api/npm/product/npm/axios/0.21.4/exists' \
+ -H 'PSKey: '
+```
+
+### Cursor iteration (JavaScript / Node)
+
+```javascript
+async function* allVulnerabilities(apiKey, platform = 'npm', perPage = 100) {
+ const base = 'https://vdp-api.patchstack.com/database/api/npm/all';
+ let cursor = ''; // empty = bootstrap cursor mode
+
+ while (true) {
+ const url = `${base}?platform=${platform}&per_page=${perPage}&cursor=${encodeURIComponent(cursor)}`;
+ const res = await fetch(url, { headers: { PSKey: apiKey } }).then(r => r.json());
+
+ for (const vuln of res.vulnerabilities) {
+ yield vuln;
+ }
+
+ if (!res.cursor.has_more) return;
+ cursor = res.cursor.next_cursor;
+ }
+}
+
+// usage
+for await (const vuln of allVulnerabilities(process.env.PATCHSTACK_KEY)) {
+ console.log(vuln.id, vuln.title);
+}
+```
+
+### Cursor iteration (PHP)
+
+```php
+ true,
+ CURLOPT_HTTPHEADER => ['PSKey: '.$apiKey, 'Accept: application/json'],
+ ]);
+ $response = json_decode(curl_exec($ch), true);
+ curl_close($ch);
+
+ foreach ($response['vulnerabilities'] as $vuln) {
+ // handle $vuln
+ }
+
+ $cursor = $response['cursor']['next_cursor'] ?? null;
+} while ($response['cursor']['has_more'] ?? false);
+```
+
+## More information
+
+You can find more information about the Patchstack Threat Intelligence API on . If you have integration questions, email .
diff --git a/src/content/docs/API solutions/Threat Intelligence API/overview.md b/src/content/docs/API solutions/Threat Intelligence API/overview.md
index 3cc7628a..85219a39 100644
--- a/src/content/docs/API solutions/Threat Intelligence API/overview.md
+++ b/src/content/docs/API solutions/Threat Intelligence API/overview.md
@@ -1,23 +1,80 @@
----
-title: "Overview"
-excerpt: ""
-metadata:
- image: []
- robots: "index"
-createdAt: "Thu Jun 01 2023 12:04:17 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Mon Jul 31 2023 12:13:26 GMT+0000 (Coordinated Universal Time)"
-sidebar:
- order: 1
- label: "Overview"
- hidden: false
----
-
-### Standard Threat Intelligence API
-Fetch the latest vulnerability information for a single version of a particular plugin, theme or WordPress core. API is limited for 5000 calls / 24 hours. Price for that API is $249 / month. Access to this API can be purchased through the [Patchstack App](https://app.patchsatck.com/billing/subscription).
-
-[Standard Threat Intelligence API Documentation](/api-solutions/threat-intelligence-api/standard/)
-
-### Extended Threat Intelligence API
-Access everything included in the Standard tier, bulk-request data for multiple plugins with one API call, and have additional endpoints with more information about vulnerabilities. Extended tier has custom pricing and is activated on request only. For access to these API endpoints, please [contact us here](https://patchstack.com/for-hosts/).
-
-[Extended Threat Intelligence API Documentation](/api-solutions/threat-intelligence-api/extended/)
\ No newline at end of file
+---
+title: "Overview"
+excerpt: ""
+metadata:
+ image: []
+ robots: "index"
+createdAt: "Thu Jun 01 2023 12:04:17 GMT+0000 (Coordinated Universal Time)"
+updatedAt: "Mon Jul 31 2023 12:13:26 GMT+0000 (Coordinated Universal Time)"
+sidebar:
+ order: 1
+ label: "Overview"
+ hidden: false
+---
+
+The Patchstack Threat Intelligence API exposes our vulnerability database for WordPress plugins, themes and core. It supports single-product lookups, bulk lookups (`POST /batch`, up to 50 products per request), the `/latest` rolling feed, advisory-by-id detail, and a per-item payload that includes `cvss_score`, `cve`, `is_exploited`, `patch_priority`, and `patched_in_ranges`.
+
+Custom pricing, activated on request — [contact us](https://patchstack.com/for-hosts/).
+
+- [Guide](/api-solutions/threat-intelligence-api/extended/) · [Reference](/api-reference/threat-intelligence-extended/) · [OpenAPI](/schemas/threat-intel-extended.yaml) · [Postman](/schemas/threat-intel-extended.postman_collection.json) · [API properties](/api-solutions/threat-intelligence-api/api-properties/)
+
+## NPM features
+
+For partners covering JavaScript components, the npm features add **npm-ecosystem coverage** alongside WordPress, available to **selected partners working directly with Patchstack**. Beyond npm itself they ship the supporting additions that make npm coverage workable at scale: the new `GET /all` endpoint, cursor pagination, `?include=details` for full advisory bodies, and a nested response shape the stable API will eventually adopt. Everything else (`/latest`, `/product/{type}/{name}/{version}`, `/batch`) is the same surface as the stable API.
+
+See the [NPM features](/api-solutions/threat-intelligence-api/npm-features/) page for the full delta — base URL, parameters, pagination, errors, and migration notes — and the [auto-generated reference](/api-reference/threat-intelligence-npm/) for the full schema. [Contact us](https://patchstack.com/for-hosts/) for access.
+
+---
+
+The legacy [Standard tier](/api-solutions/threat-intelligence-api/standard/) is no longer offered to new customers but remains documented for existing integrations — its endpoints are a strict subset of the current API.
+
+---
+
+## Using the API with your tools
+
+The API ships with an OpenAPI spec and a generated Postman collection. The npm features have their own spec — pick whichever you're integrating against:
+
+| | OpenAPI spec | Postman collection |
+|---|---|---|
+| Threat Intelligence API | [`threat-intel-extended.yaml`](/schemas/threat-intel-extended.yaml) | [`threat-intel-extended.postman_collection.json`](/schemas/threat-intel-extended.postman_collection.json) |
+| NPM features | [`threat-intel-npm.yaml`](/schemas/threat-intel-npm.yaml) | [`threat-intel-npm.postman_collection.json`](/schemas/threat-intel-npm.postman_collection.json) |
+| Standard *(legacy)* | [`threat-intel-standard.yaml`](/schemas/threat-intel-standard.yaml) | [`threat-intel-standard.postman_collection.json`](/schemas/threat-intel-standard.postman_collection.json) |
+
+### Postman, Insomnia, Bruno or Hoppscotch
+
+Every endpoint, parameter, request body and example is preconfigured. Download the Postman collection and drag it into your tool, or import by URL from inside the tool:
+
+| Tool | How to import |
+|---|---|
+| **Postman** | `File → Import → Link` and paste the collection URL. |
+| **Insomnia** | `Create → Import From → URL` → paste the OpenAPI URL. |
+| **Bruno** | `Collection → Import → OpenAPI V3 Spec` → paste the OpenAPI URL. |
+| **Hoppscotch** | `Collections → Import/Export → OpenAPI` → paste the OpenAPI URL. |
+
+**Authentication:** in Postman set the collection `Authorization` to **API Key**, key `PSKey`, value `{{PSKEY}}`, and add `PSKEY` as a collection variable with your real key as the **Current value** (leave Initial blank so it doesn't sync to teammates). Other tools work the same way — set `PSKey` as a collection header once.
+
+### Claude Code and other LLM coding assistants
+
+Point your assistant at the spec. LLMs parse OpenAPI cleanly and will generate clients that match the real field names instead of hallucinating.
+
+- **Ad hoc:** paste the spec URL into your prompt. Example: *"Write a Python client for `https://docs.patchstack.com/schemas/threat-intel-extended.yaml`. I need a batch walker over a `package.json`-style list."*
+- **In your repo:** download the spec to `docs/vendor/patchstack-threat-intel.yaml` and reference it from your `CLAUDE.md` / `AGENTS.md`. Your assistant can then grep the YAML for specific fields without refetching.
+- **Plain-text fallback:** for tools that don't parse YAML, our [`llms-full.txt`](/llms-full.txt) contains the full reference as flat markdown.
+
+### SDK generation
+
+Generate a client in any language from the spec:
+
+```bash
+# TypeScript
+npx @openapitools/openapi-generator-cli generate \
+ -i https://docs.patchstack.com/schemas/threat-intel-extended.yaml \
+ -g typescript-fetch -o ./patchstack-client
+
+# Python
+npx @openapitools/openapi-generator-cli generate \
+ -i https://docs.patchstack.com/schemas/threat-intel-extended.yaml \
+ -g python -o ./patchstack-client-py
+```
+
+Speakeasy and Fern also consume the same spec and produce more idiomatic SDKs if you need a polished client library.
diff --git a/src/content/docs/API solutions/Threat Intelligence API/standard.md b/src/content/docs/API solutions/Threat Intelligence API/standard.md
index 42acb36e..5d855bd5 100644
--- a/src/content/docs/API solutions/Threat Intelligence API/standard.md
+++ b/src/content/docs/API solutions/Threat Intelligence API/standard.md
@@ -1,77 +1,76 @@
---
title: "Standard tier API"
-excerpt: ""
-metadata:
+excerpt: "Entry-level WordPress vulnerability lookup — single product + version, 5,000 requests per day."
+metadata:
image: []
robots: "index"
createdAt: "Mon Jul 25 2022 09:28:24 GMT+0000 (Coordinated Universal Time)"
updatedAt: "Wed May 10 2023 12:26:10 GMT+0000 (Coordinated Universal Time)"
sidebar:
order: 1
+ label: "Guide"
---
-_If you’re looking for an API that has a complete data coverage and could be used commercially, please look at the Extended Threat Intelligence API here._
-
-## API Usage
-
-The Standard Threat Intelligence API is limited to 5000 requests per 24 hours.
-
-The base URL of the API is
-
-All responses are in JSON format. For performance reasons, responses are cached until we update the database after which the appropriate caches are cleared.
-
-An API key is required. This API key should be present in the _PSKey_ HTTP request header. You can request an API key by logging into your Patchstack App account and then by going to the Upgrades page .
-
-Explanation of the API response properties can be found here [here](/api-solutions/threat-intelligence-api/api-properties/).
-
-## Find Vulnerability
-
-**Description:** Retrieve vulnerabilities of a specific plugin, theme or WordPress core version.
-**Endpoint:** /product/TYPE/NAME/VERSION/EXISTS?
-**Method:** GET
-
-**TYPE** = theme, plugin, wordpress
-**NAME** = Slug of the theme, slug of the plugin, or “wordpress” in case TYPE is set to wordpress
-**VERSION** = Version to check for vulnerabilities
-**EXISTS** = Optional flag that will not return all vulnerabilities but only a boolean response whether or not there are vulnerabilities. This flag being present results in a faster response.
-
-Example response ():
-
-```json
-{
- "vulnerabilities": [
- {
- "id": 4253,
- "title": "WordPress Tutor LMS plugin <= 1.5.2 - Cross-Site Request Forgery (CSRF) vulnerability",
- "disclosed_at": "2020-02-04T00:00:00+00:00",
- "created_at": "2022-05-27T10:23:01+00:00",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "fixed_in": "1.5.3",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-5-2-cross-site-request-forgery-csrf-vulnerability"
- },
- {
- "id": 4386,
- "title": "WordPress Tutor LMS plugin <= 1.7.6 - Multiple Blind/Time-based SQL Injection (SQLi) vulnerabilities",
- "disclosed_at": "2021-03-15T00:00:00+00:00",
- "created_at": "2022-05-27T10:23:01+00:00",
- "product_slug": "tutor",
- "product_name": "Tutor LMS",
- "product_name_premium": null,
- "product_type": "Plugin",
- "fixed_in": "1.7.7",
- "direct_url": "https://patchstack.com/database/vulnerability/tutor/wordpress-tutor-lms-plugin-1-7-6-multiple-blind-time-based-sql-injection-sqli-vulnerabilities"
- }
- ]
-}
+_The Standard Threat Intelligence API is **no longer offered to new customers**. New integrations should use the [Threat Intelligence API](/api-solutions/threat-intelligence-api/extended/), which is a strict superset — every endpoint and field documented here is available there. This page is preserved for existing Standard integrations._
+
+> **Interactive reference:** Every endpoint, parameter and response shape is documented in the [Threat Intelligence API (Standard) reference](/api-reference/threat-intelligence-standard/).
+>
+> **Tooling (Postman, SDK, LLM):** spec URLs and import instructions for all three tiers live on [Overview → Using the APIs with your tools](/api-solutions/threat-intelligence-api/overview/#using-the-apis-with-your-tools).
+
+This page covers the concepts you need to use the API effectively — authentication, rate limiting, errors, and code samples. Use it alongside the interactive reference.
+
+## Base URL
+
+```
+https://patchstack.com/database/api/v2/
```
-Example response ():
+## Authentication
+
+Every request must include your API key in the **`PSKey`** HTTP request header. Standard keys remain valid for existing customers. New keys are not issued — [contact us](https://patchstack.com/for-hosts/) about Extended.
-```json
-{
- "vulnerable": true
-}
```
+PSKey:
+```
+
+## Response format
+
+All responses are JSON. Responses are cached until the Patchstack database updates, at which point the cache is cleared.
+
+The Standard tier returns a **flat** per-item shape. For the richer shape with `description`, `vuln_type`, `cvss_score`, `cve`, and `patched_in_ranges`, use the [Extended tier](/api-solutions/threat-intelligence-api/extended/). Field definitions live in [API properties](/api-solutions/threat-intelligence-api/api-properties/).
+
+## Rate limiting
+
+Standard is limited to **5,000 requests per 24 hours**. Contact to move to Extended for a higher quota and additional endpoints.
+
+## Errors
+
+| Status | Meaning |
+|---|---|
+| `401 Unauthorized` | Missing or invalid `PSKey` header. |
+| `403 Forbidden` | API key not authorised for the requested endpoint. |
+| `404 Not Found` | Unknown product/version combination. |
+| `429 Too Many Requests` | Rate limit exceeded. |
+| `500` | Server error — please include the request id in any bug report. |
+
+---
+
+## Testing — curl one-liners
+
+```bash
+# Full advisory list for a plugin version
+curl 'https://patchstack.com/database/api/v2/product/plugin/tutor/1.5.2' \
+ -H 'PSKey: '
+
+# Boolean-only exists check (faster)
+curl 'https://patchstack.com/database/api/v2/product/plugin/tutor/1.5.2/exists' \
+ -H 'PSKey: '
+
+# WordPress core
+curl 'https://patchstack.com/database/api/v2/product/wordpress/wordpress/5.8.2' \
+ -H 'PSKey: '
+```
+
+## More information
+
+You can find more information about the Patchstack Threat Intelligence API on . If you have integration questions, email .
diff --git a/src/content/docs/API solutions/index.mdx b/src/content/docs/API solutions/index.mdx
index 5813b82f..f5b0faf7 100644
--- a/src/content/docs/API solutions/index.mdx
+++ b/src/content/docs/API solutions/index.mdx
@@ -25,28 +25,11 @@ This API has unlimited requests and can be used by all Developer plan users for
-## Threat Intelligence API
-Query our vulnerability database and retrieve information about all published vulnerabilities. Threat Intelligence API is available in two tiers:
-
-### Standard tier
-Fetch the latest vulnerability information for a single version of a particular plugin, theme or WordPress core. API is limited for 5000 calls / 24 hours. Price for that API is $249 / month.
-
-
-
- Read more here
-
-
-
-### Extended tier
-Access everything included in the Standard tier, bulk-request data for multiple plugins with one API call, and have additional endpoints with more information about vulnerabilities. Extended tier has custom pricing and is activated on request only.
+## Threat Intelligence API
+Query our vulnerability database and retrieve information about all published vulnerabilities. The Extended tier covers single-product lookups, bulk-request endpoints for multiple components in one call, the `/latest` rolling feed, and advisory-by-id detail. Custom pricing, activated on request.
DEFINITIONS
+Your data, and how we handle it, should never be a mystery. Everything you need for a GDPR review lives on patchstack.com, where we keep it current, so the documents below are the single source of truth.
-Site – website available at patchstack.com
-Services – the services available from and related to the domain and subdomains of the Site
-Patchstack (also referred to as “we”, “our” or “us”) – Patchstack OÜ, a company incorporated and registered under the laws of the Republic of Estonia with registration code 14331217
-User (also referred to as “you” or “your”) – an individual who creates a user account
-General Terms – terms and conditions of services.
+## Data Processing Addendum (DPA)
-We provide services for B2B clients and therefore, privacy regulations (GDPR - General Data Protection Regulation) do not apply for such data, however, we might provide services also for individuals and therefore, we are informing you about personal data processes herein.
+Need a DPA on file? Download our pre-signed Data Processing Addendum, countersign it, and email it to privacy@patchstack.com.
-Our Privacy Notice describes how we collect, use, process, and disclose your information related to your access to using the Patchstack services.
+[Read and download the DPA](https://patchstack.com/dpa/)
-Our Services include a website security firewall to prevent cyber attacks and to protect your websites. Using Patchstack or any other Services, we do not collect any personal data about users of your website or website owners. In the event, we detect website hacking incidents we are not allocating any personal data because hackers are hiding identity and do not reveal identifiable IP addresses, names, e-mail addresses, or any personal data. Therefore, we are in a position where we are not processing any personal data of the hackers as well.
+## Privacy Policy
-Therefore as we are not collecting personal data, there is no need to sign a data processing agreement between you and Patchstack.
+Our Privacy Policy explains what personal data we collect, why we collect it, how long we keep it, and the rights you have over it.
+
+[Read the Privacy Policy](https://patchstack.com/privacy-policy/)
+
+## Terms and Conditions
+
+The Terms and Conditions cover the rules of using Patchstack's services, for you and for us.
+
+[Read the Terms and Conditions](https://patchstack.com/terms-and-conditions/)
+
+Still have a question about privacy or compliance? Write to us at privacy@patchstack.com and we'll help.
diff --git a/src/content/docs/FAQ Troubleshooting/Pricing Plans/does-patchstack-have-a-free-version.md b/src/content/docs/FAQ Troubleshooting/Pricing Plans/does-patchstack-have-a-free-version.md
index c041065a..0d2d1f3e 100644
--- a/src/content/docs/FAQ Troubleshooting/Pricing Plans/does-patchstack-have-a-free-version.md
+++ b/src/content/docs/FAQ Troubleshooting/Pricing Plans/does-patchstack-have-a-free-version.md
@@ -7,7 +7,7 @@ metadata:
image: []
robots: "index"
createdAt: "Wed Jul 27 2022 12:18:00 GMT+0000 (Coordinated Universal Time)"
-updatedAt: "Wed Jun 28 2023 12:35:06 GMT+0000 (Coordinated Universal Time)"
+updatedAt: "Tue Oct 13 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
sidebar:
order: 3.1
---
@@ -25,19 +25,20 @@ Patchstack has a free version available. Free version of Patchstack detects vuln
**What does Patchstack Personal (Free) version include?**
**Detect security issues before hackers take over your website:**
-
Detect the latest security vulnerabilities in your WordPress, Drupal or Joomla sites.
+
Detect the latest security vulnerabilities in your WordPress or Drupal sites.
Receive real-time alerts to email if any security vulnerabilities are found.
-
Have a central security dashboard for up to 3 websites (via the Patchstack App).
+
Have a central security dashboard for up to 3 websites (via the Patchstack App).
+
Update WordPress plugins, themes and core remotely from your site's Packages tab.
+
Generate Snapshot reports: a PDF of a site's current security status.
+
+Patchstack no longer updates software automatically. You choose when to update, and protection (below) blocks attacks on known vulnerabilities in the meantime — see [Automatic updates](/patchstack-app/site-dashboard/site-software/#automatic-updates).
**What's the difference between a free version and paid version?**
-The free version of Patchstack only detects and notifies you about the vulnerabilities in the software versions your sites use. The paid version of Patchstack will also protect against malicious traffic and attacks exploiting known serious vulnerabilities on your site. The pricing for Patchstack protection starts from $5 / month per site.
+The free version of Patchstack detects and notifies you about the vulnerabilities in the software versions your sites use, and lets you update that software yourself. The paid version of Patchstack will also protect against malicious traffic and attacks exploiting known serious vulnerabilities on your site. The pricing for Patchstack protection starts from $5 / month per site.
### For WordPress
To use a free version of Patchstack with WordPress, install the Patchstack plugin on your site first, and start the user registration flow from the plugin itself, after activating it on your WordPress.
-### For Joomla
-To use a free version of Patchstack with Joomla, you'll need to sign up for the Developer plan trial first. After that, you can downgrade your subscription from Developer plan to Personal plan (Free). Add your site to Patchstack App, and go through this tutorial to install the Patchstack connector to your Joomla site.
-
### For Drupal
To use a free version of Patchstack with Drupal, you'll need to sign up for the Developer plan trial first. After that, you can downgrade your subscription from Developer plan to Personal plan (Free). Add your site to Patchstack App, and go through this tutorial to install the Patchstack connector to your Drupal site.
diff --git a/src/content/docs/FAQ Troubleshooting/Technical/can-i-use-the-same-plugin-api-key-for-staging-environment.md b/src/content/docs/FAQ Troubleshooting/Technical/can-i-use-the-same-plugin-api-key-for-staging-environment.md
index a9d77376..0a641696 100644
--- a/src/content/docs/FAQ Troubleshooting/Technical/can-i-use-the-same-plugin-api-key-for-staging-environment.md
+++ b/src/content/docs/FAQ Troubleshooting/Technical/can-i-use-the-same-plugin-api-key-for-staging-environment.md
@@ -34,7 +34,17 @@ Patchstack allows you to use the same plugin API key for the staging environment
'wpengine.com',
'wp-dv',
'optiserver.co.uk',
-'azurewebsites.net'
+'azurewebsites.net',
+'artdev.space',
+'artevio.dev',
+'artevio.art',
+'copilhost.cloud',
+'.myftpupload.com',
+'.mwp.accessdomain.com',
+'store.godaddy.com',
+'stuurlui.dev',
+'flyinghost.app',
+'.wpenginepowered.com'
```
### How the staging and production site work with Patchstack?
@@ -42,7 +52,7 @@ Patchstack will work normally with your live site, if you share the same API key
Some things to keep in mind:
- Your production (live) site receives all the real-time protection rules
- All custom hardening rules set in Patchstack App are also synced normally
-- All the features that Patchstack offers, will work on your live site (like auto-updates, custom rules, etc)
+- All the features that Patchstack offers, will work on your live site (like custom rules, etc)
- On the staging site however, only the API key license check will work. Other features and firewall rules are not synced to the staging site
- We recommend turning on the server level protection for your staging site (e.g. htaccess and htpasswd)
diff --git a/src/content/docs/FAQ Troubleshooting/Technical/does-patchstack-work-with-other-captcha-plugins.md b/src/content/docs/FAQ Troubleshooting/Technical/does-patchstack-work-with-other-captcha-plugins.md
index 3586c085..23f483df 100644
--- a/src/content/docs/FAQ Troubleshooting/Technical/does-patchstack-work-with-other-captcha-plugins.md
+++ b/src/content/docs/FAQ Troubleshooting/Technical/does-patchstack-work-with-other-captcha-plugins.md
@@ -15,6 +15,6 @@ Patchstack plugin can add either Google ReCAPTCHA or Cloudflare Turnstile to you
Patchstack, by default, has the captcha features turned off. You can pick to which pages you would like to add the capcha -- login, register, forgot password, and comments.
-Note that Patchstack's captcha only works with WordPress's built-in forms and not for other plugins forms (like e-commerce registration forms).
+Note that Patchstack's captcha works with WordPress's built-in forms and WooCommerce forms, but not with other plugins' forms.
If you turn this feature on and have a different plugin installed that has the same kind of functionality, you may get locked out of your WordPress site. In this scenario, you'd have to delete either plugin to regain access to your site.
diff --git a/src/content/docs/FAQ Troubleshooting/Technical/how-to-add-security-headers-with-patchstack.md b/src/content/docs/FAQ Troubleshooting/Technical/how-to-add-security-headers-with-patchstack.md
index 4be61ffe..85d06d60 100644
--- a/src/content/docs/FAQ Troubleshooting/Technical/how-to-add-security-headers-with-patchstack.md
+++ b/src/content/docs/FAQ Troubleshooting/Technical/how-to-add-security-headers-with-patchstack.md
@@ -13,6 +13,8 @@ sidebar:
---
If you have the Patchstack plugin installed, we will automatically try to inject the security headers into the response.
+Because these headers can be injected into the HTTP response at runtime, they may not appear in your `.htaccess` file even when they are active. To confirm which headers are being sent, check the live response (for example with [securityheaders.com](https://securityheaders.com/)) instead of reading `.htaccess`. Avoid adding the same headers both automatically and manually, or you may end up with duplicate headers. For how these settings relate to each other, see [How hardening and security headers work](/patchstack-app/site-dashboard/hardening/hardening-and-security-headers-explained/).
+
If this does not work, perhaps due to an aggressive caching plugin or caching/proxy server, you may have to manually add the .htaccess rules below to your .htaccess file.
## Adding the security headers automatically
diff --git a/src/content/docs/FAQ Troubleshooting/Technical/list-of-ip-addresses-that-patchstack-uses.mdx b/src/content/docs/FAQ Troubleshooting/Technical/list-of-ip-addresses-that-patchstack-uses.mdx
index 7dfbd0cb..4f10823e 100644
--- a/src/content/docs/FAQ Troubleshooting/Technical/list-of-ip-addresses-that-patchstack-uses.mdx
+++ b/src/content/docs/FAQ Troubleshooting/Technical/list-of-ip-addresses-that-patchstack-uses.mdx
@@ -10,9 +10,11 @@ updatedAt: "Tue May 16 2023 14:17:00 GMT+0000 (Coordinated Universal Time)"
sidebar:
order: 7.3
---
-import Ips from '../../../../components/Ips.astro';
+Sometimes you need to whitelist our IP addresses in order to avoid your hosting provider or (secondary) firewall blocking our services.
-Sometimes you need to whitelist these IP addresses in order to avoid your hosting provider or (secondary) firewall blocking our services.
+You can use these two API endpoints to get the list of IP addresses that Patchstack uses:
+
+- [patchstack.com/ips-v4/](https://patchstack.com/ips-v4/)
+- [patchstack.com/ips-v6/](https://patchstack.com/ips-v6/)
Note that we may add and remove IP addresses at any time without notice.
-
diff --git a/src/content/docs/FAQ Troubleshooting/Technical/will-patchstack-plugin-help-my-site-pass-pci-dss-soc2-iso-127001-or-other-security-checks.md b/src/content/docs/FAQ Troubleshooting/Technical/will-patchstack-plugin-help-my-site-pass-pci-dss-soc2-iso-27001-or-other-security-checks.md
similarity index 93%
rename from src/content/docs/FAQ Troubleshooting/Technical/will-patchstack-plugin-help-my-site-pass-pci-dss-soc2-iso-127001-or-other-security-checks.md
rename to src/content/docs/FAQ Troubleshooting/Technical/will-patchstack-plugin-help-my-site-pass-pci-dss-soc2-iso-27001-or-other-security-checks.md
index 4052f621..ade320b1 100644
--- a/src/content/docs/FAQ Troubleshooting/Technical/will-patchstack-plugin-help-my-site-pass-pci-dss-soc2-iso-127001-or-other-security-checks.md
+++ b/src/content/docs/FAQ Troubleshooting/Technical/will-patchstack-plugin-help-my-site-pass-pci-dss-soc2-iso-27001-or-other-security-checks.md
@@ -1,5 +1,5 @@
---
-title: "Will Patchstack plugin help my site pass PCI-DSS, SOC2, ISO 127001 or other security checks?"
+title: "Will Patchstack plugin help my site pass PCI-DSS, SOC2, ISO 27001 or other security checks?"
excerpt: ""
hidden: false
metadata:
diff --git a/src/content/docs/Getting Started/Installing Patchstack/ai-assistant-blocked-a-command.mdx b/src/content/docs/Getting Started/Installing Patchstack/ai-assistant-blocked-a-command.mdx
new file mode 100644
index 00000000..c5a5f10b
--- /dev/null
+++ b/src/content/docs/Getting Started/Installing Patchstack/ai-assistant-blocked-a-command.mdx
@@ -0,0 +1,110 @@
+---
+title: "My AI assistant blocked a Connect command"
+excerpt: "Claude Code or another coding assistant refused to run npm install or npx @patchstack/connect setup. Run the command yourself — in Claude Code, with the ! prefix — and let the assistant carry on."
+hidden: false
+createdAt: "Wed Sep 30 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+updatedAt: "Wed Sep 30 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+sidebar:
+ order: 7.5
+ label: "AI assistant blocked a command"
+---
+
+import { Steps, Aside } from '@astrojs/starlight/components';
+
+Coding assistants such as Claude Code check each shell command before running it, and some of those checks stop a command that downloads or runs a package from npm. Installing [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/) involves both, so the install can stop part-way with a message like one of these:
+
+```text
+Auto mode's safety check blocked the install and flagged it as bringing
+untrusted code into the project. Nothing has changed.
+```
+
+```text
+I installed @patchstack/connect as a dependency, but I haven't set it up.
+My permission check blocked running the package's own setup command, because
+that means running code downloaded from npm on your machine.
+```
+
+The commands that usually get stopped are the install itself (`npm install --save-dev @patchstack/connect`, or the `pnpm`, `yarn` or `bun` equivalent) and `npx @patchstack/connect setup`.
+
+**Running the command yourself is fine.** It is the same command the assistant was about to run, it changes only what [`setup` is documented to change](/getting-started/installing-patchstack/installing-on-javascript-node-projects/#install), and it sends Patchstack dependency names and versions only — see [Security and data handling](/getting-started/installing-patchstack/installing-on-javascript-node-projects/#security-and-data-handling).
+
+
+
+## In Claude Code: run it with `!`
+
+Type the command in the Claude Code prompt with `!` in front of it. Claude Code runs it in your session straight away, without the permission check, and the output lands in the conversation — so Claude sees the result and can finish the rest of the install.
+
+
+
+1. **Run whichever command was blocked.** If the install was blocked, install the package with the project's package manager:
+
+ ```text
+ ! npm install --save-dev @patchstack/connect
+ ```
+
+ If the install went through and `setup` was blocked, run `setup`:
+
+ ```text
+ ! npx @patchstack/connect setup
+ ```
+
+ If the message you pasted from the app carried a claim token (you ticked **Connect this website to my account automatically**), keep it on the command so the site is created attached to your account:
+
+ ```text
+ ! npx @patchstack/connect setup --claim-token
+ ```
+
+2. **Let Claude continue.** Once the command finishes, tell Claude to carry on — for example with the prompt below. It picks up from the output it can now see: finishing anything `setup` lists as missing, running the build, and handing you the dashboard link.
+
+3. **Check server-side protection, if your app has a server.** For an Express, Fastify, or other server app, confirm the protection is wired up:
+
+ ```text
+ ! npx @patchstack/connect protect --check
+ ```
+
+
+
+```text
+I ran the blocked Patchstack command myself; the output is above. Please
+continue the @patchstack/connect install from there: finish anything setup
+lists as missing, run the complete production build, and give me the
+Patchstack dashboard link. Tell me if any other command is blocked instead of
+reporting the install as complete.
+```
+
+### Allow the Connect commands for this project
+
+If you would rather Claude Code ran the Connect commands itself — for example because you reinstall or rescan often — add an allow rule to `.claude/settings.json` in the project, then ask Claude to retry:
+
+```json
+{
+ "permissions": {
+ "allow": [
+ "Bash(npx @patchstack/connect:*)"
+ ]
+ }
+}
+```
+
+Add the rule yourself. Claude Code will usually decline to edit its own permissions to get past a check that has just stopped it.
+
+## In other assistants and site builders
+
+Codex, OpenCode, Gemini CLI, Cursor and the rest each have their own approval settings, but the fix is the same: run the blocked command yourself from the project folder, then tell the assistant it has been run.
+
+
+
+1. Open a terminal in the project folder — the one containing `package.json`.
+2. Run the command the assistant was blocked on, using the project's package manager (check the lockfile: `package-lock.json` is npm, `pnpm-lock.yaml` is pnpm, `yarn.lock` is yarn, `bun.lock` or `bun.lockb` is bun).
+3. Paste the command's output into the chat along with the prompt above, so the assistant continues from where the command left off instead of starting again.
+
+
+
+Site builders such as Lovable, GoDaddy Airo and Hostinger Horizons do not always give you a terminal. If yours has none and the assistant cannot run the install, ask it to name the exact step it cannot perform — the [builder context](/getting-started/installing-patchstack/troubleshooting-javascript-node-projects/#tell-your-builder-what-project-this-is) snippets help with that.
+
+## Still stuck?
+
+- `npx @patchstack/connect guide` prints a project-aware checklist of what is present and what is missing, so you can see how far the install got.
+- [Troubleshooting JS / Node.js](/getting-started/installing-patchstack/troubleshooting-javascript-node-projects/) covers what can go wrong after the install: a widget that never appears, a stale published build, or an outdated Connect version.
diff --git a/src/content/docs/Getting Started/Installing Patchstack/installing-on-javascript-node-projects.md b/src/content/docs/Getting Started/Installing Patchstack/installing-on-javascript-node-projects.md
new file mode 100644
index 00000000..e73c44d1
--- /dev/null
+++ b/src/content/docs/Getting Started/Installing Patchstack/installing-on-javascript-node-projects.md
@@ -0,0 +1,130 @@
+---
+title: "Installing on JavaScript / Node.js projects"
+excerpt: "Connect any JS/Node project to Patchstack vulnerability monitoring with the official @patchstack/connect npm package."
+hidden: false
+createdAt: "Tue Jul 14 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+updatedAt: "Wed Jul 15 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+sidebar:
+ order: 7.3
+ label: "JavaScript / Node.js projects"
+---
+
+Patchstack monitors JavaScript and Node.js applications — not only WordPress sites — through [`@patchstack/connect`](https://www.npmjs.com/package/@patchstack/connect), the official Patchstack Connect package, maintained and published by Patchstack on npm under the `@patchstack` organization.
+
+- **npm:** https://www.npmjs.com/package/@patchstack/connect
+- **Source (MIT-licensed):** https://github.com/patchstack/connect
+- **Setup guide:** https://github.com/patchstack/connect/blob/main/GETTING-STARTED.md
+
+## What it does
+
+Connect reads the project's dependency lockfile (`package-lock.json`, `pnpm-lock.yaml`, or `yarn.lock`; bun projects are detected via `node_modules/`) and reports package names and versions to Patchstack, which matches them against its vulnerability database and notifies you when a dependency needs patching. It works with any framework — Next.js, Vite, Nuxt, Remix, SvelteKit, TanStack Start, plain Node — and with npm, pnpm, yarn, and bun.
+
+It sends dependency names and versions only: no source code, no environment variable values, no file paths, no git history.
+
+## Install
+
+No signup, dashboard step, or UUID is needed up front. Install the package as a development dependency, then run `setup`:
+
+```bash
+npm install --save-dev @patchstack/connect # or: pnpm add -D / yarn add -D / bun add -d
+npx --no-install patchstack-connect setup
+```
+
+If your coding assistant refuses to run either command — Claude Code's permission check sometimes stops installs from npm — run it yourself; see [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/).
+
+`setup` applies a bounded, idempotent set of changes and nothing else:
+
+1. **Scans the lockfile and sends the dependency manifest** (package names and versions) to Patchstack.
+2. **Provisions a Patchstack site** on the first run and writes its UUID to `.patchstackrc.json` (commit this file); later runs reuse the existing site instead of creating a duplicate.
+3. **Manages the Patchstack Connector tag** in the project's root HTML shell (the first of `index.html`, `public/index.html`, or `src/app.html` that exists) — see the widget section below.
+4. **Adds production build integration to `package.json`:** `scan` runs before the build and `mark-build` after it, via `prebuild`/`postbuild` lifecycle hooks (or a direct build chain on bun, which skips npm-style hooks). Existing build commands are preserved, dev scripts are untouched, and `setup` never runs the build itself.
+5. **Prints a status checklist** of anything that still needs a manual step, such as framework-specific widget placement.
+
+`setup` ends by printing a **dashboard link**. The CLI never opens the link and never asks for Patchstack credentials. The site is monitored either way; connecting it to an account is what makes the reports visible to you — see [Connecting the site to your account](#connecting-the-site-to-your-account) for the three ways to do that.
+
+### Connecting the site to your account
+
+A site that is scanning but not connected is an anonymous record: it is monitored, but its reports have nowhere to go, and because the site UUID is public and claiming is first-come, it stays claimable by anyone who loads the page. Any one of these attaches it, and they all end in the same place:
+
+1. **From the widget on your own site — the shortest route.** While the site is unclaimed, the widget on your preview shows a one-time **"Connect this website"** panel. Sign in there and the site is attached; no terminal, no copied URL, and no link to find. This is where claiming is meant to happen, which is why the panel appears in the builder's edit preview by default.
+2. **From the dashboard link.** Open the link `setup`, `scan`, or `status` printed in your browser and sign in.
+3. **From the terminal.** `npx @patchstack/connect claim` prints a link to sign in with, then attaches the site to that account.
+
+On a **published** build the connect panel is hidden from ordinary visitors (see [the Patchstack Connector](#the-patchstack-connector) below). As the owner you can still reach the sign-in there by loading any page with `#patchstack` appended to the URL — `?patchstack` works too.
+
+Once the site is connected, the panel never appears again, and the widget shows the public report form instead.
+
+### Connecting straight to your account
+
+If you start from the app — **Sites → Add new → AI-assisted** — and tick **Connect this website to my account automatically**, the message it gives you to paste into your assistant carries a **claim token** for your account, and the assistant runs `setup` with it:
+
+```bash
+npx @patchstack/connect setup --claim-token
+# or: PATCHSTACK_CLAIM_TOKEN= npx @patchstack/connect setup
+```
+
+The site is then created already attached to your account, `setup` prints your dashboard link for it, and the app's **Connect website** panel picks the site up on its own. The token names your account, not the project: it is never written to `.patchstackrc.json` or the credential file, and it stops working after a day. An expired or unrecognised token does not break the install — the site is created unattached, exactly as it would be without one, and `setup` prints the dashboard link to connect it by hand.
+
+`setup` never runs the `protect` command (see below).
+
+### Manual alternative
+
+The same pieces can be applied individually: `npx @patchstack/connect scan` performs steps 1–3, and the build hooks can be added by hand:
+
+```jsonc
+{
+ "scripts": {
+ "prebuild": "patchstack-connect scan",
+ "postbuild": "patchstack-connect mark-build"
+ }
+}
+```
+
+Run `npx @patchstack/connect guide` at any time for a project-aware checklist of what is present and what is missing, with commands tailored to the project. `npx @patchstack/connect status` re-prints the site UUID and dashboard link.
+
+## The Patchstack Connector
+
+Connect installs the **Patchstack Connector**, Patchstack's vulnerability disclosure widget — a floating control that becomes a "Report a vulnerability" button once the site is connected to an account, so anyone who spots an issue can report it straight to you. The widget is a single script tag loading `https://cdn.patchstack.com/patchstack-widget.js`, configured with the site UUID (which is public by design — it ships in client-side HTML and is not a secret). A pre-existing manually placed widget tag is left untouched, and `mark-build` ensures the tag in build output (`dist/`, `build/`, `out/`, `.output/public`) without ever editing source.
+
+Frameworks without a static HTML shell need a one-line placement in the root layout; `guide` prints the exact snippet for the detected framework, and the [widget reference](https://cdn.patchstack.com/llm.html) covers additional patterns.
+
+To run without the widget, set `"widget": false` in `.patchstackrc.json` — this disables all widget management; otherwise the next scan re-adds the tag.
+
+**What the widget shows depends on whether the site is connected to an account.** While it is unclaimed, the widget serves the one-time "Connect this website" panel *instead of* the report button — so on a fresh install the first thing you see is the sign-in, not the floating button. Connect the site and the panel is replaced by the public **Report a vulnerability** button for good. To skip the onboarding entirely and always show the report form, set `data-build-mode="false"` on the script tag.
+
+On a **published** build Connect's `mark-build` hook stamps `window.__PATCHSTACK_PROD__` into the built HTML, which hides the connect panel and the owner "Log in" link from visitors and leaves the report form only. Owners reach the sign-in there with `#patchstack` (or `?patchstack`) appended to any page URL.
+
+See [Troubleshooting JS / Node.js](/getting-started/installing-patchstack/troubleshooting-javascript-node-projects/) if the widget does not appear at all.
+
+### Signing in to the widget on your site
+
+The widget's sign-in form leads with **Continue with Patchstack**: one click signs you in with the account you are already signed in to at app.patchstack.com — no password, no provider round trip, and it works for SSO and two-factor accounts too. In Chrome and Edge the button already names your account ("Continue as …"); Safari and Firefox do not let the widget see that, so there it is unnamed but works the same way. If you are not signed in to app.patchstack.com in that browser, the widget says so and the e-mail, Google, GitHub and LinkedIn options are right underneath.
+
+## The `protect` command
+
+The package also ships an **opt-in** `protect` command: a runtime exploit guard, currently for TanStack Start + Supabase applications, which patches the app's Supabase client to route traffic through a same-origin guard. It modifies application code and runs **only** when explicitly invoked — `setup`, `scan`, `guide`, `status`, and `mark-build` never invoke it. If you don't run `protect`, no application code is changed beyond the widget tag and `package.json` scripts described above.
+
+## Security and data handling
+
+- **Data sent to Patchstack:** dependency package names and versions from the lockfile, plus a build fingerprint from `mark-build`. No source code, environment variable values, file paths, or git history is transmitted.
+- **Files written locally:** `.patchstackrc.json` (site UUID and settings), the widget script tag in the root HTML shell, and the `scan`/`mark-build` entries in `package.json` scripts. `mark-build` additionally stamps build output, never source.
+- **External resources:** the widget script is loaded in the browser from `https://cdn.patchstack.com/patchstack-widget.js`. The CLI itself downloads and executes nothing from a URL.
+- **Dashboard link:** printed to the terminal only; the CLI never opens it and never asks for credentials.
+
+## Uninstalling
+
+1. Note the site UUID from `.patchstackrc.json` before deleting anything — it identifies the site in the dashboard.
+2. Remove the widget tag (and any `PatchstackWidget.init(...)` call) from the layout or HTML shell.
+3. Remove the `patchstack-connect scan` / `patchstack-connect mark-build` parts from `package.json` scripts, keeping any chained commands.
+4. Uninstall with the manager matching the lockfile: `npm uninstall` / `pnpm remove` / `yarn remove` / `bun remove` `@patchstack/connect`.
+5. Delete `.patchstackrc.json` and any `PATCHSTACK_SITE_UUID` environment variables.
+
+Reporting stops immediately. Local removal does not delete the site record on Patchstack's side: an unclaimed site is an anonymous record that stops receiving reports; a claimed site can be removed in the dashboard at https://app.patchstack.com.
+
+## Troubleshooting
+
+A widget that never appears, a published site serving an old build, a broken config file, or a Connect install stuck on an old version are all covered — with copy-paste prompts for AI site builders — in [Troubleshooting JavaScript / Node.js projects](/getting-started/installing-patchstack/troubleshooting-javascript-node-projects/). If the assistant never got that far because it would not run `npm install` or `setup`, see [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/).
+
+## How this relates to host-level npm protection
+
+Hosting partners can enable npm vulnerability intelligence for the sites they host through the partner-level [Threat Intelligence API npm features](/api-solutions/threat-intelligence-api/npm-features/). That integration is applied by the host at the infrastructure level. `@patchstack/connect` is the complementary self-service path: developers install it directly into their own projects, whether or not their host is a Patchstack partner. Both feed the same vulnerability database.
diff --git a/src/content/docs/Getting Started/Installing Patchstack/troubleshooting-javascript-node-projects.mdx b/src/content/docs/Getting Started/Installing Patchstack/troubleshooting-javascript-node-projects.mdx
new file mode 100644
index 00000000..e9d8f06d
--- /dev/null
+++ b/src/content/docs/Getting Started/Installing Patchstack/troubleshooting-javascript-node-projects.mdx
@@ -0,0 +1,284 @@
+---
+title: "Troubleshooting JavaScript / Node.js projects"
+excerpt: "Fix a Patchstack Connector that never appears or appears twice, a published build that serves an old integration, a broken config file, or an outdated @patchstack/connect — including prompts to paste into an AI site builder."
+hidden: false
+createdAt: "Mon Sep 07 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+updatedAt: "Wed Sep 09 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
+sidebar:
+ order: 7.4
+ label: "Troubleshooting JS / Node.js"
+---
+
+import { Steps, Aside } from '@astrojs/starlight/components';
+
+This page covers the problems that come up after connecting a JavaScript or Node.js project with [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/): a Patchstack Connector that never appears, a widget that appears twice, a published site still serving an old integration, a build that broke after a config change, a Connect install stuck on an old version, and an update that will not take because the package manager is holding the release back.
+
+If the install never finished because your AI assistant refused to run `npm install` or `npx @patchstack/connect setup`, start with [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/) instead.
+
+Every section ends with a **prompt you can paste into your site builder's AI chat**. The prompts are deliberately explicit about proving the result, because builder assistants otherwise tend to report the version they remember, or stop after editing one file.
+
+
+
+## Tell your builder what project this is
+
+AI builders differ in which package manager they use and which controls they expose. Prepend the snippet for your platform to any prompt below.
+
+**Lovable**
+
+```text
+This is a Lovable project. Inspect the existing lockfile before installing
+anything. Lovable projects often use Bun; if bun.lock or bun.lockb exists, use
+Bun and do not create a package-lock.json beside it.
+```
+
+**GoDaddy Airo**
+
+```text
+This is a GoDaddy Airo project. Make the changes in the project workspace and
+use its existing package manager. If Airo does not expose the required install
+or build control, tell me exactly which step is unavailable instead of
+reporting that the task is complete.
+```
+
+**Hostinger Horizons**
+
+```text
+This is a Hostinger Horizons project. Use its existing package manager and allow
+the dependency install and full production build to finish before checking the
+result; do not treat a slow build as a failed one.
+```
+
+**Anything else, or not sure**
+
+```text
+First identify this project's package manager from its lockfile and use that
+same package manager for every command. Do not create a second lockfile.
+```
+
+## The widget is not visible on my site
+
+The visitor-facing **Report a vulnerability** button does not appear until the site is connected to a Patchstack account. If you installed Connect and never saw it, that is usually the reason rather than a broken install — work through these in order.
+
+
+
+1. **Connect the site to your account.** While the site is unclaimed the widget shows a one-time **"Connect this website"** panel *instead of* the report button. Sign in through that panel — on your preview it is already on the page — and the button takes its place permanently. The [dashboard link](/getting-started/installing-patchstack/installing-on-javascript-node-projects/#connecting-the-site-to-your-account) and `npx @patchstack/connect claim` do the same thing from a browser or a terminal.
+
+ To skip the onboarding entirely and always show the report form, set `data-build-mode="false"` on the script tag:
+
+ ```html
+
+ ```
+
+2. **Open the widget as the site owner.** On a published build the connect panel and the owner "Log in" link are hidden from visitors, so neither is a sign the install failed. Load any page of your site with `#patchstack` appended to the URL:
+
+ ```text
+ https://your-site.com/#patchstack
+ ```
+
+ That reveals the owner log-in even on a live production build, and it works from any device or network. `?patchstack` in the query string does the same thing.
+
+3. **Check the script tag actually shipped.** View source on the published page (not the builder preview) and confirm there is exactly one script loading `https://cdn.patchstack.com/patchstack-widget.js`, with `data-site-uuid` set to the UUID from your committed `.patchstackrc.json`.
+
+4. **Check the site UUID is a literal value.** The UUID must be written into the HTML. Reading it from `VITE_*`, `NEXT_PUBLIC_*`, or another environment-only variable that is not defined at build time leaves the attribute empty and the widget silent. The site UUID is public by design — it ships in client-side HTML and is not a secret.
+
+5. **Check the widget was not disabled.** `"widget": false` in `.patchstackrc.json` turns off all widget management, and the next `scan` will not re-add the tag.
+
+6. **Check the browser console.** A Content Security Policy that omits `cdn.patchstack.com` from `script-src`, or a content blocker, will stop the script from loading. Both show up as an error on the live page.
+
+
+
+
+
+### Prompt: widget missing after publish
+
+Use this when the widget works in the builder preview but is absent from the published site.
+
+```text
+Please diagnose why the Patchstack Connector works in preview but is missing from
+the published site.
+
+1. Use the latest @patchstack/connect release from npm.
+2. Confirm the root page contains exactly one Connect-managed script from
+ https://cdn.patchstack.com/patchstack-widget.js with data-site-uuid set from
+ the public .patchstackrc.json value.
+3. Do not read the site UUID from VITE_*, NEXT_PUBLIC_*, or another
+ environment-only variable.
+4. Run the Connect setup/scan flow and the complete production build,
+ including mark-build where the project scripts require it.
+5. Inspect the generated production output — not only source files — and verify
+ that the widget script and window.__PATCHSTACK_PROD__ marker are present.
+6. Publish that verified output, then check the live page and browser console
+ for the first concrete error.
+
+Please make the fix and show the production evidence. Thank you.
+```
+
+## The published widget still looks outdated
+
+Your source can be correct while the builder or CDN is still serving an older artifact. Confirm the live URL — not the preview — is loading the current script, and compare the version the widget reports in each.
+
+The widget shows its version in the owner dashboard. If preview and live disagree, the deployment is stale, not the code.
+
+```text
+Please verify that the published site is actually serving the newest Patchstack
+integration rather than an older build artifact.
+
+1. Confirm @patchstack/connect matches the newest release the project's
+ package manager will install. A release published in the last 24 hours may
+ be held back — see the section below.
+2. Confirm the site loads the Patchstack CDN script rather than a copied local
+ patchstack-widget.js file.
+3. Run a clean production build through the project's normal build command and
+ wait for it to finish.
+4. Republish the new output and invalidate only the relevant builder/deployment
+ cache if the platform exposes that control.
+5. On the live URL, inspect the Network response for patchstack-widget.js and
+ the version shown by the widget. Compare that with preview and report both
+ values.
+
+Please do not stop at a source-code check; verify the live deployment.
+Thank you.
+```
+
+## Is this the latest Connect version?
+
+Site builders often resolve `@patchstack/connect` from cached package metadata and land on an older release. Check what npm actually has:
+
+```bash
+npm view @patchstack/connect version
+```
+
+Then compare it against **the lockfile**, not `package.json`. The lockfile records what is installed; `package.json` records what was asked for, and the two can disagree — see the next section. If they differ, install `@patchstack/connect@latest` with the package manager that matches your lockfile.
+
+```text
+Please update @patchstack/connect from the official npm registry. Please do not
+rely on a remembered or cached version.
+
+1. Query npm for the current dist-tag with: npm view @patchstack/connect version.
+2. Install @patchstack/connect@latest as a regular dependency with the package
+ manager already used by this project.
+3. Confirm the exact installed version in the LOCKFILE, not package.json, and
+ with @patchstack/connect --version.
+4. If the lockfile did not move to the version you asked for, check whether this
+ project holds back newly published packages (for example minimumReleaseAge in
+ bunfig.toml) and tell me the version it settled on and why.
+5. Run the project's complete production build.
+6. Tell me the registry version, the installed version from the lockfile, files
+ changed, and the final build result.
+
+Please make the changes and verify them. Thank you.
+```
+
+## The update keeps coming back after I update
+
+Some platforms hold a newly published package for a day before they will install it. Lovable is one: every project it generates carries a `bunfig.toml` with
+
+```toml
+[install]
+minimumReleaseAge = 86400
+```
+
+which tells Bun to skip any version published in the last 24 hours. Ask for one of those and the install reports success, `package.json` shows the new number, and the lockfile stays exactly where it was.
+
+This is a supply-chain guard, and a reasonable one — a package published minutes ago has had no time to be noticed if it was published by someone who should not have been able to. **We do not suggest turning it off.**
+
+To see what actually happened, open your lockfile (`bun.lock`, `package-lock.json`, `pnpm-lock.yaml`) and find `@patchstack/connect`. That number is the one that counts. If it is behind `package.json`, the release you asked for is still inside the hold window, and the install will pick it up on its own the next time the project is built after the window passes.
+
+Patchstack allows for this. The update notice in your dashboard and in the widget compares what you have installed against the newest release your package manager will actually accept, so it does not ask you to install something that is being held back — and when a newer release exists but is still held, the update screen says so rather than treating it as something you have failed to do.
+
+## The build broke after a config update
+
+Connect uses two config files with different jobs, and mixing them up breaks the build:
+
+| File | Commit it? | Holds |
+|------|-----------|-------|
+| `.patchstackrc.json` | Yes | The public `siteUuid` and non-secret settings such as `widget` |
+| `.patchstackrc.local.json` | No — gitignore it | `apiKey` only |
+
+The API key can also come from the `PATCHSTACK_API_KEY` environment variable. Never import it into browser code and never move it into the public config.
+
+```text
+Please diagnose and fix the Patchstack build after the config-file update.
+
+1. Update @patchstack/connect to the latest npm version first, even if it was
+ released within the last 24 hours.
+2. Search the entire project for .patchstackrc.json and
+ .patchstackrc.local.json, including build scripts and generated integration
+ code.
+3. Keep the public siteUuid and non-secret settings in committed
+ .patchstackrc.json.
+4. Keep apiKey only in gitignored .patchstackrc.local.json or
+ PATCHSTACK_API_KEY. Never import that secret into browser code or move it
+ into the public config.
+5. Fix any stale code path that still expects the credential only in
+ .patchstackrc.json, while preserving the site UUID.
+6. Run Patchstack status, scan, and the complete production build. Report the
+ root cause, exact files changed, and build output.
+
+Please complete and verify the fix. Thank you.
+```
+
+## I see two Patchstack Connectors
+
+Two shield buttons stacked in the corner, sometimes one opening the owner log-in and the other the report form, mean the widget script ran twice on that page. They often sit on exactly the same pixel, so the second one only shows when a panel opens or the layout shifts.
+
+The widget keeps **one floating launcher per page** on its own:
+
+- A second copy loaded by the **same document** is ignored, with a `[PatchstackWidget]` warning in the browser console.
+- A copy inside a page of **your own site that the shell shows in an `