@zerohash-sdk/onboarding-js@1.13.0
A JavaScript SDK that enables frontend applications to seamlessly integrate with the Connect Onboarding product.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is not malicious by direct static evidence, but it delegates executable code to a remote CDN at runtime and reports diagnostics. This is a genuine unresolved remote-code execution surface rather than an install-time attack.
Decision evidence
public snapshot- The package has no install lifecycle hooks, but its browser SDK dynamically loads a remote module when the consumer calls render().
- The remote module URL is selected from Zerohash CDN hosts and inserted as a module script into the document head.
- On script-load failure, it posts telemetry containing browser user agent, page origin, decoded JWT claims, and failure details to a collector endpoint.
- The manifest exposes only the built SDK and contains no lifecycle scripts or dependency declarations.
- The remote loader is reached through the explicit render API rather than package installation or import.
- No filesystem access, shell execution, eval-like execution, persistence, or destructive behavior was found in the inspected source.
Source & flagged code
5 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.d.tsView on unpkgThe package has no install lifecycle hooks, but its browser SDK dynamically loads a remote module when the consumer calls render().
package.jsonView on unpkg · L1Findings
Affected versions and remediation
This report applies to @zerohash-sdk/onboarding-js@1.13.0.
See all versions of @zerohash-sdk/onboarding-js for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/onboarding-js@1.13.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.