registry / @clerk/clerk-js / 6.33.0
@clerk/clerk-js@6.33.0
Clerk JS library
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest routes package entrypoints to Clerk bundles, declares relevant wallet dependencies, and has no install lifecycle hook among its scripts. Inspected telemetry behavior is development-gated and directed to Clerk's telemetry endpoint; the static scanner hints do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Telemetry collection when the SDK is used in a development instance, unless disabled.
Impact
Development telemetry is sent to Clerk; the inspected code does not establish credential theft or unrelated data exfiltration.
Mechanism
The browser bundle posts event and log batches to /v1/event and /v1/logs using the configured Clerk telemetry endpoint.
AI rationale
The manifest routes package entrypoints to Clerk bundles, declares relevant wallet dependencies, and has no install lifecycle hook among its scripts. Inspected telemetry behavior is development-gated and directed to Clerk's telemetry endpoint; the static scanner hints do not establish malicious behavior.
Network endpoints1
clerk-telemetry.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points package imports to Clerk distribution bundles and lists wallet SDK packages as dependencies.
- No preinstall, install, or postinstall hook appears in the inspected manifest scripts.
- The telemetry bundle uses the Clerk telemetry endpoint and gates collection to development instances, with a disable flag.
- Telemetry sends event and log batches to paths on that endpoint; no unrelated recipient was found in the inspected telemetry code.
- The CommonJS bundle identifies itself as @clerk/clerk-js.
Evidence against
Behavioral surface
CryptoEnvironmentVarsEvalNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
5 flaggeddist/clerk.jsView file
59package = @clerk/clerk-js; repositoryIdentity = javascript; dependency = @base-org/account
L59: ${e.trim()}
L60: (This notice only appears in development)`,e8=e=>e6(`${e} as a function is not supported in this environment. The value will be ignored. Provide an absolute URL instead.`),e4={prox...
L61: For more information contact us at ${t}`)}function an(e){throw Error(`${t6} Calling ${e}.reload is not currently supported. Please contact support.`)}function ai(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 · L59dist/clerk.browser.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @clerk/clerk-js@6.31.1
matchedIdentity = npm:QGNsZXJrL2NsZXJrLWpz:6.31.1
similarity = 0.927
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/clerk.browser.jsView on unpkgFindings
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
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @clerk/clerk-js@6.33.0.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.33.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.