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

codivew

v0.4.0

Published

Codivew CLI for AI code reviews through OpenAI-compatible APIs

Downloads

2,521

Readme

Codivew

English | 한국어

npm version npm downloads license

Codivew reviews Git changes through an OpenAI-compatible API and generates standalone HTML or machine-readable JSON reports. It runs without a separate Codivew server or database.

Features

  • Review working tree, staged, or branch changes
  • Get a summary and feedback by file and changed line
  • Browse diffs in a collapsible, standalone HTML report
  • Export structured review results as JSON
  • Automatically exclude sensitive and generated files

Requirements

  • Node.js 18 or later
  • Git
  • An OpenAI-compatible API with model listing and chat completion endpoints

Local Ollama works through its OpenAI-compatible endpoint. Pull a model before using it:

ollama pull qwen3.6:35b-a3b-coding-mxfp8

Installation

npm install -g codivew
codivew setup

setup lets you choose ko-KR or en, an authentication method (None, API Key/Bearer, or Basic Authentication), the API URL, and a model returned by GET /v1/models. Reviews use POST /v1/chat/completions. The local Ollama default is http://localhost:11434/v1 with no authentication.

Run codivew setup again at any time to change the endpoint or authentication. Credentials are entered without terminal echo, stored only in the user configuration file with owner-only permissions, and never displayed by config show.

Change the saved language without running setup again:

codivew config set language en
codivew config set language ko-KR

To update Codivew:

npm install -g codivew@latest

Usage

Run Codivew anywhere inside a Git repository.

# Review unstaged changes and untracked files
codivew
codivew working

# Review staged changes
codivew staged

# Review changes between main and HEAD
codivew branch

# Use a different base branch
codivew branch --base develop

Add project context with repeatable --context options:

codivew staged \
  --context "Node.js CLI project" \
  --context "Must support Node.js 18 or later"

Use a different OpenAI-compatible endpoint or model for one review. Saved authentication is still used:

codivew staged \
  --api-url https://api.example.com/v1 \
  --model qwen3.6:35b-a3b-coding-mxfp8

View all commands and options with:

codivew --help

Output

Reports are saved under .codivew/ in the directory where the command was run. HTML reports open automatically in your browser.

.codivew/

Use --no-open to prevent the browser from opening, or --output to choose the report path:

codivew staged --no-open
codivew staged --output ./reports/review.html
codivew staged --format json
codivew staged --format both --output ./reports/review

--format accepts html (default), json, or both. JSON-only output never opens a browser. With both, Codivew writes .html and .json files using the same base name and opens only the HTML report.

Excluded Files

Codivew excludes lockfiles, build output, generated files, environment files, private keys, certificates, minified JavaScript, and source maps. .env.example and .env.sample remain included.