Explore public packages
Packages published as public on the Packr registry.
The fleet checks behind one contract: audio intelligibility, content shape, the learning gate, and content URLs. Exposes a CLI (lq-check) and the same checks as an API.
SDK for app-logs, the BlueForge opt-in event lane: a batching producer client for LogEventV1 events and a reader client for events/summary queries. Zero runtime dependencies.
The learning-journey scorecard: pacing, engagement, sufficiency and progress per persona, measured against an app's lesson content and played against a running app, with a regression gate against a committed baseline.
Thin client for gamevault (GAS) generation models fronted by forge-gateway /v1/gas/* — submit, poll, fetch; typed retryable-vs-fatal errors. Design: docs/design/2026-10-20-federation-gamevault-model-gateway.md.
User-audit harness primitives: persona model, runner-parity check, safety rails, environment-noise exclusion, report schema, resumable checkpoints. Pure; browser and HTTP runners come later.
Pure, deterministic audit scoring: penalty/suggestion format, per-dimension baseline compare + gate, markdown scorecard. No I/O.
Sidecar operations for fleet repos: generate promo shots from user flows, capture them light and dark, declare them in blueforge.product.yml and the flow files, check, doctor, and install the package.json scripts
Learner-view smoke test: plays every live (app, language, learner locale) tree the way a learner does and asserts on what is rendered
Framework-agnostic API security guards (bearer/cron secrets, rate limit, origin, ingest caps, SSRF, redirects, access tokens, secret scrubbing) on web-standard Request/Response, with Hono and Next adapters and an api-guard-lint route scanner.
Visual audit core: sidecar, pixel and vision checks for product imagery with one verdict schema (visual-audit/verdict@1) shared by the forge-git correctness gate and the blueforge promotion gate
Pure routing core for AI generation: (domain, artifact, quality) -> an ordered, priced, explainable plan of provider/model candidates. No I/O, no gateway imports.
Content service factory: createContentService with memory, committed-snapshot and marketing-os (CMS read) adapters
CRM service factory: createCrmService with memory and console adapters (contacts, tags, idempotent events); results never throw
Runner-agnostic crash-safe resume for test runs: append-only ledger, fingerprint, planner, interrupted-vs-failed classifier, exit codes
Shared React components every app needs: sheet/dialog (consent, PWA install and legal subpaths follow). React-only peers, props-only copy, CSS-variable theming
React components for the support-os integration: a Contact support button (ticket dialog with app context), help-center deep links and a ticket status badge
Declarative promo screenshots: a *.shots.yml interpreter, deterministic light/dark capture, a pixel gate, and a push to the BlueForge asset store
A knowledge graph of a repo's BlueForge sidecar family (product, features, feature specs, user and data flows, roadmap, desks, plan rows): build it, query it, merge it across repos. Pure functions plus a CLI; reads files, calls nothing.
Provider-agnostic image→3D client: typed requests, job polling, GLB contract validation
SDK for app-dev-db, the BlueForge readings store: a producer client to push test.run / audit.score / flows.verify readings and a reader client for catalog, latest, series and runs. Zero runtime dependencies.