@clerk/clerk-js@6.38.1
Clerk JS library
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe flagged network and environment references are consistent with the package’s Clerk authentication, telemetry, and wallet integrations. Inspected evidence shows a Clerk telemetry endpoint and ordinary bundle entrypoints, with no install-time behavior or concrete attack surface.
Decision evidence
public snapshot- The manifest identifies this as Clerk’s JavaScript authentication package and defines runtime bundle entrypoints with no install lifecycle hook.
- The runtime bundle configures telemetry to use Clerk’s telemetry service by default and sends queued events and logs there.
- The bundle’s dynamic dependency bridge loads wallet and password-strength libraries consistent with the declared package dependencies; no concrete attack was established.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.jsView on unpkg · L87The runtime bundle configures telemetry to use Clerk’s telemetry service by default and sends queued events and logs there.
dist/clerk.jsView on unpkg · L88Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.38.1.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.38.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.