--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2a6c4f2b94932e8bcb68c0a146d536b7e3a00d48041aa5a6fc9edf9f82ae5244) package.json declares a dependency whose value is a bare HTTPS URL (https://repo.securityctrl.com/npm-extension) rather than a registry version range. On npm install, npm fetches whatever tarball that host returns and executes any lifecycle scripts inside it, unpinned and without integrity verification. The dependency key equals the package's own name, producing a dependency-confusion shape in which resolution is forced through the off-registry host. The shipped index.js is an inert stub, so the manifest line is the entire published payload — the fetched third-party code is what actually runs on installer machines.