Social SDK
github.com/opencoredev/social-sdk- Category
- Developer Tools
- Rank
- No. 1081Tools index
Previous survey · No. 2820 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Coding
- GitHub
- 856 stars
- Latest release
- @opencoredev/social-sdk@0.5.0
- Date
About
Social SDK is a typed TypeScript SDK for integrating social platforms, with capability checks, explicit delivery outcomes and deterministic testing. It offers direct adapters for Bluesky, Instagram, LinkedIn, Threads, TikTok, X and YouTube, plus optional managed backends such as Zernio, Post for Me and PostFast.
What it does
A server-side library that lets an app post, read, pull metrics and handle comments on several social networks through one client object. You pick a route per account: call the network directly with your own app credentials, or hand the call to a paid scheduling service using your key with that vendor. Each publish returns a separate result per destination, so one failed network never silently reroutes to another account. A bundled fake backend and an offline command-line checker let you build and test before touching real credentials.
Why it's ranked here
The case rests on honesty about what is and is not proven. The docs state plainly that every provider-authorized live check is not checked, that the audit was offline, and that a dash in the comparison table means unimplemented in the SDK rather than missing from the vendor. Each direct network has its own audit row in the status notes, naming the test files behind it. Against that, it is pre-1.0 software whose own status page says no release has been requested for the audited changes. MIT licensed, with credentials kept server-side by design.
What's good
Delivery results are honest. A publish reports complete, processing, uncertain or failed per destination, and the docs warn that a provider accepting a post is not the network publishing it, so you must reconcile pending work. The offline checker cannot reach the network at all: its diagnostic adapters get a request function that throws, and validation refuses input over 1 MiB and never echoes content or account identifiers back. Webhook handling is specific: one vendor signs payloads with HMAC over raw bytes, another only checks a shared header, and the SDK rejects unsigned callbacks from a third, telling you to poll instead.
Tradeoffs
Coverage is uneven across routes. Only Zernio exposes comments, messages, account analytics and native post removal; PostFast only schedules posts, and Buffer needs media already hosted at a public HTTPS address. On the direct route, X publishes text and images only and search is not exposed for TikTok, Instagram or LinkedIn. Switching managed vendors later moves none of your connected accounts, scheduled jobs or history. The library supplies no queue, scheduler worker, database or hosted service, so durable retries are yours to build. It runs only in trusted server code on Node 22.12 or later, or Bun.
How to use it well
Fits a small team adding posting or cross-posting to its own product, where a backend already holds tenant sessions. Start against the fake backend with an idempotency key on every publish, then run the offline doctor command to confirm which environment variables each adapter needs. Read the capability matrix for your exact network and content format before promising a feature. Map every connected account to a tenant yourself, since listing accounts is not a grant. It is not a scheduling product with a dashboard; if you need one, the managed vendors it wraps are that.
Technical notes+
packages/social-sdk/src/cli.ts lists thirteen adapter names (mock, five cloud backends, seven platforms) and builds each with a placeholder key and a noNetwork fetch that throws, so doctor, capabilities and validate run fully offline; exit codes are 0 valid, 1 diagnostic failure, 2 usage or input error, and validate caps input at 1024 * 1024 bytes and reports only issue code, severity and target index. doctor checks env var presence per adapter (for example X_USER_ID and X_ACCESS_TOKEN) without printing values. packages/social-sdk/src/server/index.ts re-exports connections, credentials, webhooks and oauth modules. package.json is a Bun workspace driven by Turbo, linted with oxlint and versioned through Changesets. planning/implementation-status.md records 559 regenerated capability declarations and marks all live provider verification as not checked.
Observed
- License
- MIT (LICENSE)
- Language
- TypeScript
- Install
- npm or bun package @opencoredev/social-sdk
- Runtime
- Server-side Node.js 22.12+ or Bun; not for browser bundles
- Interfaces
- Library plus an offline diagnostic CLI with adapters, capabilities, doctor, examples and validate commands
- Direct adapters
- Bluesky, Instagram, LinkedIn, Threads, TikTok, X, YouTube
- Managed backends
- Zernio, Post for Me, PostFast, Postiz, Buffer
- Live verification
- Provider-authorized live checks marked NOT CHECKED in planning/implementation-status.md
- Test double
- Deterministic mock backend exported from the testing subpath
Read from README.md, package.json, packages/social-sdk/src/index.ts, packages/social-sdk/src/cli.ts, packages/social-sdk/src/core/index.ts, packages/social-sdk/src/server/index.ts, apps/docs/docs/index.mdx, apps/docs/docs/backends/index.mdx, apps/docs/docs/platforms/index.mdx, planning/implementation-status.md, examples/snippets/mock-quickstart.ts, LICENSE.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.