@blueskydataplatform/shared-ui@0.0.1
Compatibility shim.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe source confirms automatic install-time disclosure of identifying host and project metadata to a fixed external recipient, with no affirmative consent guard. This supports blocking as installation-time data exfiltration.
Decision evidence
public snapshot- package.json runs beacon.cjs automatically during postinstall.
- beacon.cjs sends an HTTP POST to a fixed external address.
- The beacon includes the machine hostname, install path, current directory, package name, and npm version in its payload.
- Running beacon.cjs directly calls fire; importing index.js also calls it.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs beacon.cjs automatically during postinstall.
package.jsonView on unpkg · L6Findings
Affected versions and remediation
This report applies to @blueskydataplatform/shared-ui@0.0.1.
See all versions of @blueskydataplatform/shared-ui for other recorded verdicts.
- Avoid installing @blueskydataplatform/shared-ui@0.0.1. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.