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

@octaviaflow/oflow-templating

v0.0.1

Published

Flow ↔ .oflow mapping: export a workflow to a portable .oflow (credentials split into the encrypted secrets) and import one back (ids remapped, secrets re-installed). App-agnostic.

Readme

@octaviaflow/oflow-templating

Flow ↔ .oflow. Turns a live OctaviaFlow workflow into a portable, signed, encrypted .oflow (credentials split out into the encrypted secrets) and rebuilds it on import (ids regenerated, refs rewired, creds re-installed).

Built on @octaviaflow/oflow. App-agnostic — the only app-specific bits are two callbacks you provide.

Status: v0. Depends on @octaviaflow/oflow v0 (which itself needs a security review before production). The graph shape is permissive but tuned to the OctaviaFlow { id, name, steps, connections } workflow model.


Export

import { exportFlow, generateSigningKeyPair, generateRecipientKeyPair } from '@octaviaflow/oflow-templating';

const bytes = await exportFlow(flow, {
  manifest: { name: flow.name, version: '1.0.0', author: 'octaviaflow' },
  sign: signingKey.privateKey,                                  // provenance
  keyWrap: { type: 'x25519', recipients: [recipientPubKey] },   // who may open it
  // YOU provide: pull the real creds for the connector refs the package found.
  resolveSecrets: async (refs) => {
    const out: Record<string, unknown> = {};
    for (const id of refs) out[id] = await db.getConnectorCredentials(id);
    return out;
  },
});
await Bun.write('my-flow.oflow', bytes);

exportFlow scans the flow for connector references (default keys: connectorId, connectorInstanceId, connectionId — overridable), calls your resolveSecrets, strips instance/runtime fields (organizationId, _id, status, …), then signs + encrypts via the core.

Import

import { importFlow } from '@octaviaflow/oflow-templating';

const { flow, manifest, connectorIdMap, stepIdMap } = await importFlow(bytes, {
  unwrap: { type: 'x25519', privateKey: recipientPrivKey },
  trustedSigners: [signingKey.publicKey],          // reject unknown signers
  // YOU provide: re-create connectors from the secrets, return old -> new ref map.
  installSecrets: async (secrets) => {
    const map: Record<string, string> = {};
    for (const [oldId, cred] of Object.entries(secrets)) {
      map[oldId] = await db.createConnectorInstance(cred);   // new id
    }
    return map;
  },
});
// `flow` has fresh step/flow ids, connections + parentId rewired, and connector
// refs pointing at the NEW connector instances. Save it as a new workflow.

What the package owns vs. what you own

| Owns (pure, app-agnostic) | You provide (data access) | |--------------------------------------------|----------------------------------| | scan flow → connector refs | resolveSecrets(refs) | | strip runtime/env fields | installSecrets(secrets) → map | | sign + encrypt / verify + decrypt (core) | | | regenerate ids; rewire connections/parentId| | | rewrite connector refs old → new | |

Known v0 limitations

  • Data-ref tokens inside step config strings (e.g. {{stepId.path}}) are not remapped to the new step ids yet — only connections, parentId, and the configured connector-ref keys are. If your flows use cross-step token refs, add a token remap pass (or pass regenerateIds: false and remap in the app).
  • No schema version migration between flow versions yet.