Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions astro.config.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -145,6 +145,11 @@ export default defineConfig({
collapsed: true,
autogenerate: { directory: 'Patchstack App', collapsed: true },
},
{
label: 'Patchstack for JavaScript',
collapsed: true,
autogenerate: { directory: 'Patchstack for JS', collapsed: true },
},
{
label: 'Patchstack plugin',
collapsed: true,
Expand Down
34 changes: 33 additions & 1 deletion netlify.toml
Original file line number Diff line number Diff line change
Expand Up @@ -1061,4 +1061,36 @@
[[redirects]]
from = "/patchstack-plugin/patchstack-connector/how-to-install-on-joomla/"
to = "/patchstack-plugin/patchstack-connector/joomla-support-deprecated/"
status = 301
status = 301

# The JavaScript/Node.js section moved out of "Patchstack app" to its own
# top-level section, Patchstack for JavaScript, at /patchstack-for-js/.
[[redirects]]
from = "/patchstack-app/pulse/pulse-overview/"
to = "/patchstack-for-js/overview/"
status = 301

[[redirects]]
from = "/patchstack-app/pulse/packages/"
to = "/patchstack-for-js/packages/"
status = 301

[[redirects]]
from = "/patchstack-app/pulse/deploy-history/"
to = "/patchstack-for-js/deploy-history/"
status = 301

[[redirects]]
from = "/patchstack-app/pulse/attack-surface/"
to = "/patchstack-for-js/attack-surface/"
status = 301

[[redirects]]
from = "/patchstack-app/pulse/"
to = "/patchstack-for-js/overview/"
status = 301

[[redirects]]
from = "/patchstack-app/pulse/*"
to = "/patchstack-for-js/:splat"
status = 301
Original file line number Diff line number Diff line change
Expand Up @@ -281,4 +281,4 @@ check from step 5. Thank you.
- [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/) covers an assistant such as Claude Code refusing to run the install or `setup`.
- `npx @patchstack/connect guide` prints a project-aware checklist of what is present and what is missing.
- `npx @patchstack/connect status` re-prints the site UUID and dashboard link.
- [Pulse sites overview](/patchstack-app/pulse/pulse-overview/) explains what a connected site looks like in the Patchstack App, including how to tell whether it is reporting.
- [Patchstack for JavaScript overview](/patchstack-for-js/overview/) explains what a connected site looks like in the Patchstack App, including how to tell whether it is reporting.
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ On the this software subpage, you can also manage the software components of you
</Aside>

<Aside type="note" title="JavaScript and Node.js projects">
This page describes the plugins and themes of a WordPress site. For a JavaScript or Node.js app monitored with `@patchstack/connect`, the **Packages** tab lists its npm dependencies instead — see [Pulse packages](/patchstack-app/pulse/packages/).
This page describes the plugins and themes of a WordPress site. For a JavaScript or Node.js app monitored with `@patchstack/connect`, the **Packages** tab lists its npm dependencies instead — see [Packages in Patchstack for JavaScript](/patchstack-for-js/packages/).
</Aside>


Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/Patchstack App/Sites/adding-a-site.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,6 @@ Adding a site to Patchstack is relatively easy. Here is a simple guide on how to
8. Upload the plugin .zip file to your WordPress site by visiting /wp-admin > Plugins > Add New > Upload Plugin
9. Activate the plugin
</Steps>
**JavaScript and Node.js projects do not need this flow.** Pick **AI-assisted** instead and copy the message the app shows you into the assistant that built your website. The assistant installs [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/) and hands you back a link; paste it into the same panel to attach the site to your account. Tick **Connect this website to my account automatically** before copying and the message carries a one-day key for your account instead: the site is then created already attached to you, and the panel notices it by itself with nothing to paste. If the assistant still hands you a link (a message copied yesterday no longer connects), the paste field works as before. If the assistant refuses to run the install, see [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/). See [Pulse sites overview](/patchstack-app/pulse/pulse-overview/) for what those sites look like in the app.
**JavaScript and Node.js projects do not need this flow.** Pick **AI-assisted** instead and copy the message the app shows you into the assistant that built your website. The assistant installs [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/) and hands you back a link; paste it into the same panel to attach the site to your account. Tick **Connect this website to my account automatically** before copying and the message carries a one-day key for your account instead: the site is then created already attached to you, and the panel notices it by itself with nothing to paste. If the assistant still hands you a link (a message copied yesterday no longer connects), the paste field works as before. If the assistant refuses to run the install, see [My AI assistant blocked a Connect command](/getting-started/installing-patchstack/ai-assistant-blocked-a-command/). See [Patchstack for JavaScript overview](/patchstack-for-js/overview/) for what those sites look like in the app.

If you need further help, don't hesitate to reach out to us via live chat at the bottom right corner!
6 changes: 3 additions & 3 deletions src/content/docs/Patchstack App/Sites/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Retrying many sites runs in the background, so you can leave the page while it w

A site that stays unresponsive after a retry has usually lost its connection to Patchstack — check that the Patchstack plugin is still installed and activated, and see [this article](/faq-troubleshooting/firewall/app-is-showing-the-firewall-of-my-site-as-delayed/) for the usual causes. Being out of sync does not leave the site unprotected: the rules from its last successful sync stay in place and keep blocking.

Sites built with Pulse do not have a **Retry sync** option. They report their packages when they are next built, and nothing in the app can bring that build forward.
Sites monitored by Patchstack for JavaScript do not have a **Retry sync** option. They report their packages when they are next built, and nothing in the app can bring that build forward.

## Manage groups

Expand All @@ -66,7 +66,7 @@ Check [this article](/patchstack-app/sites/site-groups/) for details.

Most sites carry no label at all. A label appears when there is something about the site worth knowing before you read the rest of its row.

- **Not deployed** — Patchstack has never heard from this app: no build has reported its packages and no visitor's browser has checked in. If you know the app is live, the most likely reason is that the connector was not running in the build that went out — rebuild with `@patchstack/connect` installed and it will report on the next deploy. Only appears on sites built with Pulse.
- **Not deployed** — Patchstack has never heard from this app: no build has reported its packages and no visitor's browser has checked in. If you know the app is live, the most likely reason is that the connector was not running in the build that went out — rebuild with `@patchstack/connect` installed and it will report on the next deploy. Only appears on sites monitored by Patchstack for JS.
- **Connector deleted** — `@patchstack/connect` reported that it had been removed from the project. Nothing is watching the app's packages any more, and the site keeps using one of your site slots until you delete it here.
- **Not seen on live site** — nothing signalled a removal, but the live page no longer carries Patchstack. This is what a removal done through a prompt looks like: we can see the result without being told. Reinstall the connector, or delete the site to free its slot.
- **Build** — this site is a build or staging environment of another site, shown indented beneath it.
Expand All @@ -81,7 +81,7 @@ Two switches beside the platform filter narrow the list to the sites carrying th
- **Not deployed** — apps that have never reported in.
- **Connector deleted** — sites whose connector told us it had been removed. Sites labelled *Not seen on live site* are not included: that state is worked out from several signals rather than recorded, so there is no exact set to filter on.

Both can be on at once, in which case you get the sites that are both. The switches only appear on accounts with Pulse, since only apps deploy.
Both can be on at once, in which case you get the sites that are both. The switches only appear on accounts with Patchstack for JS, since only apps deploy.

## Adding a new site

Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Attack surface"
excerpt: "A map of a Pulse app's entry points, the inputs they read and where those inputs can reach — and what Patchstack does with it."
excerpt: "A map of the entry points of an app monitored by Patchstack for JavaScript, the inputs they read and where those inputs can reach — and what Patchstack does with it."
hidden: false
createdAt: "Thu Aug 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
updatedAt: "Thu Aug 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
Expand All @@ -11,7 +11,7 @@ sidebar:

The **Attack surface** tab describes the shape of your application: its entry points, the inputs each one reads, the sensitive operations those inputs can reach, and which of those links Patchstack could actually prove.

It is the input to two things you see elsewhere — the reachability verdicts on [Packages](/patchstack-app/pulse/packages/), and the protection rules Patchstack can pin to a specific place in your app rather than applying broadly.
It is the input to two things you see elsewhere — the reachability verdicts on [Packages](/patchstack-for-js/packages/), and the protection rules Patchstack can pin to a specific place in your app rather than applying broadly.

## Uploading a map

Expand All @@ -37,7 +37,7 @@ This is best-effort static analysis. It reports the surface it **detected**, and
- **Analysis coverage** and **analyser notes** record what could not be modelled — dynamic property access, computed `require`, reflection, and similar patterns that no amount of parsing resolves.
- A dependency inventory that could not be completed says **"This inventory is incomplete"** rather than quietly reporting fewer dependencies.

That last point is what keeps the [reachability verdicts](/patchstack-app/pulse/packages/#reachability) honest. "Not imported" is only claimed against an inventory known to be complete; otherwise the verdict is "unknown".
That last point is what keeps the [reachability verdicts](/patchstack-for-js/packages/#reachability) honest. "Not imported" is only claimed against an inventory known to be complete; otherwise the verdict is "unknown".

## Rule readiness and addressability

Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Deploy history"
excerpt: "A per-build changelog of what each deploy added, removed or moved in a Pulse app's dependencies."
excerpt: "A per-build changelog of what each deploy added, removed or moved in the dependencies of an app monitored by Patchstack for JavaScript."
hidden: false
createdAt: "Thu Aug 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
updatedAt: "Mon Oct 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time)"
Expand All @@ -13,7 +13,7 @@ sidebar:

You find it on the app's **Activity** tab.

The [Packages](/patchstack-app/pulse/packages/) tab answers "what is installed now". It cannot answer "when did this arrive" — which is the question that matters when an app's dependencies were chosen by an AI coding tool rather than picked deliberately.
The [Packages](/patchstack-for-js/packages/) tab answers "what is installed now". It cannot answer "when did this arrive" — which is the question that matters when an app's dependencies were chosen by an AI coding tool rather than picked deliberately.

## Reading a build

Expand Down Expand Up @@ -45,7 +45,7 @@ So a build annotated with a vulnerability is telling you something specific: thi

In production, the build serving traffic right now carries a **Live** badge. The newest build in the table is not automatically the live one, and the site header shows the same deploy status.

Where a newer build was scanned but never shipped, the tab says so directly — the table alone cannot, because a build that never went out looks exactly like one that did. See [when the site was last deployed](/patchstack-app/pulse/pulse-overview/#when-the-site-was-last-deployed).
Where a newer build was scanned but never shipped, the tab says so directly — the table alone cannot, because a build that never went out looks exactly like one that did. See [when the site was last deployed](/patchstack-for-js/overview/#when-the-site-was-last-deployed).

## Exporting

Expand Down
Loading