Data source

Data from npm, delivered clean.

2 datasets pulled from npm's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.

  • 2 datasets
  • 1 industry
  • Real rows on request

What Datadory delivers from npm

2
Systems Software Global - the whole JavaScript and Node.js eco… · Current registry state plus full publication…

npm Public Registry API

Systems Software Global open-source ecosystem across seven pac… · Current snapshot per query

deps.dev - Open Source Insights API

Pick a catch, see the rows.

Name any npm dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.

Get a sample

API, files, or your warehouse. Daily, weekly, or hourly.

Straight answers about npm data

What is inside one npm package record?

The full packument: every published version with its own dependencies, dev-dependencies, engine requirements, integrity hashes and file counts; distribution tags such as latest; maintainers with publish rights; the declared license; keywords, homepage, repository and issue-tracker links; and created and modified dates for the package as a whole. Twenty-eight fields, defined once, holding on every record.

Is the schema stable enough for production pipelines?

Twenty-eight fields are documented once and appear identically on every package record, definitions verified against live responses during cataloging with worked examples attached. Pipelines written against the dictionary run unchanged whether they process ten packages or the whole corpus, and extended structures ship under the same column shapes when you specify them.