@clerk/clerk-js@6.39.1
Clerk JS library
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe suspicious network, environment, and credential-transport signals resolve to development-instance telemetry and a credential-free polling request. The manifest has no install lifecycle hook, and the inspected runtime source establishes no concrete attack behavior.
Decision evidence
public snapshot- package.json defines runtime entrypoints and contains no install lifecycle hook.
- The flagged React Native polling request omits credentials and uses a timeout-bound fetch.
- Telemetry is enabled only for development instances, with disable and webdriver checks; its default endpoint is Clerk’s telemetry service.
- The SDK sends generated event and log batches to its configured telemetry endpoint.
- The additional native and browser chunks are registered as code-split modules, and the legacy bundle uses a standard module wrapper.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.jsView on unpkg · L87Telemetry is enabled only for development instances, with disable and webdriver checks; its default endpoint is Clerk’s telemetry service.
dist/clerk.jsView on unpkg · L88Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.39.1.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.39.1 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.