@clerk/clerk-js@6.32.0
Clerk JS library
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest maps normal package entrypoints and defines no install hook. The flagged network behavior sends buffered SDK events and logs to Clerk's telemetry service, with no inspected evidence of credential theft or another concrete attack.
Decision evidence
public snapshot- The manifest identifies `dist/clerk.js` as the CommonJS entrypoint and has no install lifecycle hook.
- The bundle configures telemetry for `clerk-telemetry.com` and sends buffered events and logs there.
- The inspected behavior is package-aligned Clerk SDK telemetry; no concrete malicious action was identified.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
dist/clerk.native.jsView on unpkg · L15Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.jsView on unpkg · L59Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.32.0.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.32.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.