From c18540c3e49fc5743779535353e974a174be4091 Mon Sep 17 00:00:00 2001 From: Dave Jong Date: Wed, 30 Sep 2026 20:10:26 +0200 Subject: [PATCH] Explain JavaScript report mitigation status --- src/content/docs/Patchstack App/Reports/reports-overview.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/content/docs/Patchstack App/Reports/reports-overview.md b/src/content/docs/Patchstack App/Reports/reports-overview.md index d08abcb5..8b379bbd 100644 --- a/src/content/docs/Patchstack App/Reports/reports-overview.md +++ b/src/content/docs/Patchstack App/Reports/reports-overview.md @@ -29,3 +29,9 @@ On the **Reports** page you can view and download all the previously generated P To download a report, click **Download** at the right end of its row. To view and manage your scheduled reports, click on **Scheduled reports** tab. Note that report scheduling is for the Developer and Enterprise plan users. + +## Mitigation status for JavaScript applications + +A mitigation being available for a vulnerability does not mean it has been delivered to every affected application. JavaScript application reports mark a vulnerability as mitigated when a blocking rule bundle covering it has been delivered to that application. A rule that is only available, or is used in detect-only mode, does not establish that status. + +This status records delivery of protection, not evidence that an attack occurred or was blocked. Updating the affected package to a fixed version is still recommended.