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

@canonical/ds-implementations

v0.44.0

Published

Implementation libraries and implementations of the Canonical design system, as Turtle (RDF) for the knowledge graph.

Downloads

845

Vulnerabilities

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

Links

Git

Maintainers

ilayda21ilayda21frankbanfrankbanhuwshimihuwshimianthonydillonanthonydillonsteverydzsteverydzbartazbartazjpmartinsptjpmartinsptpetesfrenchpetesfrenchjmuzinajmuzinamtrujmtrujedlerdedlerdabehniaabehniacanonical-organizationcanonical-organizationedisile-canonicaledisile-canonicalsteciuk-canonicalsteciuk-canonicalabbiesimsabbiesimsataku_bataku_bad.vlad.vlengr-aliengr-alininfa_jeonninfa_jeonndv99ndv99goulin-canonicalgoulin-canonicalimmortalcodesimmortalcodesalvaromateoalvaromateoonibenjo-canonicalonibenjo-canonical

Keywords

Readme

@canonical/ds-implementations

Turtle (RDF) datasets describing the implementation libraries and implementations of the Canonical design system, generated from @implements annotations across the pragma monorepo.

The canonical data lives at the monorepo root data/ directory and is regenerated by bun run collect (see scripts/collect-implementations.ts). This package snapshots that data at publish time (prepack) so it can be consumed as a pragma pack:

  • data/implementations.ttl — aggregate index of all implementation libraries
  • data/{librarySlug}/implementationLibrary.ttl — one ds:ImplementationLibrary per library
  • data/{librarySlug}/implementationObjects.ttl — the library's ds:ImplementationObjects

Each implementation carries a ds:headLink (source at main) and a ds:versionedLink (source pinned to the release tag), and each library a ds:version matching the release that produced it.

The vocabulary is the ds: ontology defined by @canonical/design-system.