no-for-of-loops
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting no-for-of-loops, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-14268 | Unknown | Malicious code in no-for-of-loops (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (08feaf6617a902e503390720b41d226364ba3bc125d298eb296a2d3e30d5b6d5) package.json declares no-for-of-loops as its own dependency and devDependency, with the source pointed at http://pack.nppacks.com/npm/no-for-of-loops instead of the npm registry. On `npm install`, npm fetches a tarball from this host over unauthenticated plain HTTP with no integrity hash, and installs its contents into the consumer's node_modules. The domain operator can serve arbitrary, mutable bytes on each fetch, meaning any code shipped |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (08feaf6617a902e503390720b41d226364ba3bc125d298eb296a2d3e30d5b6d5) package.json declares no-for-of-loops as its own dependency and devDependency, with the source pointed at http://pack.nppacks.com/npm/no-for-of-loops instead of the npm registry. On `npm install`, npm fetches a tarball from this host over unauthenticated plain HTTP with no integrity hash, and installs its contents into the consumer's node_modules. The domain operator can serve arbitrary, mutable bytes on each fetch, meaning any code shipped