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

@pyrfor/engine

v0.4.0

Published

Pyrfor Engine — open runtime core: Memory, Skills, Provider Router, MCP-server, Heartbeat, Tool Engine

Vulnerabilities

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

Links

Maintainers

alexgrebeshok-coderalexgrebeshok-coder

Keywords

Readme

@pyrfor/engine

Pyrfor Engine — canonical local-first runtime for Pyrfor.app and optional integration surfaces.

License: Apache 2.0 Status: Runtime consolidation — packages/engine/src/runtime is the desktop runtime boundary.

What lives here

| Module | Description | |--------|-------------| | src/ai/ | Provider Router (OpenRouter, ZAI, OpenAI, GigaChat, YandexGPT) | | src/memory/ | Bounded Memory 5KB + GBrain (FTS5 + Ollama embeddings) | | src/orchestration/ | Agent orchestration: Plan→Decompose→Delegate→Verify | | src/skills/ | MCP-server + skill registry | | src/auth/ | Telegram OAuth + email auth (base only; tenant logic in business) | | src/db/ | Prisma client adapter for engine models | | src/voice/ | Base ASR/TTS (voice-profile per-user → ochag) | | src/transport/ | SSE, Telegram bot client, notifications | | src/utils/ | Shared utilities (date, logger, rate-limit, etc.) | | src/observability/ | Sentry, monitoring, structured logging | | src/billing/ | Stars / ЮKassa / TON integrations; entitlements API | | src/policy/ | Privacy tiers: Public / Personal / Vault | | src/trust/ | Audit log, undo, «почему?», privacy badge | | src/mcp/ | MCP server (agentskills.io compatible) | | src/runtime/ | Canonical Pyrfor.app sidecar runtime: gateway, sessions, memory, tools, MCP bridges, health, CLI |

Architecture Rule

Engine has no dependencies on product packages.

engine ← business
engine ← ochag
engine ← freeclaude
engine ← ui

This is enforced by eslint-plugin-boundaries in CI.

apps/pyrfor-ide consumes the engine through the bundled sidecar and HTTP/SSE/WebSocket runtime contracts. The root daemon/ directory is a compatibility/service wrapper and must not become a second desktop backend.

Development

# From workspace root
pnpm --filter @pyrfor/engine dev

# Type check
pnpm --filter @pyrfor/engine typecheck

# Tests
pnpm --filter @pyrfor/engine test

Runtime contract

  • Default config: ~/.pyrfor/runtime.json
  • CLI entrypoint: packages/engine/bin/pyrfor.cjs
  • Desktop sidecar: built by apps/pyrfor-ide/scripts/build-sidecar.sh
  • Compatibility inputs such as .openclaw and .ceoclaw paths are migration-only and must not define the desktop first-run path.