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

@knowledge-forge-ai/theme-forge-nebular-fusion

v0.8.0

Published

Desktop workbench for reviewing, inspecting, and managing Theme Forge brand systems and artifacts

Readme

Theme Forge Nebular Fusion

Theme Forge Nebular Fusion 0.8.0 is a native desktop GUI distributed through a small npm wrapper. The wrapper selects exactly one optional platform package: darwin-arm64 (Apple Silicon), linux-arm64, or linux-x64 (AMD64). The wrapper owns the tfnf command; platform packages do not install competing bins.

Install and use

Install the wrapper with npm. npm selects the optional native package for the host when the matching package is available:

$ npm install --global @knowledge-forge-ai/[email protected]
$ tfnf --version
theme-forge-nebular-fusion 0.8.0 (<host-target>)
$ tfnf --help
Theme Forge Nebular Fusion 0.8.0
Usage: tfnf [--version|--help|--path]
Normal invocation launches the installed GUI.

tfnf --path authenticates the installed platform package and prints the absolute canonical path of the GUI executable without launching it. A normal tfnf [application args...] invocation verifies the payload immediately before pathname-based launch and forwards the arguments to the native GUI. There is no first-launch download, checkout fallback, ambient compiler/runtime fallback, or foreign-architecture fallback. Unsupported hosts fail closed.

Platform qualification

Linux requires GNU/glibc; musl and unsupported libc environments fail closed. Consult the matching release receipts for measured Linux compatibility floors and native GUI qualification. Source version and optional-package presence alone do not establish either.

Nebular 0.8 targets macOS 13.3 or later on the Darwin ARM64 path. For an unreleased candidate, this is a deployment policy rather than a claim that an artifact has been built, signed, notarized, or natively qualified. Use only the corresponding qualified artifact and release instructions for a published version. The native qualification gate must still prove the shipped Tauri WebView behavior, including the Solar Sail constructable-sheet preview and Starlight under the effective CSP.

Availability of developer archives, the Darwin npm package, and the GUI formula is established separately by matching release and channel records. A Homebrew cask has separate qualification gates and may remain withheld; do not infer signing or notarization status across channels. Do not bypass Gatekeeper or remove quarantine as an installation workaround.

Payload verification

Each platform manifest binds the package identity, complete payload inventory, regular-file sizes and SHA-256 hashes, file and directory modes, and exact internal symlink targets. Before launch the verifier enforces:

  • manifest size <= 4 MB and <= 20,000 inventory members;
  • complete payload status and the target-specific app-bundle or Linux-executable-resources payload type;
  • package version, OS, CPU, executable path, and payload-root identity;
  • path containment with no empty, ., .., backslash, NUL, or traversal segments;
  • relative, contained symlinks only, with exact declared targets;
  • 0o755 directories, 0o644 or 0o755 regular files, executable GUI binary, <= 512 MB per file, and <= 2 GB aggregate payload; and
  • changed or missing bindings, manifests, files, executables, or unexpected on-disk members rejected closed.

This authenticates installed package input. It is not a substitute for a release provenance, signing, or notarization receipt.

Launch boundary and process behavior

The wrapper sanitizes Node and dynamic-linker injection variables before launch (NODE_OPTIONS, NODE_PATH, LD_PRELOAD, LD_LIBRARY_PATH, LD_AUDIT, DYLD_INSERT_LIBRARIES, DYLD_LIBRARY_PATH, DYLD_FALLBACK_LIBRARY_PATH, DYLD_FRAMEWORK_PATH, and DYLD_FALLBACK_FRAMEWORK_PATH) while preserving desktop variables such as DISPLAY, WAYLAND_DISPLAY, XDG_*, DBUS_SESSION_BUS_ADDRESS, HOME, and PATH.

For a Linux package carrying an authenticated private-runtime projection, a normal invocation verifies the complete payload and selects only the manifest-authenticated payload/bin/tfnf launcher. That launcher checks its private runtime roles, removes every LD_* variable and GLIBC_TUNABLES, then sets its own canonical LD_LIBRARY_PATH and LD_PRELOAD=libwebkit2gtk-4.1.so.0.19.9 before executing the GUI. tfnf --path remains a non-launching query that prints the authenticated GUI executable path. Darwin and legacy non-private payloads retain direct authenticated GUI selection and do not use this Linux private-runtime preload path.

Exit codes and terminating signals are propagated. SIGTERM and SIGINT are forwarded to the child; after a fixed 5000 ms termination interval the launcher escalates to SIGKILL if needed.

Verification occurs immediately before pathname-based child_process.spawn. Node does not use fexecve; same-user concurrent pathname mutation, symlink replacement, or file alteration after verification is outside this guarantee.

Build and release boundary

Published PyPI launcher versions use an explicit tfnf install-runtime step to download and verify the matching native payload from GitHub. Consult the matching release instructions for availability. This npm wrapper never downloads a native payload.

Platform package assembly consumes explicitly selected, authenticated native payload directories and external manifest digests. Pending-native-build inputs are not complete GUI packages; the wrapper does not fabricate completed payloads. tools/qualify-nebular-npm-package.mjs qualifies explicitly prepared platform packages, packs the selected package set offline, and tests installation and target selection. Native GUI workflows and release publication are separate evidence gates.

License

Theme Forge Nebular Fusion is offered under AGPL-3.0-or-later. Review LICENSE and NOTICE before use and preserve those notices when conveying the package.