@imqueue package status — versions, licences and Node requirements

Every published @imqueue package, with the facts you would otherwise go to npm for. The numbers below come from the npm registry, read when this page was built — not from a checkout, and not from anything written by hand.

There is a machine-readable copy of this exact data at imqueue.org/status.json, and this page is also served as plain markdown at imqueue.org/status.md. If you are an agent, take the JSON: it carries the install command, the docs URL and the repository for each package as well as what the table shows.

The framework

Every package is published under the same licence. A closed-source product needs the commercial licence instead; that is one arrangement covering the whole framework, not a per-package question.

The packages

Install any of them with npm i <name> — except @imqueue/cli, which is a command-line tool and wants npm i -g @imqueue/cli.

Two pairs are mutually exclusive: pick either @imqueue/pg-prisma or @imqueue/pg-sequelize for the database toolkit, and either @imqueue/opentelemetry or @imqueue/datadog for tracing. Installing both halves of a pair fails silently rather than loudly. The API reference states the choosing rule for each.

What each package is for

• @imqueue/core — The JSON messaging-queue engine, the IMQ factory, and the pluggable adapter interface.
• @imqueue/rpc — Services, clients and decorators — @expose, @remote, @lock, @cache — and the RPC runtime.
• @imqueue/pg-pubsub — Reliable PostgreSQL LISTEN/NOTIFY with inter-process lock support.
• @imqueue/pg-cache — PostgreSQL-managed cache on Redis for @imqueue service methods.
• @imqueue/tag-cache — Tagged cache implementation over Redis.
• @imqueue/pg-sequelize — Turns a query described as data — filters, paging, ordering and the requested fields — into one efficient Sequelize statement, with database views as models.
• @imqueue/pg-prisma — Prisma query extensions — soft-delete, access scoping, authorship and audit trails derived from the emitted contract — plus row archiving and change-notify triggers.
• @imqueue/async-logger — Non-blocking logger over winston, with file and HTTP transports configured from the environment.
• @imqueue/opentelemetry — OpenTelemetry instrumentation for @imqueue/rpc — every RPC traced, with no changes to service or client code.
• @imqueue/datadog — Datadog APM tracing for @imqueue/rpc — a drop-in replacement for Datadog's own dd-trace package that traces every RPC.
• @imqueue/graphql-dependency — Declarative cross-service dependency loading for GraphQL — nested data in bulk instead of one call per resolved object.
• @imqueue/type-graphql-dependency — The same dependency loading for type-graphql — declared on your decorated classes rather than on raw GraphQL types.
• @imqueue/net — CIDR membership testing for IPv4 and IPv6 — sorted binary ranges searched in O(log n) rather than one comparison per network.
• @imqueue/http-protect — Per-IP rate limiting and banning for express-like servers, backed by Redis so every process sees one view of a client.
• @imqueue/validation — Zod-backed field- and method-level validation via native (TC39) decorators.
• @imqueue/job — Safe-by-default Redis job queue — delayed and scheduled jobs, at-least-once delivery, and retries driven by the handler.
• @imqueue/cli — Scaffolds services, generates typed clients, and runs a local fleet — the entry point.
• @imqueue/mcp — The Model Context Protocol server: these docs as tools, over stdio or the hosted endpoint.