@clerk/clerk-js@6.30.1
Clerk JS library
AI Security Review
scanned 27d ago · by lpm-firewall-aiInspected source shows ordinary Clerk package metadata and vendor telemetry gated to development instances with a disable option. The static flags do not establish a malicious attack surface.
Decision evidence
public snapshot- The manifest identifies the Clerk JavaScript repository and the clerk-js package directory.
- The manifest contains build and development scripts but no preinstall, install, or postinstall hook.
- The bundled telemetry endpoint is Clerk-owned and telemetry is restricted to development instances, with a disable option.
- Telemetry events and logs are sent by POST to the configured telemetry endpoint.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.jsView on unpkg · L59The bundled telemetry endpoint is Clerk-owned and telemetry is restricted to development instances, with a disable option.
dist/clerk.jsView on unpkg · L60Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.30.1.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.30.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.