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

@finsys/adapter-toolkit

v0.1.1

Published

Partner SDK for the FinSys Source Adapter Framework — manifest validator, fixture harness, mock consumer, and reference examples for adapter authors.

Readme

@finsys/adapter-toolkit

Partner SDK for the FinSys Source Adapter Framework. Build, validate, and locally test a source adapter without standing up the full FinSys stack.

Status: v0.1.0 — minimum viable surface. Expanding as partner-side feedback sharpens what authors actually need.

New here? Start with the integration guide

If you're a company integrating your data into FinHero as a data provider, read the integration guide — it walks you from zero to a working, validated adapter. Then:

The contract types are re-exported from this package, so one import does it: import type { SourceAdapter, AdapterManifest, AdapterExtraction, ApplicantIdentity } from "@finsys/adapter-toolkit".

What's in the box

  • validateAdapter(dir) — loads manifest.json, validates against the @finsys/core JSON-schema, dynamically imports the entry point, confirms the exported SourceAdapter matches the manifest's id + category, and cross-checks produces against the category's canonical field set. CLI variant: finsys-adapter-toolkit validate ./my-adapter.
  • runFixtures(adapter, fixtures) — runs the adapter against partner-supplied fixture pairs. Two modes:
    • rawPayload → calls extract(raw) only (tests transformation logic in isolation)
    • identity → calls fetch(identity) then extract(raw) (full e2e against a real or mocked upstream) Diffs actual canonical instances against expected and reports per-fixture pass/fail with structured errors.
  • MockConsumer — in-memory stand-in for FinSys's persistence layer. Mirrors the real AdapterStorageService contract enough that partners can do a full round-trip locally: extract → persist → query → assert. Implements replace-on-rerun semantics.

Example: examples/fake-telco/

A complete, runnable example: a fake telco API as a Docker container + a reference adapter that calls it. Drop it into a FinSys or FinSim stack as a first-time integration sanity check, or use it as a template for your own adapter.

See examples/fake-telco/README.md.

Install (once published)

npm install --save-dev @finsys/adapter-toolkit

During pre-release iteration this package is published to an internal Verdaccio registry, not the public npm registry. Public npm release lands after the OSS split.

Quickstart

import { validateAdapter, runFixtures, MockConsumer } from "@finsys/adapter-toolkit"

const result = await validateAdapter("./adapters/my-telco-v1")
if (!result.ok) {
  console.error(result.errors)
  process.exit(1)
}

const adapter = result.adapter!
const fixtures = [
  {
    name: "strong-payer",
    identity: { ihsId: 1, ic: "850101015432", fullName: "Aiman bin Hassan" },
    expected: [
      {
        instanceKey: "default",
        observedAt: "2026-01-01T00:00:00.000Z",
        values: { telcoOnTimePaymentRatio24m: 1.0 /* ... */ },
      },
    ],
  },
]

const results = await runFixtures(adapter, fixtures)
console.log(results)

Adapter contract (reference)

A source adapter is a directory with:

my-adapter/
├── manifest.json   # id, version, category, produces, optional requiredIdentityFields
└── extract.mjs     # default export: SourceAdapter { id, category, version, produces, extract(raw), fetch?(identity) }

See @finsys/core's SourceAdapter and AdapterManifest types for the full contract.

License

Apache-2.0