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

flinteditor

v0.5.2

Published

Very much in development.

Readme

FLINT editor extension for Visual Studio Code

Very much in development.

Functionalities

For all acts, facts and duties:

  • Index in tree-view
  • Jump to definition
  • Find references
  • Autocompletion

Validation:

  • Warnings and errors based on law-reg validation logic
  • Validation using json-schema, including snippets for auto-insertion

Execution:

  • Running a FLINT model in the Compliance by Design demo (Ctrl + shift + P, then type Run Flint)

Configuration needed for execution

In order to run a model, some configuration is needed to run. This can be configured on a folder-basis. (Right click on the empty space in a vscode folder, navigate to Extensions -> FLINT editor, click Edit settings.json)

Example config:

Actors are all actors specified, factFunctionSpec links different facts to those actors. Active actors are the (exactly 2) actors that are shown in the interface.

{
    "flinteditor.run_configuration": {
        "name": "ANLb",
        "actors": ["RVO", "collectief"],
        "activeActors": ["RVO", "collectief"],
        "factFunctionSpec": {
            "[RVO]": "RVO",
            "[agrarisch collectief]": "collectief"
          }
    }
}

Package

npm run package

Install in vscode

Install the resulting .vsix file in vscode by manually loading it as extension.