nx-app@9999.0.0-security-test

package.json declares its own name `nx-app` as a dependency whose value is a raw HTTPS URL (`https://repo.securityctrl.com/nx-app`) rather than a semver range against the npm registry. On `npm install`, npm fetches a tarball from that URL and runs any lifecycle scripts it contains, with no version pin, no integrity hash, and no signature check. Whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency key (matching the package's own name) is a dependency-confusion shape that forces resolution to the off-registry URL even when a registry-hosted `nx-app` exists, and the shipped in-tree source is an inert stub so the manifest URL is the sole payload delivery vector.