risk-detection
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 risk-detection, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-17563 | Unknown | Malicious code in risk-detection (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4b74a904a25687bbc34ad321ea019c5083f9a3651457750ed36207a209798f77) package.json declares a dependency `ltidisafe` whose source is an off-registry tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.1.tgz`) rather than a semver range on the npm registry. The shipped `index.js` is an empty stub (`module.exports = {}`), so the manifest URL is the entire install-time surface. On `npm install`, npm fetches whatever bytes that URL returns — unpinned, no integrity hash, no registry publishe |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4b74a904a25687bbc34ad321ea019c5083f9a3651457750ed36207a209798f77) package.json declares a dependency `ltidisafe` whose source is an off-registry tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.1.tgz`) rather than a semver range on the npm registry. The shipped `index.js` is an empty stub (`module.exports = {}`), so the manifest URL is the entire install-time surface. On `npm install`, npm fetches whatever bytes that URL returns — unpinned, no integrity hash, no registry publishe