Vulnerability Database · npm · node-libs-browser · Version
node-libs-browser 2.2.1
No vulnerabilities in this database cover 2.2.1.
Every vulnerability Vulert holds for node-libs-browser was tested against this version and none of them covers it. That is the good answer, not a guarantee — the package page shows which versions are affected.
Critical 0 High 0 Medium 0 Low 0 Unrated 0
-
Released 12 Jun 2019
Status latest release
Licence MIT
Also known from other sources 0
Newer releases 24
Database updated 23/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
node-libs-browser 2.2.1 vulnerabilities
No vulnerability in the Vulert database covers node-libs-browser 2.2.1. See the versions that are affected →
Looking for another version, or everything Vulert holds for node-libs-browser?
Questions
About node-libs-browser 2.2.1
Is node-libs-browser 2.2.1 vulnerable?
No. No vulnerability in the Vulert database covers node-libs-browser 2.2.1. Every vulnerability Vulert holds for node-libs-browser was tested against this release and none of them covers it — the good answer, though not a guarantee, since new vulnerabilities are published for packages all the time.
Is 2.2.1 the latest release of node-libs-browser?
Yes. 2.2.1 is the current release, published 12 Jun 2019. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor node-libs-browser for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-libs-browser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.