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

@plasius/asset-sources

v0.1.5

Published

Fail-closed provider source connector contracts and disabled registry for the Plasius asset pipeline

Readme

@plasius/asset-sources

Build Status License Security Policy

Fail-closed provider source connector contracts for the Plasius governed asset pipeline. The package defines safe provider-facing ports and a deterministic disabled registry; provider-specific normalizers and live acquisition remain in their own reviewed Features.

Install

npm install @plasius/asset-sources

Contract surface

The package exports:

  • ProviderSourceDescriptor and createProviderRegistry() for the parent and five provider feature flags.
  • CredentialProvider, ProviderTransport, AcquisitionPort, PrivateStagingPort, and CheckpointPort for dependency-inverted implementations.
  • createProviderConnector() for search, metadata inspection, download requests, and private staging.
  • createFakeDependencies() and fixtureCandidate() for deterministic contract tests.

Callers provide opaque provider asset identifiers. They do not provide download URLs, credentials, paths, archive names, or provider-specific network addresses. Every real provider descriptor is disabled until the parent flag, provider flag, source review, rights evidence, capability, and private-staging gates are satisfied.

import {
  DEFAULT_PROVIDER_DESCRIPTORS,
  createProviderRegistry,
} from "@plasius/asset-sources";

const registry = createProviderRegistry();
const sketchfab = registry.get(DEFAULT_PROVIDER_DESCRIPTORS[4].providerId);
// sketchfab.enabled === false until its source review and rollout gates pass

Provider text is bounded and normalized as untrusted data. URL-shaped text is redacted, unsafe opaque IDs are rejected, rights evidence must be approved for commercial redistribution, and acquisition checkpoints are idempotent by caller-supplied key. Private staging returns only an opaque staging reference, checksum, media type, size, and expiry; it never returns a raw provider URL.

Development

Use Node.js 24 (the version in .nvmrc) and npm:

npm ci
npm run typecheck
npm test
npm run test:coverage
npm run lint
npm run build
npm run audit:npm
npm run privacy:check
npm run pack:check

The release workflow publishes only an exact successful main commit through .github/workflows/cd.yml. npm trusts the Plasius-LTD/asset-sources repository, cd.yml, and the GitHub production environment; no local publish or long-lived npm write token is permitted. Because npm cannot bind a trusted publisher before the package exists, the initial 0.1.0 publication has a separately selected, package-absence-checked bootstrap path using a short-lived credential in production. That path and credential are removed immediately after the trusted publisher is bound and an OIDC release is proven.

Architecture and rollout

The inherited template files in this repository provide the legal, security, contribution, workflow, and public-artifact integrity baseline required for @plasius/* packages.