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

scrutinizor

v1.1.0

Published

Extract a git repository's metadata relying on open source conventions

Readme

scrutinizor

npm npm license npm downloads travis

Extract a git repository's metadata relying on open source conventions

Installation

Install scrutinizor by running:

npm install --save scrutinizor

Documentation

scrutinizor.local(gitRepository, options) ⇒ Promise

Kind: static method of scrutinizor
Summary: Examine a local git repository directory
Access: public
Fulfil: Object - examination results

| Param | Type | Description | | --- | --- | --- | | gitRepository | String | path to git repository | | options | Object | options | | options.reference | String | git reference to check | | [options.progress] | function | progress callback (state) |

Example

scrutinizor.local('./foo/bar/baz', {
  reference: 'master',
  progress: (state) => {
    console.log(state.percentage)
  }
}).then((results) => {
  console.log(results)
})

scrutinizor.remote(gitRepository, options) ⇒ Promise

If $GITHUB_TOKEN is set, it will be used to authenticate with GitHub to increase rate-limiting.

Kind: static method of scrutinizor
Summary: Examine a remote git repository url
Access: public
Fulfil: Object - examination results

| Param | Type | Description | | --- | --- | --- | | gitRepository | String | git repository url | | options | Object | options | | options.reference | String | git reference to check | | [options.progress] | function | progress callback (state) |

Example

scrutinizor.remote('[email protected]:foo/bar.git', {
  reference: 'master',
  progress: (state) => {
    console.log(state.percentage)
  }
}).then((results) => {
  console.log(results)
})

Tests

Our test suite contains integration test cases that run this module against real projects. For that reason, we maintain a set of git submodules in test/repositories, where the actual test cases that assert their results live in test/e2e.

  1. Fetch all git submodules
git submodule update --init --recursive
  1. Set $GITHUB_TOKEN, to increase rate-limiting

  2. Run the test npm script:

npm test

You may enable debug information by setting DEBUG=scrutinizor*.

Contribute

Before submitting a PR, please make sure that you include tests, and that the linter runs without any warning:

npm run lint

One of the most valuable things you can contribute to this project is implement or improve plugins, which are small functions whose duty is to extract a certain facet about the repository, like license information.

  1. Create a new file in lib/plugins, like myplugin.js

  2. Export a function that takes a single argument, backend, which contains every function you need to interact with a git repository, like reading a file

Make sure you use the backend object instead of falling back to fs or an API call, so the plugin works fine in both local and remote modes.

You can do whatever you need here, including checking out other branches. scrutinizor will make sure the project is properly reset before calling another plugin.

  1. Add the new plugin to BUILTIN_PLUGINS in lib/index.js

  2. Update test cases in test/e2e

Support

If you're having any problem, please raise an issue on GitHub.

License

This project is free software, and may be redistributed under the terms specified in the license.