registry / @clerk/clerk-js / 6.36.0
@clerk/clerk-js@6.36.0
Clerk JS library
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected bundle excerpts show standard exports and telemetry reporting. 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 the package exposes its CommonJS exports; telemetry sends when events or logs are queued.
Impact
No concrete malicious impact was established.
Mechanism
The browser bundle posts telemetry batches to configured endpoint paths. The inspected code showed no install hook or unrelated credential forwarding.
AI rationale
The manifest has no install lifecycle hook, and the inspected bundle excerpts show standard exports and telemetry reporting. The scanner signals do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json lists build and development scripts but no preinstall, install, or postinstall hook.
- dist/clerk.js ends with a normal CommonJS export bridge.
- dist/clerk.browser.js sends event and log batches to endpoint paths provided by its telemetry client.
Evidence against
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 · L8588wedProtocols:t?.useStaticAllowlistOnly?tr:this.#tx})};#th(){return void 0!==this.client}}})();var s=exports;for(var o in i)s[o]=i[o];i.__esModule&&Object.defineProperty(s,"__esModu
Low
Ai Review Evidence
dist/clerk.js ends with a normal CommonJS export bridge.
dist/clerk.jsView on unpkg · L88dist/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
LowSuspicious Lifecycle 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.36.0.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.36.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.