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

@fiducial/advisor

v0.3.0

Published

Advisory checks for Fiducial — typed judgments where deterministic rules cannot reach. Never gates anything.

Downloads

314

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

aleksazcodesaleksazcodes

Keywords

fiducialadvisorysystem-onecode-reviewdecisions

Readme

@fiducial/advisor

Advisory review for Fiducial products. Reached as fid advise.

What it is for

It asks a decision model the questions an exact check cannot answer:

  • a fact declared twice under two different names
  • logic sitting above the layer it could reach
  • a physical quantity declared without a unit or tolerance
  • an abstraction with no escape hatch
  • a comment explaining what instead of why
  • a change that does more than was asked, or is left half-finished

What it deliberately does not ask

Anything already decided exactly. A hand-edited artifact is fid derive --check. A missing translation is the i18n pipeline. Contrast ratios are arithmetic. A push to main is the guard. Spending a probabilistic answer where a certain one exists is a regression dressed as a feature, and a test in this package enforces that boundary.

Every check is a hybrid: code narrows candidates deterministically and the model judges only what survives. A question whose input is missing is not asked at all.

It cannot break anything

It writes no file, touches no artifact, and exits 0 even with findings — including when the key is missing, the network is down, or the model is overloaded. fid derive is byte-identical with and without a key, and crates/fiducial-cli/tests/determinism.rs proves it by deriving a product twice and hashing both trees. A gate whose verdict varies is not a gate, so AI in this platform advises and never derives.

--strict opts into a non-zero exit for a hook of your own. Never wire it into a gate that must not flake.

Usage

fid advise key set          # store an OpenRouter or TypeSafe key
fid advise                  # review uncommitted changes
fid advise --task "..."     # judge scope against what was asked
fid advise --base main      # review the whole branch
fid advise --facts          # duplicate-check new declarations
fid advise --dry-run        # print the exact request body, send nothing

--dry-run exists because this sends your diff to a third-party API, and "trust me" is not an acceptable answer to what leaves the machine.

License

MIT