Vulnerability Database · npm · convert-string · Version
convert-string 0.1.0
No vulnerabilities in this database cover 0.1.0.
Every vulnerability Vulert holds for convert-string 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 21 Nov 2013
Status latest release
Also known from other sources 0
Newer releases 1
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
convert-string 0.1.0 vulnerabilities
No vulnerability in the Vulert database covers convert-string 0.1.0. See the versions that are affected →
Looking for another version, or everything Vulert holds for convert-string?
Questions
About convert-string 0.1.0
Is convert-string 0.1.0 vulnerable?
No. No vulnerability in the Vulert database covers convert-string 0.1.0. Every vulnerability Vulert holds for convert-string 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 0.1.0 the latest release of convert-string?
Yes. 0.1.0 is the current release, published 21 Nov 2013. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor convert-string for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the convert-string version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.