ipfs/kubo

IPFS implementation in Go: a daemon that stores and serves content-addressed data, with a CLI, HTTP Gateway, and RPC API

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 3rd, 2026
Created on June 26th, 2014
Open Issues & Pull Requests: 872 (+0)
GitHub issues: Enabled
Number of forks: 3,169
Total Stargazers: 17,128 (+0)
Total Subscribers: 514 (+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)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Kubo is a Go implementation of IPFS that runs as a network daemon for storing and serving content-addressed data, with a command-line interface, HTTP Gateway, and RPC API.

Kubo solves the problem of distributed content storage and retrieval by implementing the InterPlanetary File System protocol. It uses content addressing through CIDs and DAGs, with UnixFS for organizing files and directories. The tool operates as a network service that discovers peers over both local networks via mDNS and wide-area networks via the Amino DHT. Data transfer is handled through Bitswap and HTTP protocols, with support for both trusted and trustless verifiable retrieval. The implementation takes an opinionated approach designed to maximize interoperability across the IPFS ecosystem.

Kubo suits developers and operators who need a full-featured IPFS node with comprehensive tooling. It is the most widely used IPFS implementation and works well for projects requiring a command-line interface, web-based node management through WebUI, or programmatic control via HTTP RPC API. The tool includes experimental FUSE mount support for accessing IPFS content as local filesystems and content blocking capabilities for public node operators. Developers building JavaScript applications should consider Helia as an alternative IPFS implementation.

The project maintains active continuous integration with automated builds on every commit. Development activity shows consistent engagement with the codebase through regular updates and testing workflows. The project sustains an active community discussion forum and maintains multiple communication channels for user support and coordination.