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

@immediately-run/safe-content

v0.1.1

Published

The immediately.run safe renderer: non-executable MDX/Markdown as data, with no evaluator anywhere in the pipeline (TRUST_MODES_SPEC §5.1). Extracted from @immediately-run/sdk's safeContent tier (PLATFORM_LAYERING_SPEC §4, R3-279); the SDK re-exports it,

Downloads

866

Vulnerabilities

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

Links

Git

Maintainers

neumarkneumark

Keywords

Readme

@immediately-run/safe-content

The immediately.run safe renderer: untrusted Markdown/MDX-syntax content rendered as data, with no evaluator anywhere in the pipeline (TRUST_MODES_SPEC §5.1).

  • parseSafeMdast — MDX-syntax → mdast using the micromark/mdast tree with no acorn: expression nodes carry their source as inert strings, never evaluated.
  • renderMdast — mdast → React elements. JSX tags resolve only through a component registry by name, with literal string props only; unknown tags render their children inert; URLs pass an allowlist; wiki-links resolve through the shared link-space resolver (@immediately-run/mdx-plugins).
  • SafeContent — the React component wiring the two.

This is the S3 content-framework tier's first extraction from @immediately-run/sdk (PLATFORM_LAYERING_SPEC §4, R3-279). The SDK re-exports everything byte-compatibly (@immediately-run/sdk/safeContent/* keeps working); depend on this package directly only when you want the renderer without the platform client.

@immediately-run/mdx-plugins is a deliberate dependency (the anti-drift coupling): the compiled and interpreted paths share one grammar, so a wiki-link or heading anchor means the same byte on both sides.

A T2 tool, not a platform gate: it stops content executing as code; it certifies nothing to the host.