registry / @clerk/clerk-js / 6.34.1
@clerk/clerk-js@6.34.1
Clerk JS library
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe inspected manifest and required bundle paths show package-aligned Clerk behavior, without an install hook, self-dependency chain, or concrete attack surface. The scanner signals do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Importing and using the Clerk library in an application.
Impact
No malicious impact was established from the inspected source.
Mechanism
The browser bundle sends queued telemetry through its configured endpoint and routes API requests through the configured FAPI client; no unrelated destination or hostile execution chain was established.
AI rationale
The inspected manifest and required bundle paths show package-aligned Clerk behavior, without an install hook, self-dependency chain, or concrete attack surface. The scanner signals do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies the package as Clerk’s JavaScript library from Clerk’s own repository.
- The inspected CommonJS bundle contains a guarded telemetry initialization path that checks runtime conditions and environment settings.
- The browser bundle sends telemetry events and logs to an endpoint configured by the package’s telemetry client.
- The browser bundle routes API requests through Clerk’s configured FAPI client.
Evidence against
- The manifest contains no preinstall, install, or postinstall hook and no runtime dependency on its own package name.
- Inspected network activity is consistent with Clerk telemetry and Clerk API requests; no unrelated recipient or concrete attack behavior was identified.
Behavioral surface
CryptoEnvironmentVarsEvalNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
5 flaggeddist/clerk.jsView file
85package = @clerk/clerk-js; repositoryIdentity = javascript; dependency = @base-org/account
L85: ${e.trim()}
L86: (This notice only appears in development)`,te=e=>e7(`${e} as a function is not supported in this environment. The value will be ignored. Provide an absolute URL instead.`),tt={prox...
L87: For more information contact us at ${t}`)}function ao(e){throw Error(`${t7} Calling ${e}.reload is not currently supported. Please contact support.`)}function al(e){throw Error(`${...
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.jsView on unpkg · L8586process.env&&tl.some(e=>e_(process.env[e]))||globalThis[tc])return;if("u">typeof console&&"function"==typeof console.log){for(let e of tu)console.log(e);console.log("")}globalThis[
Low
Ai Review Evidence
The inspected CommonJS bundle contains a guarded telemetry initialization path that checks runtime conditions and environment settings.
dist/clerk.jsView on unpkg · L86dist/clerk.browser.jsView file
Findings
2 High3 Medium7 Low
HighCopied Package Dependency Bridgedist/clerk.js
HighPrevious Version Dangerous Deltadist/clerk.browser.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEval
LowHigh Entropy Strings
LowUrl Strings
LowAi Review Evidencepackage.json
LowAi Review Evidencedist/clerk.js
LowAi Review Evidencedist/clerk.browser.js
Affected versions and remediation
This report applies to @clerk/clerk-js@6.34.1.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.34.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.