OpenINF is an open source community building tools that help developers aggregate, curate, disseminate, and apply information.

Every package, every page of documentation, and the discussion around both are public. It is early, and most of what this becomes is still open to argument.

OpenINF SDK Q4 2026

Packages
10
Already on npm
6 since April 2022
Never published, joining them
4
Carry no third-party runtime dependency
9 of 10
Builds per package, both typed
2 CJS and ESM

Ten small TypeScript packages for the unglamorous middle of Node.js work

None of it is the interesting part of your program. All of it is the part you end up writing again on every project.

  1. 01

    Type guards and argument validation

    Narrow unknown input, and reject what does not belong.

  2. 02

    Structured errors

    Errors with structure behind them, not just a message.

  3. 03

    Object and array helpers

    The small operations you keep rewriting.

  4. 04

    Terminal-friendly text

    Text that behaves itself in a terminal.

Plus a couple of things that fit nowhere else.

Install Not yet published
$ npm install @openinf/…

The ten ship together in Q4 2026, and package names are announced at release. Six already live on npm under the @openinf scope, in TypeScript with type declarations from the start.

How we work

Vision
  • Contributing

    How issues get claimed, what makes a pull request easy to merge, and the sign-off every contribution carries.

  • Good first issues

    Open issues across the organisation marked as suitable to pick up. See also help wanted.

  • Style handbook

    The house style our documentation and commit messages follow.

  • Code of Conduct

    Respect people, their identities, their culture, and their work. Listen before responding.

  • Support

    Where to ask, in the order worth trying.

  • Security

    How to report a vulnerability privately.

Elsewhere: @OpenINF on X. A Matrix room exists but is mostly defunct in favour of Discord.