Multiple vulnerabilities were discovered in tempo/charge and tempo/session which allowed for undesirable behaviors, including:
Full advisory text at GitHub advisory.
npm package report
Is mppx safe?
mppx (npm) has 5 known vulnerabilities, the worst rated CRITICAL. Upgrade to 0.8.2 or later to clear all of them. No malicious-package signal is recorded.
// ai model usage
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
cvss
9.0
critical
severity band, no base score published
epss
not scored
chance of exploitation in 30 days
xyz score
4.6
medium
CyberXYZ composite out of 10
fig. 01 — GHSA-8x4m-qw58-3pcx, the advisory selected below
// 5 advisories
Is mppx safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 5 known vulnerabilities for mppx (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does mppx have known vulnerabilities?
Yes. CyberXYZ records 5 known vulnerabilities for mppx (npm), the worst rated CRITICAL. They are GHSA-8x4m-qw58-3pcx, GHSA-mv9j-8jvg-j8mr, GHSA-vc9j-9wph-qghj, GHSA-727h-3vm5-qwq6, GHSA-8mhj-rffc-rcvw.
Which version of mppx should I use?
0.8.2 or later clears every advisory recorded for mppx (npm). Check the release you pick before installing it.
How do I check mppx before installing?
Search mppx in CyberXYZ Check at https://cyberxyz.io/check?q=mppx. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:14 UTC. The most recent advisory here was published 2026-09-22. Updated continuously from NVD, GHSA, OSV and CNA feeds.