open-index/open-npm huggingface dataset:
npm package: @faramesh/cli
Description: AI agent execution control. Policy-driven governance for every tool call.
Latest version: 1.2.3

# faramesh

AI agent execution control. Policy-driven governance for every tool call.

## Install

```bash
npx faramesh@latest init
```

Or install globally:

```bash
npm install -g faramesh
```

## What it does

Faramesh sits between your AI agent and the tools it calls. Every tool call is checked against your policy before it runs.

- **Permit** — the rule said yes, the action runs
- **Deny** — blocked, nothing runs, the agent is told why
- **Defer** — held for a human to approve or deny

## Quick start

```bash
faramesh run python agent.py
```

## Learn more

- [Documentation](https://faramesh.dev/docs)
- [GitHub](https://github.com/faramesh/faramesh-core)
npm package: @faramesh/openclaw
Description: Faramesh governance plugin for OpenClaw — policy-based Allow/Ask/Deny for every tool call, human approval workflows, and full audit logging.
Latest version: 0.1.4

# Faramesh plugin for OpenClaw

**npm package:** `@faramesh/openclaw` · **Plugin id:** `openclaw`

Governance for every tool call: **Allow**, **Ask** (human approval), or **Deny** — enforced at the code level before execution, immune to prompt injection.

## Install

```bash
openclaw plugins install @faramesh/openclaw
```

Then add `openclaw` to `plugins.allow` in your OpenClaw config.

No other config needed if Faramesh runs at `http://127.0.0.1:8000`. To point at a different server:

```yaml
plugins:
  allow:
    - openclaw
  entries:
    openclaw:
      config:
        base_url: "http://your-faramesh-server:8000"
        api_key: "your-api-key"   # optional
```

You can also set `FARAMESH_BASE_URL` and `FARAMESH_API_KEY` as environment variables instead.

## What it does

Before every tool call (bash, file, browser, network, etc.) the plugin submits the action to Faramesh (`POST /v1/actions`). Every call is recorded in the Faramesh dashboard. The outcome is one of:

| Outcome | What the agent sees |
|---|---|
| **Allow** | Nothing — the tool runs. |
| **Pending approval** | `[Faramesh PENDING]` — waits for a human to approve in the dashboard. |
| **Denied by policy** | `[Faramesh DENY]` — blocked by a policy rule. |
| **Denied by human** | `[Faramesh DENY]` — a human denied it in the dashboard. |
| **Service unreachable** | `[Faramesh ERROR]` — fail-closed, tool does not run. |

The included **skill** teaches the agent how to explain each outcome to the user and where to approve or change policy.

## Requirements

- OpenClaw (gateway or TUI)
- Faramesh server — [Horizon (managed)](https://faramesh.dev) or [self-hosted](https://faramesh.dev/docs/installing-faramesh)
npm package: @faranglao/sv-prod
Description: A library for Svelte web applications, improving safety using HTTP Response Headers
Author: Kevin Obee
Latest version: 0.0.1

# sv-prod library

A Svelte library that adds some of the bits you will need in production environments.

## Getting Started

```bash
# add the package to your project
npm install -d @faranglao/sv-prod
```

## Add HTTP Security Response Headers

Add the `ServerHookSecurityHeaders` server hook.

```ts
// src/hooks.server.ts
import { ServerHookSecurityHeaders } from '@faranglao/sv-prod';

export const handle = ServerHookSecurityHeaders().handle;
```

Your application will now return the following HTTP security response headers:

```http
permissions-policy: geolocation=(), camera=(), microphone=()
referrer-policy: strict-origin-when-cross-origin
x-content-type-options: nosniff
x-frame-options: DENY
x-xss-protection: 1; mode=block
```

Note: The `x-sveltekit-page` header will have been removed from the HTTP response to prevent unnecessary information disclosure.

Check the security headers and best practices of your website with [Mozilla Observatory](https://observatory.mozilla.org/) or [Security Headers](https://securityheaders.com/) 🧪