Feature: Celestia-backed NPM Registry

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, sqlite

Research direction

Start by tracing Apex's blob client and transaction-submission path, then map the SQLite metadata/index and npm-compatible registry API requirements. Done means the four listed implementation steps are covered: blob submission, tarball storage, metadata storage, and registry-compatible endpoints.

Written by the indexing model from the issue text.

Description

Summary

Expose an npm-compatible registry API backed by Celestia blobs through Apex.

Example usage:

npm publish --registry=https://apex.dev/npm
npm install package-name

Motivation

The npm ecosystem currently depends on centralized infrastructure.

Using Celestia DA would provide:

  • Permanent package availability
  • Censorship resistance
  • Decentralized package distribution
  • Verifiable package storage

Architecture

npm client
↓
npm registry API
↓
SQLite metadata/index
↓
Apex blob client
↓
Celestia blobs

Package tarballs would be chunked and stored as blobs.

Implementation Steps

  1. Implement blob transaction submission in Apex
  2. Store package tarballs as blobs
  3. Store package metadata in SQLite
  4. Expose npm registry compatible endpoints
Dominant language
Go
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evstack/apex

All issues in evstack/apex

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.