@greenlake/common-context@3.0.0
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource confirms an automatic installation beacon that discloses identifying host and project metadata to a hardcoded external recipient without installer consent. This meets the installation beacon policy for blocking.
Decision evidence
public snapshot- The package runs beacon.cjs automatically through its postinstall lifecycle hook.
- The beacon sends an HTTP POST to a hardcoded external IP address.
- The request payload includes the machine hostname, install path, and working directory.
- Importing index.js also calls the beacon without a user action.
Source & flagged code
8 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package runs beacon.cjs automatically through its postinstall lifecycle hook.
package.jsonView on unpkg · L7Findings
Affected versions and remediation
This report applies to @greenlake/common-context@3.0.0.
See all versions of @greenlake/common-context for other recorded verdicts.
- Avoid installing @greenlake/common-context@3.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.