Vulnerability Database · npm · update-section · Version
update-section 0.2.0
No vulnerabilities in this database cover 0.2.0.
Every vulnerability Vulert holds for update-section 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 07 Mar 2014
Licence MIT
Also known from other sources 0
Newer releases 8
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
update-section 0.2.0 vulnerabilities
No vulnerability in the Vulert database covers update-section 0.2.0. See the versions that are affected →
Looking for another version, or everything Vulert holds for update-section?
Questions
About update-section 0.2.0
Is update-section 0.2.0 vulnerable?
No. No vulnerability in the Vulert database covers update-section 0.2.0. Every vulnerability Vulert holds for update-section 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.2.0 the latest release of update-section?
No. 0.2.0 was published 07 Mar 2014, 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 update-section for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the update-section version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.