Vulnerability Database · npm · react-component-taggers · Version
react-component-taggers 0.1.6
0.1.6 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.1.8.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 23 Sep 2025
Licence MIT
Also known from other sources 0
Newer releases 9
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
react-component-taggers 0.1.6 vulnerabilities
1 vulnerability cover react-component-taggers 0.1.6. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Malicious Code Vulnerability in react-component-taggers Package | N/A critical | No fix published | 24 Nov 2025 |
Looking for another version, or everything Vulert holds for react-component-taggers?
Questions
About react-component-taggers 0.1.6
Is react-component-taggers 0.1.6 vulnerable?
Yes. 1 vulnerability in the Vulert database cover react-component-taggers 0.1.6: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 0.1.8, and each entry above names the fixed version to move to.
Which version of react-component-taggers should I use instead of 0.1.6?
0.1.8 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.1.6 the latest release of react-component-taggers?
No. 0.1.6 was published 23 Sep 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
What does a malicious-package vulnerability mean?
It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.
How do I monitor react-component-taggers for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the react-component-taggers version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.