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

@nimiplatform/kit-protected-local-darwin-arm64

v0.11.0

Published

Fixed macOS arm64 Node-API projection for Nimi protected-local carriers.

Downloads

895

Readme

Nimi protected-local macOS arm64 binding

This host-only Node-API package carries the fixed macOS filesystem-UDS Desktop and local-app transports. It has no renderer export, endpoint selector, portable token, or arbitrary RPC surface. Production requires the compile-time Developer ID team. The mutually exclusive local-development build requires an ad-hoc signature and does not consume a Team ID. Runtime admission uses the live audit-token peer, root-owned fixed executable path, exact signing identifier, strict SecCode identity, ad-hoc signature class, hardened-runtime validation, and process exit-or-exec liveness; it does not consume release-trust records or pre-recorded artifact hashes.