npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rvagg/car-to-schema

v0.1.0

Published

Read a CAR file and describe its blocks using IPLD Schemas

Readme

@rvagg/car-to-schema

Read a CAR file and describe its blocks using IPLD Schemas.

Usage

Install

$ npm install @rvagg/car-to-schema -g

Run

$ car-to-schema <path-to-CAR-file> --output=<output/dir> [--library=<schema/library/dir>]

Unqiue found schemas will be printed to stdout as well as written to files in the current working directory named schema_X.ipldsch (the human-readable text form) and schema_X.json (the JSON object descriptor form), where X is the unique schema number. A schema_summary.csv will also be written with a mapping of the schema to the number of blocks found matching that schema.

Library

If you have existing Schemas to match against, supply a directory path with --library and the Schemas found in that directory will be included in the matching process. Schema files should end with .ipldsch (or the object form can be .json).

The name of each Schema file in the library directory should be the name of the root type in the Schema. e.g. A Schema Schema describing the DAG-PB structure might be named PBNode.ipldsch and include a type PBNode. This type will be matched against the root found in the block.

Limitations

Currently only supports the following codecs for blocks:

  • DAG-CBOR
  • DAG-JSON
  • DAG-PB
  • raw
  • json

See also the Limitations section of ipld-schema-describer for the limitations of Schema inference on objects.

License & Copyright

Copyright 2020 Rod Vagg

Licensed under Apache 2.0 (LICENSE-APACHE / http://www.apache.org/licenses/LICENSE-2.0)