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

deterministic-sphere-network

v0.1.1

Published

Seeded Fibonacci-sphere proximity graphs and GPU-ready typed buffers with bounded deterministic topology.

Readme

Deterministic Sphere Network

Seeded Fibonacci-sphere proximity graphs with bounded degree and GPU-ready typed buffers. The package is pure TypeScript and has no runtime or rendering dependency.

Use cases

  • WebGL/Three.js network visualizations;
  • deterministic procedural fixtures;
  • sphere-distributed simulation nodes;
  • repeatable animation and screenshot tests;
  • GPU upload buffers for nodes, edges, and travelling packets.

Installation

From the built GitHub release asset:

npm install https://github.com/FrankFMY/deterministic-sphere-network/releases/download/v0.1.0/deterministic-sphere-network-0.1.0.tgz

The npm release is pending maintainer approval:

npm install deterministic-sphere-network

Example

import { generateSphereNetwork } from "deterministic-sphere-network";

const graph = generateSphereNetwork({
  nodeCount: 512,
  sphereRadius: 3,
  edgeMaxDistance: 1.2,
  maxEdgesPerNode: 6,
  packetCount: 2_000,
  seed: 42,
});

console.log(graph.nodePositions.length); // 1536
console.log(graph.edgeCount); // generated undirected edges

The same complete configuration always produces byte-identical typed-array values on the same JavaScript numeric runtime.

Output

  • nodePositions: Float32Array(nodeCount * 3);
  • nodeTiers: Uint8Array(nodeCount) containing core/relay/edge tiers 0/1/2;
  • nodePhases: deterministic values in [0, 2π);
  • edgeNodeIndices: endpoint node IDs as Uint32Array(edgeCount * 2);
  • edgeStarts / edgeEnds: flattened GPU-ready coordinates;
  • edgePhases: deterministic flow phases;
  • packetEdgeIndices: a valid edge ID for every packet;
  • packetSpeeds / packetOffsets: deterministic animation inputs.

Safety and complexity bounds

Generation uses an O(n²) exact neighbor search with per-node candidate sorting (O(n² log n) worst-case total time). To keep accidental UI/server inputs bounded, the public contract rejects:

  • more than 4,096 nodes;
  • degree caps above 32;
  • more than 1,000,000 packets;
  • non-finite or negative geometry values;
  • sphere radii whose jittered coordinates cannot remain finite in Float32Array and edge distances above the Float32 range;
  • non-integer seeds/counts;
  • packets when no edge can be generated.

Zero-node and one-node configurations are valid when packetCount is zero. The one-node case remains finite, and packet indices cannot silently point to a nonexistent edge.

Boundaries

This package generates topology and typed data only. It does not include rendering, shaders, animation loops, scene lifecycle, pointer interaction, layout controls, or Three.js/Svelte adapters.

Runtime: ESM on Node.js 20+. Reproducibility is scoped to the same numeric runtime, not guaranteed across engines. npm package. Until approval, the existing release asset above is usable; for this candidate run npm ci && npm run build && npm pack in a source checkout.

Development

npm ci
npm run format:check
npm run lint
npm run check
npm test
npm run build
npm run pack:check
npm run package:check

Author

Artem Prianishnikov — FrankFMY

  • Website: https://frankfmy.com
  • Email: [email protected] · [email protected]
  • Telegram: https://t.me/FrankFMY
  • LinkedIn: https://www.linkedin.com/in/frankfmy/
  • X: https://x.com/FrankFMY
  • npm: https://www.npmjs.com/~frankfmy

License

MIT © 2026 Artem Prianishnikov.