npm package report

Is @backstage/integration safe?

1 known vulnerability, worst severity LOW.

cvss
2.7

how bad it is if exploited, out of 10

epss
0.30%

chance of exploitation in the next 30 days

xyz score
1.8

CyberXYZ composite, out of 10

fig. 01 — GHSA-95v5-prp4-5gv5, the advisory selected below

// advisories

GHSA-95v5-prp4-5gv5

LOWCVE-2026-29185

A vulnerability in the SCM URL parsing used by Backstage integrations allowed path traversal sequences in encoded form to be included in file paths. When these URLs were processed by integration functions that construct API URLs, the traversal segments could redirect requests to unintended SCM provider API endpoints using the configured server-side integration credentials.

Affected
<= 1.20.0
Fixed in
1.20.1
Weakness
CWE-22
Published
2026-03-05
Source
github

GHSANVDMITREreference

// dependencies

10 direct, 4 carrying known advisories, worst CRITICAL

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 03:27 UTC. The most recent advisory here was published 2026-03-05. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @backstage/integration safe? npm package security report | CyberXYZ