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

@reviewpipe/core

v0.1.0

Published

Schema, interfaces, and pipeline engine for reviewpipe. Zero ML dependencies.

Readme

@reviewpipe/core

The core of reviewpipe — the Pipeline engine, the pluggable interfaces, the NormalizedReview / AnalysisResult types, and the provider-agnostic aggregation logic.

Zero runtime dependencies. Model- and format-specific code lives in separate packages (adapters, providers, exporters); this package never pulls in an ML dependency.

npm install @reviewpipe/core
import { Pipeline } from '@reviewpipe/core';

const result = await new Pipeline()
  .source(adapter) // a SourceAdapter — e.g. @reviewpipe/adapter-csv
  .provider(provider) // an AnalysisProvider — e.g. @reviewpipe/provider-lexicon
  .run(input);

result.overallSentiment; // { score, positive, neutral, negative, reviewCount }
result.trend; // average sentiment per month
result.flagged; // reviews needing attention (rating/text mismatch, strongly negative)
result.errors; // non-fatal per-review failures — one bad row never crashes the batch

What's here

  • Pipeline — a builder wiring source → use(transform)* → provider → themes → export → run.
  • Interfaces — SourceAdapter, Transformer, AnalysisProvider (with a capabilities flag), ThemeExtractor, and Exporter. Everything else in the ecosystem implements one of these.
  • Types — NormalizedReview, AnalysisResult, SentimentResult, Theme, TrendPoint, FlaggedReview, PipelineError, and SCHEMA_VERSION.

Provider failures are isolated per review; adapter/transformer failures are fatal (nothing left to analyze). See the documentation for the full guide.

License

Apache-2.0