@clerk/clerk-js@6.39.0
Clerk JS library
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe manifest identifies the package’s distribution entrypoints and runtime dependency, while the inspected bundle shows ordinary Clerk API and configured-endpoint telemetry behavior. The scanner hints did not establish malicious behavior.
Decision evidence
public snapshot- package.json points consumers to the Clerk JavaScript distribution entrypoints and declares @clerk/shared as a runtime dependency.
- dist/clerk.js routes requests through the configured Clerk FAPI client.
- Telemetry sends queued events and logs to paths under its configured endpoint; no concrete attack behavior was identified.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.jsView on unpkg · L87dist/clerk.js routes requests through the configured Clerk FAPI client.
dist/clerk.jsView on unpkg · L89Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.39.0.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.39.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.