@greenlake/session@3.0.0
Compatibility shim.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest activates a beacon during installation, and the beacon sends identifying machine and project metadata to a fixed external endpoint without a consent guard. This is concrete unconsented installation-time disclosure, supporting a block.
Decision evidence
public snapshot- The package manifest runs the beacon during installation.
- The beacon sends an HTTP request to a fixed external address and labels the request with the package name.
- The outgoing payload includes the machine hostname, install path, working directory, and npm runtime information.
- The beacon writes the payload to the outgoing request.
- Importing the package entrypoint also triggers the beacon.
Source & flagged code
9 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe package manifest runs the beacon during installation.
package.jsonView on unpkg · L6Findings
Affected versions and remediation
This report applies to @greenlake/session@3.0.0.
See all versions of @greenlake/session for other recorded verdicts.
- Avoid installing @greenlake/session@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.