ring-device-settings-library@30.0.0

package.json declares a dependency whose key equals the package's own name (ring-device-settings-library) and whose value is a raw HTTPS URL pointing at an off-registry host: https://repo.securityctrl.com/ring-device-settings-library. On `npm install`, npm resolves that URL rather than a registry version range and installs whatever bytes the host returns, running any lifecycle scripts contained in the fetched artifact. There is no version pin, no integrity hash, and no signature check, and the host is unrelated to any npm registry. The shipped package contents are otherwise an inert placeholder, so the manifest line is the entire installed surface: whoever controls repo.securityctrl.com controls the code that executes on the installer's machine on every install. The self-referential dependency name, combined with the implausibly high version (45.0.0), is also a dependency-confusion shape that can win resolution against an internally-named package.