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

@bluink/fonts

v26.10.5

Published

Bluink's shared offline web, PDF and Word font catalogue

Vulnerabilities

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

Links

Git

Maintainers

seemantrseemantr

Keywords

Readme

@bluink/fonts

Offline fonts for Bluink's interface and publication generators. Each family includes web, PDF and static Word faces from checksum-pinned upstream sources.

The package is installed by @bluink/cli. It contains prepared assets and requires no installation scripts or first-use downloads. Bluink-owned packaging code is MPL-2.0; the fonts retain their upstream OFL-1.1 licences, included with the assets.

For product information, visit bluink.app.

Build with npm run build --workspace @bluink/fonts. The pinned harfbuzzjs development dependency instances variable fonts through WebAssembly in Node. No Python installation or native build toolchain is needed for the fonts build. Installed export reads prepared assets in Rust and does not run this build tool.

fontDirectory('docx') provides complete regular, bold, italic and bold-italic TrueType faces plus their checksummed manifest and upstream licences. All variation axes are pinned; weight uses 400/700 and other axes use their upstream defaults. Every glyph is retained. Derived faces use stable Bluink family aliases to respect upstream reserved names and avoid confusion with installed variable fonts. Theme and UI font IDs continue to identify the original catalogue family.