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

@pmcollab/coworkstream-details

v6.0.0

Published

Rich category templates and reusable building blocks for @pmcollab/coworkstream.

Readme

@pmcollab/coworkstream-details

Rich category templates and reusable building blocks for @pmcollab/coworkstream.

Two kinds of exports. Read this before you depend on anything from this package.

Category templates — fork-friendly, NOT a stable API

DecisionDetails, PreparedDetails, SignalDetails, DraftDetails, ConsolidatedDetails, AuditDetails, IncidentDetails.

These are rich starting points designed to be forked into your codebase. Behavior, layout, and props will evolve across major versions. Don't deep-import or wrap them in production paths you can't easily update.

The recommended adoption pattern is:

  1. npm install @pmcollab/coworkstream-details.
  2. Try the components via renderDetailsByCategory.
  3. Once you know which 1-3 you want to keep, copy them into your repo (src/components/details/ContosoDecision.jsx) and rename. You now own them; we can't break you.

See FORKING.md for the full pattern.

Building blocks — stable API

MultiAgentPositions, RiskAssessment, SimilarPastDecisions, VisibleReasoning, AgentLearning, DecisionFeedback, EditableParameters, WcosAlert.

These are depended-on sub-components that the templates compose internally. They're props-driven, fully decoupled, and follow semver. Safe to import directly long-term — they're how a forked ContosoDecision keeps using our work even after diverging the wrapper.

Quick start

import { WorkStream } from '@pmcollab/coworkstream'
import { renderDetailsByCategory } from '@pmcollab/coworkstream-details'

<WorkStream items={items} renderDetails={renderDetailsByCategory} />

Use building blocks directly

import {
  MultiAgentPositions,
  RiskAssessment,
  WcosAlert,
} from '@pmcollab/coworkstream-details'

function MyCustomDetails({ item }) {
  return (
    <>
      <WcosAlert verdict={item.meta.wcos?.verdict} reasons={item.meta.wcos?.reasons} />
      {item.isMultiAgent && <MultiAgentPositions multiAgent={item.multiAgent} />}
      {item.meta.risk && <RiskAssessment risk={item.meta.risk} item={item} />}
    </>
  )
}

What's in _fork-stubs.js?

The templates reference Zustand-style hooks and a toast library. The package ships with no-op stubs in src/_fork-stubs.js so the components render without runtime errors when consumed as-is. Fork the components or shadow this module to wire your real state and notifications. See FORKING.md.

Peer dependencies

  • react >=18
  • @pmcollab/coworkstream >=0.1
  • framer-motion >=10 (used by some animated panels)

License

Commercial. See LICENSE in the repository root.