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

@opengeni/codemode

v0.4.4

Published

Attempt-frozen programmatic tool catalog and execution authority for OpenGeni.

Readme

@opengeni/codemode

OpenGeni's canonical attempt-frozen programmatic tool surface. It compiles one catalog from the exact tools admitted to an execution attempt and dispatches both model MCP calls and sandbox Codemode calls through the same opaque tool identities and executors.

The package owns deterministic catalog projection, collision-safe JavaScript paths, catalog digests, stale-catalog fencing, approval classification, and result-shape preservation. It does not discover MCP servers, resolve credentials, persist attempts, or bypass host authorization; callers provide the already-admitted definitions and one authorization hook.

modelName and codemodePath are projections only. Execution authority is always the exact { serverId, toolName } identity in the frozen catalog.

Inside an OpenGeni sandbox the worker supplies OPENGENI_CODEMODE_URL and a renewed bearer file. The package exposes one lazy namespace over that exact attempt catalog:

import { tools } from "@opengeni/codemode";

const sessions = await tools.opengeni.sessions_list({ status: "running" });
const hits = await tools.slack.search({ query: "release blocker" });

Generate digest-pinned project declarations from the live attempt catalog with ogtool declarations opengeni-codemode.d.ts. Runtime schema validation remains authoritative when a script outlives a catalog generation.

The bearer is reread for every request. Namespace paths are resolved against the signed catalog and never parsed into authority from flattened model names. For Browser/Computer work, the authored facade wraps those same atomic entries:

import { openGeni } from "@opengeni/codemode";

const browser = await openGeni.browsers.open({ initialUrl: "http://127.0.0.1:3000" });
const tab = await browser.tabs.selected();
await tab.getByRole("button", { name: "Save" }).click();

const computer = await openGeni.computers.open();
const app = await computer.apps.focused();
await app.getByRole("button", { name: "1" }).invoke();

Both surfaces return the same durable tool receipts. Human approval, catalog generation, operation idempotency, and outcome-unknown behavior remain enforced by the shared attempt executor.

Editable artifacts use the same path. The object remains in OpenGeni; files are only explicit import/export boundaries:

import { openGeni } from "@opengeni/codemode";

const workbook = await openGeni.artifacts.create("spreadsheet", "Forecast");
const sheetId = openGeni.artifacts.ids.stable();
await workbook.apply([
  { kind: "sheet.create", sheetId, name: "Inputs", after: null },
  {
    kind: "cells.set",
    sheet: { kind: "created-in-batch", sheetId, createCommandIndex: 0 },
    anchor: { row: 0, column: 0 },
    rows: 2,
    columns: 2,
    cells: ["Metric", "Value", "Revenue", 120],
  },
]);