VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@backstage/integration: vulnerability history, versions and safety

@backstage/integration is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 102 releases, first recorded in Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 05 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @backstage/integration vulnerabilities

Vulert verdict on @backstage/integration 2.1.3 i

Updated on 23 Oct 2026

Good news: 2.1.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 89/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 2.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.1.3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 05 Mar 2026 i
  • Highest CVSS 2.7 i
  • With no published fix 0 i
  • Depended on by 1,129 packages i
  • Stars 34,659 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @backstage/integration, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.1.3 20 Oct 2026 none Apache-2.0 — Details →
2.1.3-next.1 06 Oct 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260928023907 28 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260927023342 27 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260926022852 26 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260925022940 25 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260924023050 24 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260923023054 23 Sep 2026 L1 Apache-2.0 Yes Details →
2.1.3-next.0 22 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260922023058 22 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260921023416 21 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260920023043 20 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260919022921 19 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260918023200 18 Sep 2026 L1 Apache-2.0 Yes Details →
2.1.2 15 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260909022715 09 Sep 2026 L1 Apache-2.0 Yes Details →
2.1.2-next.1 08 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260904022803 04 Sep 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260902024315 02 Sep 2026 L1 Apache-2.0 Yes Details →
2.1.2-next.0 01 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260829022506 29 Aug 2026 L1 Apache-2.0 Yes Details →
2.1.1 28 Aug 2026 none Apache-2.0 — Details →
2.1.0 18 Aug 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260818023149 18 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260817023522 17 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260816023538 16 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260815023121 15 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260814030239 14 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260813030414 13 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260812030228 12 Aug 2026 L1 Apache-2.0 Yes Details →
2.1.0-next.1 11 Aug 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260811025108 11 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260810025551 10 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260809025047 09 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260808024620 08 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260807031145 07 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260806031410 06 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260805031525 05 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260804031620 04 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260803031511 03 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260802031400 02 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260801031325 01 Aug 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260731031617 31 Jul 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260730031533 30 Jul 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260729031221 29 Jul 2026 L1 Apache-2.0 Yes Details →
2.1.0-next.0 28 Jul 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260728031313 28 Jul 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260727031641 27 Jul 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260726031454 26 Jul 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260725031401 25 Jul 2026 L1 Apache-2.0 Yes Details →
2.0.3 16 Jun 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260616032439 16 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260615032517 15 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260614032343 14 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260613032133 13 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260612032440 12 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260611032059 11 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260610032156 10 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260609032118 09 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260608032505 08 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260607032244 07 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260606031950 06 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260605032312 05 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260604032348 04 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260603032450 03 Jun 2026 L1 Apache-2.0 Yes Details →
2.0.3-next.1 02 Jun 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260602032639 02 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260601032430 01 Jun 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260531032321 31 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260530032139 30 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260529032432 29 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260528032551 28 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260527032423 27 May 2026 L1 Apache-2.0 Yes Details →
2.0.3-next.0 26 May 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260526032421 26 May 2026 L1 Apache-2.0 Yes Details →
2.0.2 19 May 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260519032312 19 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260518032303 18 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260517032033 17 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260516032040 16 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260515032213 15 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260514032146 14 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260513032245 13 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260512032235 12 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260511032212 11 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260510031943 10 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260509032050 09 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260508031713 08 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260507032228 07 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260506032142 06 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260505210529 05 May 2026 L1 Apache-2.0 Yes Details →
2.0.2-next.1 05 May 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260504032045 04 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260503031939 03 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260502031749 02 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260501031939 01 May 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260430032050 30 Apr 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260429031911 29 Apr 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260428031946 28 Apr 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260427031952 27 Apr 2026 L1 Apache-2.0 Yes Details →
0.0.0-nightly-20260426031943 26 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260425031642 25 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260424031925 24 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260423031659 23 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260422031853 22 Apr 2026 L1 — Yes Details →
2.0.2-next.0 21 Apr 2026 none — — Details →
0.0.0-nightly-20260421031647 21 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260420031813 20 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260419031625 19 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260418031715 18 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260417031854 17 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260416031834 16 Apr 2026 L1 — Yes Details →
2.0.1 14 Apr 2026 none — — Details →
0.0.0-nightly-20260414031820 14 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260413031937 13 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260411031533 11 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260410031841 10 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260409031723 09 Apr 2026 L1 — Yes Details →
0.0.0-nightly-20260408031702 08 Apr 2026 L1 — Yes Details →
2.0.1-next.0 07 Apr 2026 none — — Details →

The newest 120 of 1,348 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @backstage/integration

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-29185: Backstage SCM Integration Path Traversal Vulnerability 2.7 low 1.20.1 05 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @backstage/integration

Is @backstage/integration safe to use?

Vulert records 1 vulnerabilities for @backstage/integration in npm: 0 critical, 0 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @backstage/integration's Vulert package health score?

Vulert scores @backstage/integration 89/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @backstage/integration affected?

No. 2.1.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @backstage/integration have?

1 vulnerability is recorded for @backstage/integration in the npm ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @backstage/integration vulnerabilities disclosed?

1 vulnerability was recorded for @backstage/integration in the last 12 months, and the oldest entry in this database dates to 05 Mar 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @backstage/integration are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @backstage/integration for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @backstage/integration version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.