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

crobe-sdk

v0.5.0

Published

Crobe (Compliance Probe) is a CLI tool for running compliance checks through flexible playbooks. This package contains the TypeScript type definitions to facilitate playbook authoring and integration.

Readme

crobe-sdk 🛡️

TypeScript type definitions for Crobe, a CLI tool written in Go for running compliance checks on a system.

This package provides types for three separate stages of the compliance lifecycle:

  • Playbook Inline JS/TS Development: Types for writing script logic (Generators, Evaluators, Gatherers) inlined in a playbook.
  • Playbook Definition: Types for defining the entire playbook structure.
  • Report Consumption: Types for parsing and validating the JSON reports generated by the agent.

📥 Installation

npm install crobe-sdk

🚀 Usage

1. Playbook Script Logic (crobe-sdk/func)

Use these types when writing external .ts or .js scripts that will be baked into a playbook.

import { ScriptContext } from 'crobe-sdk/func';

/**
 * Generate a dynamic shell command based on the environment.
 */
export default ({ os }: ScriptContext) => {
  return os === 'windows' ? 'dir' : 'ls -la';
};

2. Full Playbook Definition (crobe-sdk/playbook)

Use these types if you are generating playbooks dynamically (e.g., via a web app or server-side script).

import { Playbook } from 'crobe-sdk/playbook';

const playbook: Playbook = {
  title: "Cloud Security Hygiene",
  sections: [
    {
      title: "Identity & Access",
      description: ["Verify IAM best practices"],
      assertions: [
        /* ... */
      ]
    }
  ]
};

3. Result Consumption (crobe-sdk/submission)

Use these types when building a "Central Hub" or dashboard that parses the reports submitted by agents.

import { FinalReport, RemoteSubmission } from 'crobe-sdk/submission';

function handleSubmission(payload: RemoteSubmission) {
  const report: FinalReport = JSON.parse(atob(payload.json));
  console.log(`Report from ${report.username} on ${report.os}`);
}

📝 JSON Schema Validation

For the best developer experience when writing playbooks manually in YAML or JSON, you can use the JSON schema included in this package.

Alternatively, you can use the schema from latest release https://github.com/benedictjohannes/crobe/releases/latest/download/playbook.schema.json.

VS Code (YAML Extension)

Add the following line to the top of your playbook.yaml file:

# yaml-language-server: $schema=node_modules/crobe-sdk/playbook.schema.json
title: My Playbook
...

This will enable auto-completion, hover documentation, and real-time validation for your playbook structure.

⚖️ License

MIT