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

@skenora/tooling

v0.1.3

Published

Offline diagnostics, documentation, CLI, and transport-neutral MCP tooling for Skenora.

Vulnerabilities

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

Links

Maintainers

jdzhang225gmailjdzhang225gmail

Keywords

Readme

@skenora/tooling

Offline developer tooling and MCP adapters for Skenora. The package owns the skenora CLI, versioned documentation/example/schema resources, static scene checks, Node/browser doctor reports, a read-only stdio/loopback-HTTP server, and transport-neutral MCP handlers with optional host-injected ScenePlan tools.

It is deliberately not a dependency of browser products or Runtime. Run skenora --help after installing the package.

The installed immutable gallery is available through skenora examples list|search|show|pull. The default MCP exposes list/search/get/source without filesystem mutation; only the CLI pull command writes. All manifests and source artifacts are verified against the package-versioned resource hash.

Particle/weather guidance is installed as docs.particle-presets, with SDK source in examples.particle-presets. Discover them through skenora_search_resources or read them with skenora_get_resource. Hosts that install the optional built-in particle provider also expose its textures through the existing authorized skenora_search_scene_resources tool.

Use skenora mcp for stdio or skenora mcp --transport http for a read-only loopback Web MCP. Applications can import @skenora/tooling/mcp and @skenora/tooling/mcp/http to inject an authenticated, handle-scoped ScenePlanGateway adapter. Authoring composition requires an explicit authorization callback; HTTP additionally requires authentication. Write authorization receives a canonical plan hash and revision/idempotency intent, and scene inspection returns a revision-bound paginated safe outline. See the Web MCP guide.

@skenora/tooling/wgsl is an isolated optional audience that reflects trusted MaterialProgram-generated WGSL with @vgpu/wgsl and can validate it with a caller-supplied WebGPU device. skenora wgsl inspect runs the parser/reflection half and therefore reports unverified until a device participates.

Repository maintainers run pnpm check:tooling-resources for manifest drift. After an intentional resource edit, pnpm baseline:tooling-resources updates hashes and the package version; unlisted or missing resource files still fail.