@clerk/clerk-sdk-node 0.5.1

Clerk (clerk.dev) server SDK for usage with node

@clerk/clerk-sdk-node@0.5.1 was published on 2021-07-28. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=10.

Deprecated: January 10 2025 marks the end of support for @clerk/clerk-sdk-node as previously announced in our October 2024 deprecation notice. Express users can migrate to the @clerk/express package. For more information, you can find our changelog here: https://clerk.com/changelog/2025-01-10-node-sdk-eol

All @clerk/clerk-sdk-node versions · Permanent reference to 0.5.1 · View npm registry JSON · Latest release

Package specifications

Version0.5.1
License declarationMIT
Published2021-07-28T11:05:27.054Z
Node.js requirement>=10
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size580.42 KiB
Published file count105
Package typeNot declared
ES module entrydist/clerk-sdk-node.esm.js
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies55
Repository stars1774
Repository forks484

Install @clerk/clerk-sdk-node 0.5.1

npm install @clerk/clerk-sdk-node@0.5.1
pnpm add @clerk/clerk-sdk-node@0.5.1
yarn add @clerk/clerk-sdk-node@0.5.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness