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

@crewhaus/dream-engine

v0.5.8

Published

v0.3.0 Goal 5 (design §6): scheduled memory consolidation — a deterministic phase-1 pass (TTL sweep, dedupe/supersede, staleness flags, sessions-index fold-in, proof pinning, handoff refresh, trash purge) plus ONE bounded, budget-capped model synthesis se

Vulnerabilities

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

Links

Git

Maintainers

studiomaxopsstudiomaxops

Keywords

Readme

@crewhaus/dream-engine

v0.3.0 Goal 5 (design §6): scheduled memory consolidation — "consolidation on a schedule, not every turn". A dream run is two phases:

  • Phase 1 — deterministic (always, idempotent, zero model spend): fact TTL sweep + near-duplicate supersede (+compact() growth bounding), staleness flags (facts unrecalled >90d, wiki unverified >30d — constants exported), sessions-index fold-in, proof-excerpt re-validation + retention-pin refresh, focus/handoff next-actions refresh, trash purge (>7 days).
  • Phase 2 — model synthesis (mode: full AND budget_usd > 0): ONE bounded fresh session (sessionTarget: "dream", singleTurn, capped tool loop) seeded with the dream playbook + phase-1 findings, acting ONLY through the normal registered tools (wiki_write, wiki_set_signals, MemoryForget, PlanUpdate) — the full justification/audit path. The engine refuses an unpriced model: cost-tracker's pricingMisses would turn the item-27 budget cap into a silent no-op.

Schedule state lives at .crewhaus/dream/<spec>/state.json ({lastRunAt, lastOutcome, phase1Counts, lastEvidence}); runs are window-idempotent (dream:<spec>:<floor(now/everyMs)> through durable-execution's withIdempotency, backed by a lock-honoring file store), so a janitor tick, a GH-Actions cron, and a CLI catch-up can never double-fire. dreamJanitorStep(engine) registers into runtime-core's janitor step registry with the CREWHAUS_DREAM=0 / CREWHAUS_DREAM_INTERVAL_MS env knobs.

The model session is an injected seam (DreamModelPhase) — the CLI verb and daemon emitters build it from runChatLoop; this package stays runtime-core-free. Composition happens in @crewhaus/memory-service's wireDream / runDreamBootCatchUp / createDreamJanitorStep; the user surface is crewhaus dream run|status|init.