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

edc-lib

v0.2.0

Published

TypeScript client for the Eclipse Dataspace Connector (EDC) REST APIs, generated from the official OpenAPI specs with @hey-api/openapi-ts.

Readme

edc-lib

edc-lib is a JavaScript/TypeScript library to control / interact with the Eclipse Dataspace Connector.

The library is written in TypeScript and can be used from either JavaScript or TypeScript. It targets EDC 0.14.1 and is generated per API from the connector's official OpenAPI specs. It is intended for server-side use (Node >= 18) and relies on the runtime's built-in fetch — it has no runtime dependencies.

Installation

npm i edc-lib

Usage

A single EDCConnector bundles the connector's APIs. Configure it with the connector's base URLs and, optionally, credentials — either basic auth ({username, password}) or an API key ({apiKey, apiKeyHeader?}, header defaults to X-Api-Key). Then call the per-API services.

import {EDCConnector} from 'edc-lib';

const connector = new EDCConnector({
  controlPlane: {
    managementUrl: 'https://localhost:8181/management',
    controlUrl: 'https://localhost:9191/control', // optional, defaults to managementUrl
  },
  auth: {apiKey: 'my-api-key'},
});

// Register an asset on the management API
const {data: asset} = await connector.controlPlane.assetService.createAssetV3({
  body: {
    '@context': {'@vocab': 'https://w3id.org/edc/v0.0.1/ns/'},
    '@id': 'asset-1',
    properties: {name: 'My dataset'},
    dataAddress: {type: 'HttpData', baseUrl: 'https://example.com/data'},
  },
});

// Request a remote connector's catalog
const {data: catalog} = await connector.controlPlane.catalogService.requestCatalogV3({
  body: {
    '@context': {'@vocab': 'https://w3id.org/edc/v0.0.1/ns/'},
    counterPartyAddress: 'https://provider:8282/protocol',
    protocol: 'dataspace-protocol-http',
  },
});

// Check the connector's health
const {data: health} = await connector.observabilityService.checkHealth();

The service groups are connector.controlPlane (assets, catalog, contract definitions / negotiations / agreements, policies, transfer processes, EDR cache, secrets, data-plane selector, …), connector.dataPlane (provision and public data-plane APIs), connector.observabilityService, and connector.versionService.

Regenerating the client

The models and services are generated from the EDC OpenAPI specs with @hey-api/openapi-ts. The emitted *.gen.ts files are not hand-edited — change the generator configuration and regenerate instead.

npm run generate   # regenerate the client from the specs
npm run build      # generate + compile to build/

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

License

Apache 2.0