music-metadata (npm) has 6 known vulnerabilities, the worst rated HIGH. Upgrade to 11.16.0 or later to clear all of them. No malicious-package signal is recorded.
music-metadata's ASF parser (parseExtensionObject() in lib/asf/AsfParser.ts:112-158) enters an infinite loop when a sub-object inside the ASF Header Extension…
CyberXYZ does not call a package safe in absolute terms. It records 6 known vulnerabilities for music-metadata (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does music-metadata have known vulnerabilities?
Yes. CyberXYZ records 6 known vulnerabilities for music-metadata (npm), the worst rated HIGH. These include GHSA-v6c2-xwv6-8xf7, GHSA-8j4c-6x6g-rq3j, GHSA-5gfj-9q3v-qfp3, GHSA-jjpr-9cvf-cq55, GHSA-53v6-4h7p-p4gj.
Which version of music-metadata should I use?
11.16.0 or later clears every advisory recorded for music-metadata (npm). Check the release you pick before installing it.
How do I check music-metadata before installing?
Search music-metadata in CyberXYZ Check at https://cyberxyz.io/check?q=music-metadata. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 13:11 UTC. The most recent advisory here was published 2026-10-08. Updated continuously from NVD, GHSA, OSV and CNA feeds.