@bygd/gd-sdk-pes@1.43.60
AI Security Review
scanned 21d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook and no confirmed attack surface. The scanner’s exfiltration label is not supported by the inspected tracker request, which sends a product name and visitor ID to GameDock’s tracker.
Decision evidence
public snapshot- The manifest lists build and deployment scripts and has no npm lifecycle hook.
- The inspected bundles send a product name and visitor ID to GameDock’s product tracker; the request shown contains no credentials or body data.
- The SDK calls the tracking helper after the GameDock SDK loads.
- The scanner labels the behavior as credential or rich-record exfiltration, but the inspected request shows only product tracking with a visitor ID.
Source & flagged code
7 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/default/esm/index.jsView on unpkg · L1Package source references a known benign dynamic code generation pattern.
dist/default/esm/index.jsView on unpkg · L1The inspected bundles send a product name and visitor ID to GameDock’s product tracker; the request shown contains no credentials or body data.
dist/default/esm/index.jsFindings
Affected versions and remediation
This report applies to @bygd/gd-sdk-pes@1.43.60.
See all versions of @bygd/gd-sdk-pes for other recorded verdicts.
- Review the evidence and your use of @bygd/gd-sdk-pes@1.43.60 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.