config-normalizer-node
Config normalization for Node services, with install-time diagnostics.
This report shows the evidence for config-normalizer-node@1.0.0. 0 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 18h ago · by lpm-firewall-aiThe postinstall hook automatically sends a disclosed, payload-free request to a fixed diagnostics endpoint. This is default install-time telemetry, which warrants a warning under the policy; the source does not show collection of host, user, project, or credential data.
Decision evidence
public snapshot- The package runs scripts/install.js automatically through its postinstall hook.
- The install script calls beacon.emit during installation.
- The beacon makes an HTTPS GET to the fixed /beacon endpoint at my-contolled-backend.
- The README describes the request as empty and says it carries no identifiers or payload.
- The exported normalizer performs a configuration merge; no network behavior appears in that entry point.
- The README discloses the install-time diagnostic request.
Source & flagged code
8 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe package runs scripts/install.js automatically through its postinstall hook.
package.jsonView on unpkg · L12Findings
Affected versions and remediation
This report applies to config-normalizer-node@1.0.0.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of config-normalizer-node@1.0.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.