@backstage/cli-common (npm) has 1 known vulnerability, the worst rated MODERATE. Upgrade to 0.1.17 or later to clear it. No malicious-package signal is recorded.
The resolveSafeChildPath utility function in @backstage/backend-plugin-api, which is used to prevent path traversal attacks, failed to properly validate…
// questionsIs @backstage/cli-common safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for @backstage/cli-common (npm), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does @backstage/cli-common have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for @backstage/cli-common (npm), the worst rated MODERATE. They are GHSA-2p49-45hj-7mc9.
Which version of @backstage/cli-common should I use?
0.1.17 or later clears every advisory recorded for @backstage/cli-common (npm). Check the release you pick before installing it.
How do I check @backstage/cli-common before installing?
Search @backstage/cli-common in CyberXYZ Check at https://cyberxyz.io/check?q=%40backstage%2Fcli-common. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 03:11 UTC. The most recent advisory here was published 2026-01-21. Updated continuously from NVD, GHSA, OSV and CNA feeds.