Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

ipfs-utils

Package Overview
Dependencies
Maintainers
1
Versions
69
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

ipfs-utils

Package to aggregate shared logic and dependencies for the IPFS ecosystem

  • 0.7.3-rc.55
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
47K
decreased by-23.84%
Maintainers
1
Weekly downloads
 
Created
Source

js-ipfs-utils

Travis CI Codecov branch Dependency Status js-standard-style

This package serves as a central repository for shared logic and dependencies for all IPFS packages, using ipfs-utils helps to easily re-use small scoped blocks of logic across all the js core interface implementations and also as a dependency proxy (think aegir for domain logic dependencies).

ipfs-utils aims to provide single function default export per file (with a few exceptions) scoped in 3 general categories:

  • General use
  • Data structs wrangling (arrays, objects, streams, etc)
  • IPFS core subsystems

General use and Data structs wrangling should try to be just re-exports of community packages.

The IPFS ecosystem has lots of repos with it comes several problems like:

  • Domain logic dedupe - all interface-core implementations shared a lot of logic like validation, streams handling, etc.
  • Dependencies management - it's really easy with so many repos for dependencies to go out of control, they become outdated, different repos use different modules to do the same thing (like merging defaults options), browser bundles ends up with multiple versions of the same package, bumping versions is cumbersome to do because we need to go through several repos, etc.

These problems are the motivation for this package, having shared logic in this package avoids creating cyclic dependencies, centralizes common use modules/functions (exactly like aegir does for the tooling), semantic versioning for 3rd party dependencies is handled in one single place (a good example is going from streams 2 to 3) and maintainers should only care about having ipfs-utils updated.

Lead Maintainer

Hugo Dias

Install

$ npm install --save ipfs-utils

Usage

Each function should be imported directly.

const validateAddInput = require('ipfs-utils/src/files/add-input-validation')

validateAddInput(Buffer.from('test'))
// true

Functions

General Use

TODO

Data Struct Wrangling

TODO

Core API

TODO

Contribute

Contributions welcome. Please check out the issues.

Check out our contributing document for more information on how we work, and about contributing in general. Please be aware that all interactions related to this repo are subject to the IPFS Code of Conduct.

License

MIT © Protocol Labs Inc.

FAQs

Package last updated on 11 Mar 2020

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc