Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
This is an implementation of go-datastore that is backed by DynamoDB.
ddbds includes support for optimized prefix queries. When you setup your table's key schema correctly and register it with ddbds, then incoming queries that match the schema will be converted into DynamoDB queries instead of table scans, enabling high performance, ordered, high-cardinality prefix queries.
Package merkledag implements the IPFS Merkle Directed Acyclic Graphs data structures as specified in https://docs.ipfs.tech/concepts/merkle-dag.
Package p2phttp allows to serve HTTP endpoints and make HTTP requests through LibP2P using Go's standard http and net stacks.
This package provides P2P routing implementations for IPFS development.
go-cidutil implements various utilities and helper functions for working with CIDs.
This is an IPLD ADL that provides string based pathing for protobuf nodes. The top level node behaves like a map where LookupByString returns the Hash property on the Link in the protobufs list of Links whos Name property matches the key. This should enable selector traversals that work based of paths.
Datastore is a generic layer of abstraction for data store and database access. It is a simple API with the aim to enable application development in a datastore-agnostic way, allowing datastores to be swapped seamlessly without changing application code. Thus, one can leverage different datastores with different strengths without committing the application to one datastore throughout its lifetime.
Package cmds helps building both standalone and client-server applications.
Package blockservice implements a BlockService interface that provides a single GetBlock/AddBlock interface that seamlessly retrieves data either locally or from a remote peer through the exchange.
This package provides a DS implementation backed by Badger.
This package implements a functionality to prioritize queue of abstract tasks distributed among peers.
This package provides an implementation DNS over HTTPS resolver as specified in RFC 8484.
Basic utilities to generate fast path CBOR codecs for types.
Package flatfs is a Datastore implementation that stores all objects in a two-level directory structure in the local file system, regardless of the hierarchy of the keys.
IPFS is a global, versioned, peer-to-peer file system. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bittorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built in. You can also mount the world at /ipfs.
This package provides a very simple daemon to interface to from other programming languages. It's designed to fulfill the needs of Spritely's Goblins library to support libp2p as a netlayer.
This is an implementation of the IPLD @urlhttps://ipld.io/specs/codecs/dag-jose/spec/,dag-jose codec.
This package implements a Badger v4 (a key-value database) backed datastore for IPFS.
go-ipfs-exchange-interface defines the IPFS exchange interface.
Package measure provides a Datastore wrapper that records metrics using https://github.com/ipfs/go-metrics-interface.
go-ipfs-blockstore implements a thin wrapper over an IPFS datastore, giving a clean interface for getting and putting block objects.
This package provides facilities for the Publish/Subscribe pattern of message propagation, also known as overlay multicast. The implementation provides topic-based pubsub, with pluggable routing algorithms.
go-ipld-format is a set of interfaces that a type needs to implement in order to be a part of the IPLD merkle-forest.
go-log wraps zap to provide a logging facade. go-log manages logging instances and allows for their levels to be controlled individually.