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

gcheck-core

v0.4.2

Published

Checklist engine of the Duniter/Ğ1 ecosystem, with the official gcheck checklists embedded

Readme

gcheck-core

Checklist engine of the Duniter/Ğ1 ecosystem: it reads a gcheck checklist (YAML or JSON), resolves its options, selects the questions to ask and turns the answers into a verdict (pass, warning or fail).

The official checklists (member certification, smith commitments…) are embedded. They come from the source of truth, g1_monetary_license: updating this dependency is enough to get their latest questions. An application can also provide its own checklists, instead of or on top of the embedded ones.

The Rust crate gcheck-core offers the same API and the same checklists; both engines are checked against shared test cases, so they cannot drift apart.

Usage

import { createEngine, Catalog, SMITH_ASPIRANT } from "gcheck-core";

const catalog = Catalog.embedded();
// …optionally, the application's own checklists, which take precedence:
// catalog.addContent("my-checklist", myYamlOrJson);

const checklist = catalog.get(SMITH_ASPIRANT, "fr");
const engine = createEngine();
const prepared = await engine.prepare(checklist.content);
if (!prepared.ok) throw new Error(prepared.error.message);
const quiz = prepared.value;

const answers = {};
for (const question of quiz.questions) {
	answers[question.id] = ask(question.text); // your UI here
}

const verdict = engine.evaluate(quiz, answers); // "pass" | "warning" | "fail"
for (const issue of verdict.issues) {
	console.log(issue.text, "expected:", issue.expected, issue.message);
}
  • quiz.checklistHash is the content hash of the checklist that was gone through: store it with the result, compare it later to know whether the checklist changed since. The Rust engine computes the same value.
  • allChecklists() lists the embedded checklists, getChecklist(id, lang) picks one (falling back to English, then to any available language).
  • externalChecklist(id, content) validates a checklist provided by the application.

Checklist format

Checklists follow the checklist schema published by the source of truth.

License

AGPL-3.0-or-later: GNU Affero General Public License, version 3 or (at your option) any later version.