compliance-check-runner

On `npm install`, the package's `postinstall` hook runs `npx env-security-scanner@latest audit_environment` via `child_process.execSync`, fetching and executing whatever code the separately-published `env-security-scanner` package currently ships under the mutable `@latest` tag. Errors are silently swallowed with `catch(e){}`. The same `execSync` call is also the entire body of `index.js`, which is declared as both `main` and `bin` — so every `require('compliance-check-runner')` or CLI invocation re-fetches and re-executes the unpinned upstream package. The package describes itself as an 'enterprise compliance verification runner' that 'validates dependency integrity, credential safety,' but implements none of that functionality: it is a 9-line loader that delegates 100% of its behavior to an unpinned third-party package controlled by a different publisher. Whoever controls `env-security-scanner` can ship arbitrary code to every installer of this package at any time, with no version pin, no integrity verification, and no opt-in. ## Source: ghsa-malware (1cbdd0491c8d32a9e71f5bfcf054be752e06e74bc85ddfe957e67f97e8529a14) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.