@clerk/clerk-js@6.29.0
Clerk JS library
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection found a bundled authentication SDK with package-aligned runtime telemetry, not malicious install-time or runtime behavior. The static hints are explained by legitimate network, wallet, and telemetry dependencies.
Decision evidence
public snapshot- Runtime telemetry posts event/log data to Clerk's telemetry service.
- Telemetry conditionally includes only the first 16 characters of a supplied secret key.
- Entrypoints are bundled Clerk library targets; manifest has no npm lifecycle hook.
- No preinstall, install, or postinstall script is declared.
- No child-process, filesystem-write, or AI-agent-control-surface behavior was found in inspected package artifacts.
- Network behavior is package-aligned authentication/telemetry functionality, not a staged payload chain.
Source & flagged code
4 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.native.jsView on unpkg · L17Runtime telemetry posts event/log data to Clerk's telemetry service.
dist/clerk.native.jsView on unpkg · L16Telemetry conditionally includes only the first 16 characters of a supplied secret key.
dist/clerk.native.jsView on unpkg · L16Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.29.0.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.29.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.