0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
librastandardlib
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting librastandardlib, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-15538 | Unknown | Malicious code in librastandardlib (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (519c28eb8d9df0a16d93e1b1c486f1ad4a9092a9bf958aed56f273cfe1fcfc14) package.json at line 11 declares a dependency whose key equals the package's own name (librastandardlib) and whose value is an off-registry HTTPS URL (https://repo.securityctrl.com/librastandardlib) instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, running any lifecycle scripts inside with no version pin and no integrity check. The implausibly hig |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (519c28eb8d9df0a16d93e1b1c486f1ad4a9092a9bf958aed56f273cfe1fcfc14) package.json at line 11 declares a dependency whose key equals the package's own name (librastandardlib) and whose value is an off-registry HTTPS URL (https://repo.securityctrl.com/librastandardlib) instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, running any lifecycle scripts inside with no version pin and no integrity check. The implausibly hig