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

@krynix/policy

v0.2.1

Published

Policy evaluation engine for Krynix: YAML policy parsing, rule matching, and trace evaluation

Readme

@krynix/policy

Policy evaluation engine for Krynix — YAML policy parsing, rule matching, and trace evaluation with deterministic CI exit codes.

Install

npm install @krynix/policy

Key Exports

  • evaluate(trace, policy) — evaluate a trace against a policy, returns verdict + violations
  • matchRule(event, rule) — match a single event against a rule
  • parsePolicy — parse a YAML policy file into a typed Policy object

Usage

import { evaluate, parsePolicy } from "@krynix/policy";
import { readTrace } from "@krynix/core";

const events = await readTrace("/path/to/trace.jsonl");
const policy = parsePolicy(`
  apiVersion: krynix.dev/v1
  kind: Policy
  metadata:
    name: no-shell-exec
    version: "1.0"
    description: Block shell command execution
  spec:
    scope:
      agents: ["*"]
      event_types: ["tool_call"]
    rules:
      - id: block-shell
        description: Deny shell tool calls
        match:
          event_type: tool_call
          payload:
            - field: tool_name
              operator: eq
              value: shell_exec
        action: deny
        severity: error
        message: "Shell execution is not permitted"
`);

const result = evaluate(events, policy);
// result.verdict: "pass" | "fail" | "require-approval"
// result.exitCode: 0 (pass), 1 (error), 2 (critical), 3 (require-approval)
// result.violations: array of matched deny/require-approval rules

Evaluation Semantics

  • First-match-wins: for each event, the first matching rule determines the outcome. Order your rules from most specific to most general.
  • Scope filtering: events outside scope.agents / scope.event_types are skipped entirely.
  • Deterministic exit codes: same trace + same policy always produces the same result.

Operators

| Operator | Description | Example Value | |----------|-------------|---------------| | eq | Strict equality | "shell_exec" | | neq | Strict inequality | "shell_exec" | | in | Value is in array | ["shell_exec", "bash"] | | not_in | Value is not in array | ["shell_exec", "bash"] | | matches | Regex match (Unicode) | "^(shell\|bash\|exec).*" | | contains | Substring search | "shell" | | exists | Field is present and non-null | true or false |

Exit Codes

| Code | Meaning | |------|---------| | 0 | Pass — no CI-failing violations | | 1 | Error-severity violation or runtime error | | 2 | Critical-severity violation | | 3 | Requires approval — no CI-failing violations but approval needed |

Rule Types

  • Per-event rules: Match individual events based on event_type and payload field conditions.
  • Sequence rules: Match patterns across multiple events in a session (e.g., "tool_call followed by tool_call without an intervening llm_request").

License

Apache 2.0