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

@asyra/core

v0.5.7

Published

Public composition core for canvas-based, visual, and domain-driven Asyra products

Readme

@asyra/core

Strict public composition facade and lifecycle coordinator for current Asyra Framework capabilities.

Requirements

  • Node.js 24.x
  • Yarn 4.3.1 for this repository's maintained workflows

Install

npm install @asyra/core
import core from '@asyra/core'

Use only the package root and the explicitly documented public subpaths.

Owns

  • composition closure, startup ordering, readiness, teardown, load coordination, and curated package facades
  • one pre-start render-engine provider and engine-neutral default adapter

Does not own

  • App-domain rules, UI presentation, concrete engine resources, backend policy, permissions, or the future Core Kernel

Start here

Use Core for supported App composition and extensions that cross canonical package owners. Register composition before the first core.start(...).

Read the Core App implementation guide before building: it connects transaction publications, incremental persistence, scoped subscriptions, computation reuse and lifecycle. Working Undo alone does not establish complete integration.

Lifecycle and composition

Startup validates and closes composition, initializes required runtime owners, loads canonical data, and publishes ready only after success. App-owned migrations form one connected migration chain; an unmatched string version passes through to ordinary owner validation. A failure tears down owned work and never reports false readiness. The current no-provider compatibility branch is not a public Headless lifecycle.

Learn more

Support and policy

GitHub Discussions is the intended public channel for community conversation and general help. Discussions is not enabled for this repository yet, so there is currently no public community support destination. GitHub Issues are not a general public support channel. External pull requests are not accepted by default. Community participation creates no SLA or response deadline.

You may use, inspect, and fork the package under the MIT License. Read the support policy. For suspected vulnerabilities, follow the security policy and report privately.