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

@cloudhal/agent-runtime

v0.6.2

Published

Cloudhal agent runtime: policy engine (actors, scopes, approvals), skill loader, audit log

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

madrakamadraka

Keywords

Readme

@cloudhal/agent-runtime

What governs agents — no MCP SDK in here (ADR-0011).

  • PolicyEngine — evaluate(principal, tool, { confirmed }) → allow | deny | approval-required. Checks the principal's scopes against the tool's scopes, limits a call to the scopes of the skill the principal declared, and requires approval for tools marked requiresApproval, annotated destructiveHint, or listed in the skill's cloudhal.approval. defaultScopes(actor): humans/system get *; agents get reading, content writes, previews and uploads, never publish or rollback (the exact list is in the function).
  • loadSkill(dir) / loadSkills(root) — SKILL.md frontmatter validated against the skill-manifest contract; Cloudhal data in flat metadata keys (cloudhal.schemaVersion, cloudhal.requiresCapabilities, cloudhal.scopes, cloudhal.approval). Bodies and references/*.md are read lazily (progressive disclosure).
  • AuditLog — append-only audit table (migration 0003_agent): who (actor), what (tool, input), decision + reason, skill, outcome, snapshot id, duration.

Scopes (src/policy.ts, RFC-0005 §1) are the single list the engine, REST, MCP and Studio use:

  • KEY_SCOPES — what an agent key may carry (site, content, preview, publish, rollback, assets, analytics, comments, schedules and releases, several with an :own variant limited to one's own nodes);
  • PERSON_SCOPES — held only by people through their role, never stored on a key (members, settings, agents, audit, commenter data, automations, in-editor AI);
  • * — every scope. implies(a, b) follows the lattice (content:write → content:write:own → content:draft:own → content:propose, site:publish → releases:publish, …).

Roles (src/roles.ts, RFC-0005 §2, ADR-0018): ROLES (Owner > Administrator > Editor > Author > Contributor) and ROLE_SCOPES map each role to scopes; a key never holds more than its creator's role (narrow), and modeCap caps its mode (edits for Contributors, auto otherwise).