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

@bpmsoftwaresolutions/appture

v1.0.0

Published

Layout intent validation and materialization pipeline. DISR + CST -> validated HTML with IEM scoring.

Readme

Appture

Appture is the production DISR/CST validation and materialization pipeline.

Core Concepts (DISR and CST)

  • DISR (Diagram Instruction Stream)

    • The model of meaning/intent.
    • Serves as the canonical reference model.
    • Acts as anti-drift source-of-truth for what the system is supposed to express.
  • CST (Composable Semantic Template)

    • The execution plan for how DISR truth is revealed.
    • Defines how intent is materialized into concrete renderable outputs.
    • Targets can include HTML, CSS, SVG, JavaScript, ReactJS, Node, XAML, workflows, and other renderable/runtime surfaces.

Core closed loop:

DISR + CST -> HTML

Validation checks:

  • grammar-contract
  • disr-to-cst
  • cst-to-output
  • disr-to-output
  • intent-expression

Architecture (Current)

Appture is organized as hard-cut stages:

  1. Fetch
    • load DISR text
    • load CST JSON
    • load external grammar profile
  2. Decode
    • merge grammar/profile + CST decode contract
    • enforce DISR boundary rules
    • parse DISR intent
    • validate grammar contract
  3. Execute
    • validate DISR-to-CST topology
    • materialize HTML from CST + intent primitives
    • compute intent-expression scoring
  4. Write-back
    • validate CST-to-output and DISR-to-output
    • write HTML artifact
    • write evidence artifact

The pipeline entrypoint is src/pipeline.ts.

Source Layout

  • src/types.ts — shared contracts and model types
  • src/core/
    • html-inspector.ts
    • interpolator.ts
    • topology-indexer.ts
  • src/fetch/
    • disr-sampler.ts
    • cst-sampler.ts
    • grammar-sampler.ts
  • src/decode/
    • boundary-guard.ts
    • disr-decoder.ts
    • grammar-resolver.ts
    • grammar-contract-validator.ts
  • src/execute/
    • topology-validator.ts
    • materializer.ts
    • iem-scorer.ts
  • src/write-back/
    • output-validator.ts
    • output-writer.ts
  • src/pipeline.ts — pipeline orchestrator
  • src/index.ts — public export surface
  • src/cli.ts — CLI runner

Demos and Artifacts

  • demos/demo-manifest.json defines demo order and metadata.
  • demos/<demo>/ contains source files and generated outputs:
    • *-output.html
    • *-evidence.txt
  • demos/.baseline/ stores baseline snapshots and hash manifests for no-regression verification.

CLI Usage

Run from the repository root:

  • npm run build
  • npm run appture -- all
  • npm run appture -- <demo-name>

Example demo names are in demos/demo-manifest.json.

Build Note (Grammar Assets)

Build now includes a grammar asset copy step so runtime profile loading works from dist/:

  • npm run build runs TypeScript compilation and copies grammar/ to dist/grammar/.
  • Copy script: scripts/copy-grammar-assets.js

Behavior Notes

  • Decode behavior is data-driven via renderingContract.decodeContract and optional external grammar profiles.
  • DISR boundary guardrails are enforced before parsing.
  • Primitive rendering is template-map driven and checked for materialization coverage.
  • Demo suite status follows current baseline truth; no-regression is validated using baseline evidence/HTML hashes.