VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@dependencytrack/frontend: vulnerability history, versions and safety

@dependencytrack/frontend is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 7 releases, from Oct 2022 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
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 17 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @dependencytrack/frontend vulnerabilities

Vulert verdict on @dependencytrack/frontend 1.0.0-alpha.9 i

Updated on 23 Oct 2026

Action needed: 1.0.0-alpha.9 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 59/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.0.0-alpha.9 — affected i
  • Vulnerabilities on record 2 over 3 years · 1 in the last year i
  • Latest disclosure 17 Nov 2025 i
  • Highest CVSS 5.4 i
  • With no published fix 0 i
  • Stars 182 i
  • OpenSSF scorecard 5/10 i
  • Last release 81 months ago 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 @dependencytrack/frontend, 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
1.0.0-alpha.9 14 Jan 2020 M1 Apache-2.0 Yes Details →
1.0.0-alpha.8 13 Jan 2020 M1 Apache-2.0 Yes Details →
1.0.0-alpha.7 12 Jan 2020 M1 Apache-2.0 Yes Details →
1.0.0-alpha.6 11 Jan 2020 M1 Apache-2.0 Yes Details →
1.0.0-alpha.5 11 Jan 2020 M1 Apache-2.0 Yes Details →
1.0.0-alpha.4 09 Jan 2020 M1 Apache-2.0 Yes Details →
1.0.0-alpha.3 08 Jan 2020 M1 Apache-2.0 Yes Details →

All 7 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for @dependencytrack/frontend

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-39350: Persistent Cross-Site-Scripting in @dependencytrack/frontend 5.4 medium 4.6.1 25 Oct 2022
CVE-2025-64758: @dependencytrack/frontend Persistent Cross-Site Scripting Vulnerability 4.8 medium 4.13.6 17 Nov 2025

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 @dependencytrack/frontend

Is @dependencytrack/frontend safe to use?

Vulert records 2 vulnerabilities for @dependencytrack/frontend in npm: 0 critical, 0 high, 2 medium and 0 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 @dependencytrack/frontend's Vulert package health score?

Vulert scores @dependencytrack/frontend 59/100, which reads as usable, but worth attention. 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 @dependencytrack/frontend affected?

Yes. 1.0.0-alpha.9, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of @dependencytrack/frontend should I use?

1.0.0-alpha.9 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @dependencytrack/frontend have?

2 vulnerabilities are recorded for @dependencytrack/frontend in the npm ecosystem: 0 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @dependencytrack/frontend vulnerabilities disclosed?

1 vulnerability was recorded for @dependencytrack/frontend in the last 12 months, and the oldest entry in this database dates to 25 Oct 2022. 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 @dependencytrack/frontend 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 @dependencytrack/frontend for upcoming vulnerabilities?

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