@clerk/clerk-js@6.31.0
Clerk JS library
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner signals are consistent with a bundled authentication library and included wallet SDKs. Direct inspection found no lifecycle execution, self-dependency chain, persistence, harvesting, or destructive behavior.
Decision evidence
public snapshot- The manifest has no preinstall, install, or postinstall lifecycle hook.
- The package does not depend on its own package name.
- The declared entrypoints are bundled JavaScript library files for browser and React Native use.
- Inspection found no child-process execution, evaluator, filesystem harvesting, or install-time project mutation.
- The bundle configures an optional telemetry collector as a logging transport.
- The bundled runtime contains network and telemetry-related functionality.
- The bundle includes third-party wallet SDK code and environment checks, which explain the scanner signals but add normal authentication runtime complexity.
Source & flagged code
4 flaggedPackage source references dynamic require/import behavior.
dist/clerk.native.jsView on unpkg · L15Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/clerk.jsView on unpkg · L59Findings
Affected versions and remediation
This report applies to @clerk/clerk-js@6.31.0.
See all versions of @clerk/clerk-js for other recorded verdicts.
- Review the evidence and your use of @clerk/clerk-js@6.31.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.