bluesky-social/atproto

Social networking technology created by Bluesky

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 6th, 2026
Created on December 17th, 2021
Open Issues & Pull Requests: 752 (+0)
GitHub issues: Enabled
Number of forks: 918
Total Stargazers: 9,631 (+0)
Total Subscribers: 112 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 372
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 483 days
Stale 30+ days: 351
Stale 90+ days: 326

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (313)
  • oauth (21)
  • enhancement (5)
  • documentation (3)
  • correctness (2)
  • good first issue (2)
  • consensus (1)
  • devex (1)

Most active issues this week

Detailed Description

AT Protocol is a decentralized social media protocol that provides a reference implementation and TypeScript SDK for building applications on top of the Authenticated Transfer Protocol.

The protocol solves the problem of vendor lock-in in social media by enabling third-party developers to build custom feeds, federated services, and alternative clients against the same APIs as first-party applications. It achieves this through a set of standardized schemas and APIs defined in Lexicon format, with the core protocol primitives split into focused packages for identifier parsing, DID and handle resolution, cryptographic signing, repository management, and firehose consumption. The Bluesky Social application layer builds on top of this foundation using the app.bsky namespace.

Developers building applications or bots should start with the type-safe SDK that generates TypeScript from Lexicon schemas and provides an HTTP client. Those implementing OAuth authentication can choose from client variants for browser, Node, or Expo runtimes. If you are implementing the protocol itself, the tool provides specialized packages for each concern: syntax for identifier parsing, identity and DID packages for resolution, crypto for signing operations, repo for repository and Merkle Search Tree management, and sync for firehose consumption. The older API client still exists but new code should prefer the newer SDK. The repository contains both the canonical Lexicon definitions for the core protocol and application layer, as well as multiple TypeScript packages published under the @atproto scope on npm.

The project maintains active discussion channels for questions and provides comprehensive protocol specifications and guides. Development activity shows consistent work across multiple focused packages, with clear separation between public APIs published to npm and internal shared utilities. The codebase demonstrates ongoing refinement of the SDK approach, with newer packages preferred over older alternatives while maintaining backward compatibility for existing code.