From e71ab1b4306b84d4cae99e3b5212d7d047d4da8a Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 29 Sep 2026 07:27:28 +0000 Subject: [PATCH 1/2] Rename Pulse to Patchstack for JavaScript and give it its own section Pulse is an internal product name. Replace every mention in the docs with "Patchstack for JavaScript" (formal/first mention, titles, sidebar) or "Patchstack for JS" (repeated mentions in running text). Move the section out of "Patchstack app" into its own top-level sidebar group and URL path (/patchstack-for-js/), rename pulse-overview to overview, update internal links, and add 301 redirects from the old /patchstack-app/pulse/ URLs in netlify.toml. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_01Ustuxckjeo5Gkofas6tPXQ --- astro.config.mjs | 5 +++ netlify.toml | 33 ++++++++++++++++++- ...oubleshooting-javascript-node-projects.mdx | 2 +- .../Site Dashboard/site-software.mdx | 2 +- .../Patchstack App/Sites/adding-a-site.mdx | 2 +- .../docs/Patchstack App/Sites/overview.md | 6 ++-- .../attack-surface.md | 6 ++-- .../deploy-history.md | 6 ++-- .../overview.md} | 24 +++++++------- .../Pulse => Patchstack for JS}/packages.md | 6 ++-- 10 files changed, 64 insertions(+), 28 deletions(-) rename src/content/docs/{Patchstack App/Pulse => Patchstack for JS}/attack-surface.md (87%) rename src/content/docs/{Patchstack App/Pulse => Patchstack for JS}/deploy-history.md (90%) rename src/content/docs/{Patchstack App/Pulse/pulse-overview.md => Patchstack for JS/overview.md} (87%) rename src/content/docs/{Patchstack App/Pulse => Patchstack for JS}/packages.md (94%) diff --git a/astro.config.mjs b/astro.config.mjs index fd83287c..06cd665b 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -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, diff --git a/netlify.toml b/netlify.toml index 7c2c03ed..3869f9cd 100644 --- a/netlify.toml +++ b/netlify.toml @@ -1061,4 +1061,35 @@ [[redirects]] from = "/patchstack-plugin/patchstack-connector/how-to-install-on-joomla/" to = "/patchstack-plugin/patchstack-connector/joomla-support-deprecated/" - status = 301 \ No newline at end of file + status = 301 +# Pulse was renamed to Patchstack for JavaScript and moved out of "Patchstack app" +# into its own top-level section. +[[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 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 index 90213d68..efb87104 100644 --- 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 @@ -278,4 +278,4 @@ check from step 5. Thank you. - `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. diff --git a/src/content/docs/Patchstack App/Site Dashboard/site-software.mdx b/src/content/docs/Patchstack App/Site Dashboard/site-software.mdx index 5331d848..c2dcf363 100644 --- a/src/content/docs/Patchstack App/Site Dashboard/site-software.mdx +++ b/src/content/docs/Patchstack App/Site Dashboard/site-software.mdx @@ -21,7 +21,7 @@ On the this software subpage, you can also manage the software components of you diff --git a/src/content/docs/Patchstack App/Sites/adding-a-site.mdx b/src/content/docs/Patchstack App/Sites/adding-a-site.mdx index 72a581fd..3a736a33 100644 --- a/src/content/docs/Patchstack App/Sites/adding-a-site.mdx +++ b/src/content/docs/Patchstack App/Sites/adding-a-site.mdx @@ -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 -**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. 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. 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! \ No newline at end of file diff --git a/src/content/docs/Patchstack App/Sites/overview.md b/src/content/docs/Patchstack App/Sites/overview.md index 04e3e7a8..dfe8e8b3 100644 --- a/src/content/docs/Patchstack App/Sites/overview.md +++ b/src/content/docs/Patchstack App/Sites/overview.md @@ -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 @@ -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. @@ -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 diff --git a/src/content/docs/Patchstack App/Pulse/attack-surface.md b/src/content/docs/Patchstack for JS/attack-surface.md similarity index 87% rename from src/content/docs/Patchstack App/Pulse/attack-surface.md rename to src/content/docs/Patchstack for JS/attack-surface.md index d18e4695..989df037 100644 --- a/src/content/docs/Patchstack App/Pulse/attack-surface.md +++ b/src/content/docs/Patchstack for JS/attack-surface.md @@ -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)" @@ -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 @@ -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 diff --git a/src/content/docs/Patchstack App/Pulse/deploy-history.md b/src/content/docs/Patchstack for JS/deploy-history.md similarity index 90% rename from src/content/docs/Patchstack App/Pulse/deploy-history.md rename to src/content/docs/Patchstack for JS/deploy-history.md index b923a746..3ef451f4 100644 --- a/src/content/docs/Patchstack App/Pulse/deploy-history.md +++ b/src/content/docs/Patchstack for JS/deploy-history.md @@ -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: "Thu Aug 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time)" @@ -11,7 +11,7 @@ sidebar: **Deploy history** turns the manifests your builds report into a changelog: for each build, what it added, what it removed, what changed version, and whether anything it brought in was already known to be vulnerable. -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 @@ -38,7 +38,7 @@ So a build annotated with a vulnerability is telling you something specific: thi The page header carries the same deploy status as the site header: which of the builds below is the one serving traffic right now. The list is a record of builds, and the newest entry in it is not automatically the live one. -Where a newer build was scanned but never shipped, the page says so directly — the timeline 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 page says so directly — the timeline 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). The status describes production only, so it is hidden while you are looking at the sandbox lineage. diff --git a/src/content/docs/Patchstack App/Pulse/pulse-overview.md b/src/content/docs/Patchstack for JS/overview.md similarity index 87% rename from src/content/docs/Patchstack App/Pulse/pulse-overview.md rename to src/content/docs/Patchstack for JS/overview.md index 2f077010..963388b2 100644 --- a/src/content/docs/Patchstack App/Pulse/pulse-overview.md +++ b/src/content/docs/Patchstack for JS/overview.md @@ -1,17 +1,17 @@ --- -title: "Pulse sites overview" +title: "Patchstack for JavaScript overview" excerpt: "How JavaScript and Node.js apps appear in the Patchstack App, and how they differ from WordPress sites." 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)" sidebar: order: 1 - label: "Pulse overview" + label: "Overview" --- -**Pulse** is how Patchstack monitors JavaScript and Node.js applications. Where a WordPress site is monitored by the Patchstack plugin running inside WordPress, a Pulse site is monitored by [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/), an npm package that runs during your build. +**Patchstack for JavaScript** is how Patchstack monitors JavaScript and Node.js applications. Where a WordPress site is monitored by the Patchstack plugin running inside WordPress, a Patchstack for JS site is monitored by [`@patchstack/connect`](/getting-started/installing-patchstack/installing-on-javascript-node-projects/), an npm package that runs during your build. -That difference in mechanism is why a Pulse site's dashboard does not look like a WordPress site's. This page explains what you get instead. +That difference in mechanism is why the dashboard of a Patchstack for JS site does not look like a WordPress site's. This page explains what you get instead. ## Getting a site into the dashboard @@ -25,18 +25,18 @@ An unclaimed site that nobody ever claims is cleaned up after a reminder period, ## What the tabs show -A Pulse site gets a smaller set of tabs than a WordPress site, because several of them describe things only WordPress has. +A Patchstack for JS site gets a smaller set of tabs than a WordPress site, because several of them describe things only WordPress has. | Tab | What it tells you | |-----|-------------------| | **Overview** | Whether protection is active, the vulnerabilities found in this app's dependencies, and how many packages are installed. | -| **[Packages](/patchstack-app/pulse/packages/)** | Every npm package the app has installed, which are vulnerable, and how close each vulnerability is to code the app actually runs. | -| **[Deploy history](/patchstack-app/pulse/deploy-history/)** | What each build changed about the installed packages, and whether it brought in anything already known to be vulnerable. | -| **[Attack surface](/patchstack-app/pulse/attack-surface/)** | The app's entry points, the inputs they read, and where those inputs can reach. Populated only if you run `map --upload`. | +| **[Packages](/patchstack-for-js/packages/)** | Every npm package the app has installed, which are vulnerable, and how close each vulnerability is to code the app actually runs. | +| **[Deploy history](/patchstack-for-js/deploy-history/)** | What each build changed about the installed packages, and whether it brought in anything already known to be vulnerable. | +| **[Attack surface](/patchstack-for-js/attack-surface/)** | The app's entry points, the inputs they read, and where those inputs can reach. Populated only if you run `map --upload`. | | **Protection** | Rules protecting the app's vulnerable packages at runtime, and what they have matched. | | **Settings** | Site name, group, and removal. | -Hardening, Activity, and Users are WordPress-only and do not appear. Reports currently cover WordPress sites; a Pulse site's security-report page hides the sections that do not apply. +Hardening, Activity, and Users are WordPress-only and do not appear. Reports currently cover WordPress sites; the security-report page of a Patchstack for JS site hides the sections that do not apply. ## Application status @@ -74,7 +74,7 @@ A deploy that was scanned before it went out, but not by the build that shipped The site header shows **Last scan** — when Connect last sent a dependency manifest. This moves when you build or install dependencies, and it is how old the package data on the page is. -Hover it and Patchstack also tells you when it last had any contact with the site, whenever that is much more recent than the scan. The two differ because Patchstack learns about a Pulse site from more than one signal. Connect reports at build time. The Patchstack Connector in your served pages checks in when a visitor loads the site, which is how Patchstack knows the app is actually live and running the build you last reported. Patchstack also re-fetches the published page on a schedule to confirm the widget is still there. +Hover it and Patchstack also tells you when it last had any contact with the site, whenever that is much more recent than the scan. The two differ because Patchstack learns about a Patchstack for JS site from more than one signal. Connect reports at build time. The Patchstack Connector in your served pages checks in when a visitor loads the site, which is how Patchstack knows the app is actually live and running the build you last reported. Patchstack also re-fetches the published page on a schedule to confirm the widget is still there. An app that builds rarely but gets traffic will show an old scan time and recent contact. That is normal, not a fault. @@ -84,7 +84,7 @@ That happens more often than you might expect. Patchstack's re-fetch reads the H ## When the site was last deployed -Beside those timestamps, a Pulse site's header carries a **deploy status**. Building and deploying are separate events, and Patchstack tracks them separately. +Beside those timestamps, the header of a Patchstack for JS site carries a **deploy status**. Building and deploying are separate events, and Patchstack tracks them separately. Connect's `mark-build` step stamps each build's fingerprint into the HTML it publishes. Patchstack reads that fingerprint back off the live site — from the widget when a visitor loads a page, and from its own scheduled fetch of the published page — and compares it against the builds you have reported. That comparison is what the status says out loud: @@ -118,7 +118,7 @@ Reporting your dependencies tells you what is vulnerable. The **runtime guard** The guard fetches the rules Patchstack generated for the vulnerable packages this site actually has, and reports every rule that matched, including matches it allowed through. A new rule starts in detect-only mode and begins blocking once the evidence justifies it, so protection does not arrive as a wall of false positives. -Runtime protection on a production Pulse app is a paid feature. See [The runtime guard](/getting-started/installing-patchstack/installing-on-javascript-node-projects/) for what `setup` installs and which frameworks are wired automatically. +Runtime protection for a production app on Patchstack for JS is a paid feature. See [The runtime guard](/getting-started/installing-patchstack/installing-on-javascript-node-projects/) for what `setup` installs and which frameworks are wired automatically. ### When protection shows as Active diff --git a/src/content/docs/Patchstack App/Pulse/packages.md b/src/content/docs/Patchstack for JS/packages.md similarity index 94% rename from src/content/docs/Patchstack App/Pulse/packages.md rename to src/content/docs/Patchstack for JS/packages.md index 110fee3f..83f2d21e 100644 --- a/src/content/docs/Patchstack App/Pulse/packages.md +++ b/src/content/docs/Patchstack for JS/packages.md @@ -1,6 +1,6 @@ --- title: "Packages" -excerpt: "The npm packages a Pulse app has installed, which are vulnerable, and how close each vulnerability is to code the app runs." +excerpt: "The npm packages an app monitored by Patchstack for JavaScript has installed, which are vulnerable, and how close each vulnerability is to code the app runs." 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)" @@ -9,7 +9,7 @@ sidebar: label: "Packages" --- -The **Packages** tab lists every npm package the app has installed, with its version and whether Patchstack knows of a vulnerability in it. It answers "what is installed right now" — for "when did this arrive", see [Deploy history](/patchstack-app/pulse/deploy-history/). +The **Packages** tab lists every npm package the app has installed, with its version and whether Patchstack knows of a vulnerability in it. It answers "what is installed right now" — for "when did this arrive", see [Deploy history](/patchstack-for-js/deploy-history/). The list comes from the dependency manifest the connector sends during your build, so it includes transitive dependencies, not only the ones named in your `package.json`. @@ -19,7 +19,7 @@ Click the **Package**, **Vulnerabilities** or **Version** header to sort the lis A modern app installs hundreds of packages it never calls. A vulnerability in one of those is not the same problem as a vulnerability in a package your request handlers use directly, and treating them alike buries the second under the first. -If you have uploaded an [attack-surface map](/patchstack-app/pulse/attack-surface/), Patchstack labels each finding with how close it is to code your app actually runs: +If you have uploaded an [attack-surface map](/patchstack-for-js/attack-surface/), Patchstack labels each finding with how close it is to code your app actually runs: | Verdict | What it means | |---------|---------------| From 28e0c510d42a6d3b6fbcd92e165cf9c0cf292f4a Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 30 Sep 2026 15:46:01 +0000 Subject: [PATCH 2/2] Tidy the redirect comment in netlify.toml Separate the new redirect block from the previous rule with a blank line and describe the move without the old internal product name. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_01Ustuxckjeo5Gkofas6tPXQ --- netlify.toml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/netlify.toml b/netlify.toml index 3869f9cd..3f421eff 100644 --- a/netlify.toml +++ b/netlify.toml @@ -1062,8 +1062,9 @@ from = "/patchstack-plugin/patchstack-connector/how-to-install-on-joomla/" to = "/patchstack-plugin/patchstack-connector/joomla-support-deprecated/" status = 301 -# Pulse was renamed to Patchstack for JavaScript and moved out of "Patchstack app" -# into its own top-level section. + +# 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/"