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

@eddiethedean/dpcs

v0.13.1

Published

WebAssembly bindings for the DPCS reference toolkit

Readme

dpcs (WebAssembly)

npm Wasmer Guides License

JavaScript/TypeScript bindings for the Data Pipeline Contract Standard (DPCS) Rust reference toolkit via wasm-bindgen. Parse, validate, plan, compare, and bind pipeline contracts in the browser or Node.

| | | | --- | --- | | npm | @eddiethedean/dpcs | | Wasmer | eddiethedean/dpcs | | Toolkit | 0.13.x (ROADMAP reference-implementation release) | | Spec | 1.0.0-draft | | Guides | dpcs.readthedocs.io | | Bindings notes | docs/BINDINGS.md |

The bare npm name dpcs is reserved under npm similarity rules; release CI publishes the scoped @eddiethedean/dpcs package. Wasmer module ABI is none (host JS still required for wasm-bindgen glue).

Install

npm install @eddiethedean/dpcs
# after a local wasm-pack build:
# npm install ./bindings/wasm/pkg

Quick start

import init, * as dpcs from "@eddiethedean/dpcs";

await init(); // required for some targets / bundlers

const report = dpcs.validate_yaml(yamlSource);
const errors = (report.diagnostics || []).filter((d) => d.severity === "error");
if (errors.length) {
  throw new Error(JSON.stringify(errors));
}

console.log(dpcs.version(), dpcs.dpcs_spec_version());

CommonJS (Node / smoke style):

const dpcs = require("@eddiethedean/dpcs");
const report = dpcs.validate_yaml(yamlSource);
console.log(report.diagnostics);

API

Exported functions return plain JS objects (serde → JsValue) unless noted. Parse failures reject / throw as strings.

| Function | Purpose | | --- | --- | | version() | Toolkit version string | | dpcs_spec_version() | Spec version (1.0.0-draft) | | validate_yaml(source) / validate_json(source) | Validate a contract document | | plan_yaml(source) | Build a pipeline plan (or validation report on refusal) | | evaluate_capabilities(profile_yaml, contract_yaml) | Check orchestrator capabilities | | bind_yaml(contract_yaml, profile_yaml, target) | Emit scaffolding (airflow, dagster, prefect, temporal, kubernetes, …) | | compare_contract_yaml(baseline, candidate) | Compatibility comparison | | validate_registry_yaml(source) | Validate an artifact registry document | | contract_to_json(source_yaml) | Convert YAML contract → JSON string |

CLI, report formats, and TUI are Rust-first (dpcs-cli); this package wraps the core library entry points. Full toolkit docs: dpcs.readthedocs.io.

Develop from source

cd bindings/wasm
wasm-pack build --target bundler --release --out-dir pkg --out-name dpcs
# CI also exercises: --target nodejs --dev
# Wasmer publish uses: --target web --release

Release profiles pass --enable-bulk-memory and --enable-nontrapping-float-to-int to wasm-opt (required for Rust 1.87+ WASM defaults). See Cargo.toml package.metadata.wasm-pack.profile.release.

After building for npm, set the scoped name before publish:

cd pkg && npm pkg set name=@eddiethedean/dpcs

License

Apache-2.0 OR MIT — same as the main dpcs repository.