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

@lifeops/core

v0.1.0

Published

Secondary builder SDK for Life Ops primitives like connectors, agenda composition, and structured project sharing.

Readme

@lifeops/core

@lifeops/core is the installable JavaScript SDK for Life Ops.

Most users do not need this package first.

If you want the main install path, use the sibling lifeops package in packages/lifeops-cli. Reach for @lifeops/core only when you specifically want to embed Life Ops primitives inside another codebase.

It gives other codebases a small, connector-based surface for:

  • pulling important signals from their own data feeds
  • normalizing those signals into a shared Life Ops item model
  • composing a week agenda for agent workflows
  • drafting structured project-share emails and follow-ups
  • handing email drafts to any transport layer they already trust

Install

npm install @lifeops/core

For local development from this repo:

npm install ./packages/life-ops-core

Quick example

import {
  LifeOpsClient,
  createStaticConnector,
  buildProjectSharePacket,
  renderAgendaText,
} from "@lifeops/core";

const client = new LifeOpsClient({
  connectors: [
    createStaticConnector({
      name: "calendar",
      items: [
        {
          id: "demo-sync",
          kind: "event",
          title: "Founder sync",
          startsAt: "2026-03-26T15:00:00.000Z",
          endsAt: "2026-03-26T16:00:00.000Z",
          priority: "high",
          organization: "Life Ops",
        },
      ],
    }),
  ],
});

const agenda = await client.agenda({
  now: "2026-03-26T00:00:00.000Z",
  days: 7,
  timezone: "America/Chicago",
});

console.log(renderAgendaText(agenda));

const sharePacket = buildProjectSharePacket({
  project: {
    name: "Life Ops",
    summary: "A local-first operating system for important human data and action loops.",
    whyNow: "The project is ready to share with a few high-context collaborators.",
    highlights: [
      "Normalizes inbox, calendar, and records into one action layer.",
      "Lets an agent draft and follow through on operational outreach.",
    ],
    proofPoints: [
      "Full Gmail archive and attachment corpus ingestion.",
      "Canonical profile memory and alert surfaces.",
    ],
    links: [
      { label: "Repo", url: "https://github.com/example/life-ops" },
    ],
  },
  recipients: [
    {
      name: "Alicia",
      email: "[email protected]",
      whyRecipient: "You care about agent-native personal software and sharp product framing.",
      ask: "If it resonates, I'd love a short reaction and one intro that feels obvious to you.",
    },
  ],
  senderName: "Cody",
});

console.log(sharePacket.drafts[0].text);

API surface

Connectors

  • defineConnector
  • createStaticConnector
  • collectItems
  • LifeOpsClient

Agenda

  • normalizeItem
  • normalizeItems
  • composeAgenda
  • renderAgendaText

Email and project sharing

  • draftStructuredEmail
  • renderEmailText
  • renderEmailHtml
  • sendEmailDraft
  • draftProjectShareEmail
  • buildProjectSharePacket
  • createProjectShareFollowUpItem

Email sending

@lifeops/core does not force a mail provider.

Instead, sendEmailDraft expects a sender object with a send(payload) method, which lets you plug in resend, nodemailer, postmark, or your own queue.

await sendEmailDraft({
  draft,
  sender: {
    async send(payload) {
      return resend.emails.send({
        from: "[email protected]",
        to: payload.to.map((recipient) => recipient.email),
        subject: payload.subject,
        text: payload.text,
        html: payload.html,
      });
    },
  },
});