Vulnerability Database · npm · specificity · Version
specificity 0.3.2
No vulnerabilities in this database cover 0.3.2.
Every vulnerability Vulert holds for specificity 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 26 Sep 2017
Licence MIT
Also known from other sources 0
Newer releases 16
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
specificity 0.3.2 vulnerabilities
No vulnerability in the Vulert database covers specificity 0.3.2. See the versions that are affected →
Looking for another version, or everything Vulert holds for specificity?
Questions
About specificity 0.3.2
Is specificity 0.3.2 vulnerable?
No. No vulnerability in the Vulert database covers specificity 0.3.2. Every vulnerability Vulert holds for specificity 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.3.2 the latest release of specificity?
No. 0.3.2 was published 26 Sep 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor specificity for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the specificity version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.