@clerk/clerk-js@6.42.1
Clerk JS library
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package metadata and runtime behavior match Clerk’s authentication SDK. Its telemetry is disclosed, limited to development instances, and has a runtime disable control; the scanner’s network and dependency-bridge indicators are consistent with the SDK’s bundled integrations.
Decision evidence
public snapshot- The package metadata identifies the expected Clerk JavaScript library and points to Clerk’s official repository.
- The SDK explicitly tells users that telemetry is collected when connected to development instances and links to opt-out information.
- Runtime telemetry is disabled outside development instances and can be disabled with a configuration flag or CLERK_TELEMETRY_DISABLED; buffered events and logs are sent to the declared Clerk telemetry endpoint.
- The SDK contains network calls, including telemetry POSTs to clerk-telemetry.com.
- The telemetry collector can receive event payloads and log context, so its runtime behavior merits review.
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 SDK explicitly tells users that telemetry is collected when connected to development instances and links to opt-out information.
dist/clerk.jsView on unpkg · L88Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.42.1.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.42.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.