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

@elevasis/core

v0.74.0

Published

Minimal shared constants across Elevasis monorepo

Readme

@elevasis/core

Shared schemas, types, and constants for building on the Elevasis platform. Published from packages/core in the Elevasis monorepo, where it is named @repo/core.

Install

pnpm add @elevasis/core

Published surface

The workspace exposes far more subpaths than npm does. publishConfig.exports is the published surface, and it is these eight:

| Subpath | Contains | | -------------------------------------- | -------------------------------------------------------------------- | | @elevasis/core | Alias of ./organization-model — see the note below | | @elevasis/core/organization-model | The organization model: schemas, defaults, contract IDs | | @elevasis/core/organization-model/readiness | Readiness snapshot types and helpers | | @elevasis/core/auth | Multi-tenancy types and the permission catalog | | @elevasis/core/entities | BaseDealSchema and the other base entity schemas, for extension | | @elevasis/core/content | Content domain schemas | | @elevasis/core/knowledge | Knowledge graph types | | @elevasis/core/test-utils | Test helpers; requires vitest as an optional peer |

Anything else you may see referenced — ./platform, ./execution, ./business/*, ./pdf — is workspace-internal and does not resolve from an installed copy. Some of those capabilities reach tenants through @elevasis/sdk instead, which inlines the types it re-exports.

The bare root is an alias, deliberately

@elevasis/core and @elevasis/core/organization-model are the same module. The root entry builds from src/published.ts, which is one line re-exporting the organization model, so the two .d.ts files are byte-identical by construction rather than by accident.

This is worth knowing because the workspace root (src/index.ts) advertises a much larger browser-safe surface that npm does not ship. Import the named subpath you want; the root is kept only so an existing bare import keeps resolving.

Optional peers

pdfmake is an optional peer, not a dependency. No published subpath reaches the PDF code, so installing this package does not pull it in. Add it yourself only if you are working inside the monorepo against @repo/core/pdf.

vitest is likewise an optional peer, needed only by ./test-utils.

License

MIT — see LICENSE.