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 🙏

© 2025 – Pkg Stats / Ryan Hefner

scf-api

v1.4.0

Published

An SCF API Client for NodeJS

Readme

SCF API Client

A library that unifies interaction with SCF API.

Versions

📦 Stable Versions

The Stable versions are released under the latest tag on npm. These versions are encouraged to be used in production with production API.

The version number reflects how inter-changeable the version is with other versions. They are named in a x.y.z style, where:

z reflects the updates in the developer experience and the library itself. It is guaranteed that the versions that only differ in z are fully compatible feature-wise and interface-wise. They should only differ in the internal implementations and developer experience.

y reflects the breaking changes in the API methods or the exposed interfaces. By default the versions that differ in y are unlikely to be compatible and you have to ensure that your code uses the updated interfaces correctly.

x is reserved for major breaking changes with the library or API implementations. Versions that differ in x are incompatible.

🔧 Dev Versions

The Dev versions are released under the dev tag on npm. You are discouraged to use these versions as they are used for implementations of experimental features that could be breaking your code. Do NOT use dev versions in production setting.