pip install cognis-cspbuilder
cspbuilder scan .            # → prioritized findings in seconds

🔎 Example output

Real, reproducible output from the tool — runs offline:

$ cspbuilder-emit --version
cspbuilder 0.1.0

$ cspbuilder-emit --help
usage: cspbuilder [-h] [--version] [--format {table,json}] {build,audit} ...

Generate and audit a Content-Security-Policy from page resources.

positional arguments:
  {build,audit}
    build               scan an HTML page and emit a least-privilege CSP
    audit               audit an existing CSP for weaknesses

options:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  --format {table,json}
                        output format (default: table)

Blocks above are real cspbuilder output — reproduce them from a clone.

Sample result format (illustrative values — run on your own data for real findings):

{
"findings": [
    {
        "id": "1234567890",
        "title": "Suspicious Network Activity",
        "description": "Possible malicious activity detected on network segment 192.168.1.0/24",
        "created_by": "cspbuilder",
        "created_at": "2023-02-20T14:30:00Z",
        "updated_at": "2023-02-20T14:30:00Z"
    }
]
}

Usage — step by step

1. Install the CLI (Python 3.9+):

   pip install cspbuilder     # or: pip install .   from a checkout
   

2. Build a least-privilege policy — the build subcommand scans an HTML page and emits a Content-Security-Policy header:

   cspbuilder build page.html --url https://app.example.com
   

3. Audit an existing policy for weaknesses — pass a file or an inline header string:

   cspbuilder audit policy.txt
   cspbuilder audit --policy "default-src 'self'; script-src 'unsafe-inline'"
   

4. Read the result via exit code: 0 = clean / no actionable findings, 1 = HIGH/MEDIUM weaknesses (or a policy still permitting inline), 2 = usage error. Use --format json to capture the generated header:

   cspbuilder build page.html --url https://app.example.com --format json | jq -r .header
   

5. Gate CI on CSP hygiene — fail the build when a policy regresses:

   cspbuilder audit policy.txt || echo "CSP weaknesses detected"
   

Contents

• Why cspbuilder? · Features · Quick start · Example · Architecture · AI stack · How it compares · Integrations · Install anywhere · Related · Contributing

Why cspbuilder?

ship a real CSP

cspbuilder is single-purpose, scriptable, and self-hostable: point it at a target, get prioritized results in the format your workflow already speaks (table · JSON · SARIF), gate CI on it, and let agents drive it over MCP.

Features

• ✅ Extract Resources
• ✅ Build Policy
• ✅ Policy To Header
• ✅ Parse Policy
• ✅ Audit Policy
• ✅ Runs on Linux/macOS/Windows · Docker · devcontainer
• ✅ Ports in Python, JavaScript, Go, and Rust (ports/)

Quick start

pip install cognis-cspbuilder
cspbuilder --version
cspbuilder scan .                       # scan current project
cspbuilder scan . --format json         # machine-readable
cspbuilder scan . --fail-on high        # CI gate (non-zero exit)

Example

$ cspbuilder scan .
  [HIGH    ] CSP-001  example finding             (./src/app.py)
  [MEDIUM  ] CSP-002  another signal              (./config.yaml)

  2 findings · risk score 5 · 38ms

Architecture

flowchart LR
  IN[target / manifest] --> P[cspbuilder<br/>checks + rules]
  P --> OUT[findings (JSON / SARIF)]

Use it from any AI stack

cspbuilder is interoperable with every popular way of using AI:

• MCP server — cspbuilder mcp (Claude Desktop, Cursor, Cognis.Studio, uncensored-fleet)
• OpenAI-compatible / JSON — pipe cspbuilder scan . --format json into any agent or LLM
• LangChain · CrewAI · AutoGen · LlamaIndex — wrap the CLI/JSON as a tool in one line
• CI / scripts — exit codes + SARIF for non-AI pipelines

How it compares

	Cognis cspbuilder	csp-evaluator
Self-hostable, no account	✅	varies
Single command, zero config	✅	⚠️
JSON + SARIF for CI	✅	varies
MCP-native (AI agents)	✅	❌
Polyglot ports (JS/Go/Rust)	✅	❌
Open license	✅ COCL	varies

Built in the spirit of csp-evaluator, re-framed the Cognis way. Missing a credit? Open a PR.

Integrations

Pipes into your stack: SARIF for code-scanning, JSON for anything, an MCP server (cspbuilder mcp) for AI agents, and a webhook forwarder for SIEM/Slack/Jira. See docs/INTEGRATIONS.md.

Install — every way, every platform

pip install "git+https://github.com/cognis-digital/cspbuilder.git"    # pip (works today)
pipx install "git+https://github.com/cognis-digital/cspbuilder.git"   # isolated CLI
uv tool install "git+https://github.com/cognis-digital/cspbuilder.git" # uv
pip install cognis-cspbuilder                                          # PyPI (when published)
docker run --rm ghcr.io/cognis-digital/cspbuilder:latest --help        # Docker
brew install cognis-digital/tap/cspbuilder                             # Homebrew tap
curl -fsSL https://raw.githubusercontent.com/cognis-digital/cspbuilder/main/install.sh | sh

Linux	macOS	Windows	Docker	Cloud
scripts/setup-linux.sh	scripts/setup-macos.sh	scripts/setup-windows.ps1	docker run ghcr.io/cognis-digital/cspbuilder	DEPLOY.md (AWS/Azure/GCP/k8s)

Related Cognis tools

• portfan — Summarize and diff nmap XML into prioritized, attackable findings
• subhunt — Aggregate & dedupe subdomain enumeration from multiple sources
• dirsight — Analyze web content-discovery output (ffuf/gobuster) into ranked endpoints
• jwtinspect — Decode JWTs and lint for alg=none, weak secrets, and missing claims
• corsaudit — Detect permissive/misconfigured CORS from headers or a config
• headerscan — Grade HTTP security headers (CSP/HSTS/XFO) A-F from a response dump

Explore the suite → 🗂️ all 170+ tools · ⭐ awesome-cognis · 🔗 cognis-sources · 🤖 uncensored-fleet · 🧠 engram

Contributing

PRs, new rules, and demo scenarios are welcome under the collaboration-pull model — see CONTRIBUTING.md and SECURITY.md.

⭐ If cspbuilder saved you time, star it — it genuinely helps others find it.

Interoperability

{} composes with the 300+ tool Cognis suite — JSON in/out and a shared OpenAI-compatible /v1 backbone. See INTEROP.md for the suite map, composition patterns, and reference stacks.

License

Source-available under the Cognis Open Collaboration License (COCL) v1.0 — free for personal, internal-evaluation, research, and educational use; commercial / production use requires a license ([email protected]). See LICENSE.

---