Attack Navigator solution with vulnerable modules

As a tool for security purposes logging above look very vulnerable for usage in production.
Am I doing something incorrect of is the solution using older vulnerable components?

Install is today on current Kali VM with node v20.19.2 and npm 9.2.0 after git clone of https://github.com/mitre-attack/attack-navigator.git

~/Documents/MITRE_Attack/navigator/nav-app]
└─$ npm install

npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated read-package-json@7.0.1: This package is no longer supported. Please use @npmcli/package-json instead.
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated tslint@6.1.3: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.

added 1233 packages, and audited 1234 packages in 22s
20 vulnerabilities (1 low, 14 moderate, 5 high)

Start in the nav-app directory by running npm audit and reviewing the dependency manifests against the advisories reported during npm install. The issue does not identify which packages should change, so confirm the affected components and compatibility requirements before defining completion; done should include verification that the reported vulnerabilities are addressed.