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

@lore-co/sdk

v0.1.4

Published

Typed HTTP client for Lore engineering memory

Readme

@lore-co/sdk

The customer library for applications and integrations that call Lore programmatically. It provides a typed client for learnings, activity, audited context delivery, observations, and turns.

Install

pnpm add @lore-co/sdk
import { LoreClient } from "@lore-co/sdk";

const lore = new LoreClient({
  baseUrl: process.env.LORE_API_URL!,
  headers: {
    authorization: `Bearer ${process.env.LORE_WORKSPACE_TOKEN!}`,
  },
});

const result = await lore.processTurn({
  connector: "incident-bot",
  eventId: "incident-42:reply-3",
  agent: "incident-bot",
  sessionId: "incident-42",
  previousAssistant: { content: "Restart the service." },
  currentUser: { content: "No, fail over first." },
}, "incident-42:reply-3");

observeEvent calls POST /v1/observations; deliverContext calls audited POST /v1/context/deliveries; and processTurn calls POST /v1/turns and forwards the optional idempotency key. The client also exposes learning inspection and lifecycle methods, activity listing, workspace-token management, and Devin session registration. observe, getContext, and the memory-named methods remain available for compatibility.

Use @lore-co/adapter-generic instead when the customer owns an agent runtime and wants a higher-level prepare/observe bridge. CLI users should install @lore-co/cli globally; they do not need this package.

Production guidance

  • Use an HTTPS API URL and keep workspace tokens in server-side secrets.
  • Reuse stable connector, event, and session IDs when retrying requests.
  • Handle LoreApiError for non-2xx responses and log its status without exposing credentials.

Node.js 22 or newer is required. See the technical guide for the complete API surface.