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

@voightxyz/nosana

v0.1.0

Published

Voight × Nosana SDK — detect Nosana GPU jobs from inside the container and link agents to their on-chain job account.

Readme

@voightxyz/nosana

Voight × Nosana SDK. Detect, from inside the container, that an AI agent is running on a Nosana GPU job, and link it to its on-chain job account on Solana.

Built for the Voight × Nosana grant. Progress log: PROGRESS.md.

Install

npm install @voightxyz/nosana

Use

import { detectNosana, isRunningOnNosana } from '@voightxyz/nosana'

const nosana = detectNosana()
if (nosana) {
  // Running on a Nosana GPU.
  console.log(nosana.jobId)        // on-chain job account (base58)
  console.log(nosana.dashboardUrl) // https://dashboard.nosana.com/jobs/<jobId>
}

Zero runtime dependencies. CJS + ESM + TypeScript types.

How detection works

A Nosana node injects NOSANA_ID into every container/run operation of a job, and its value is the job's on-chain account address (verified against the nosana-ci/nosana-cli source: the container env merge in Provider.ts, and jobHandler.claim() which sets the flow id to the claimed job address). The SDK also honors NOSANA_JOB_ID and JOB_ID as fallbacks, and carries DEPLOYMENT_ID for load-balanced deployments.

Because the detected id is the on-chain account, the same value that flags "this agent runs on Nosana" also anchors it to Solana: no extra lookup needed to correlate GPU workloads with on-chain activity.

API

| Export | Returns | | --- | --- | | detectNosana(env?) | NosanaContext \| null — { jobId, source, isAddress, dashboardUrl?, deploymentId? } | | isRunningOnNosana(env?) | boolean | | nosanaJobUrl(jobId) | Nosana dashboard URL for a job |

Development

npm install
npm test        # node:test suite
npm run build   # tsup → dist (esm + cjs + d.ts)

License

MIT © Galaxyhub Labs Inc. d/b/a Voight