contentrain-serve — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited contentrain-serve (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
contentrain serveStart the local review UI as a bridge between agent and developer.
Use this when:
Before starting a new instance, check if port 3333 is already in use:
lsof -ti:3333If a process is running, serve is already up — skip to Step 3.
Run from the project root (where .contentrain/ lives):
contentrain serveOptional flags:
--port (default: 3333)--host (default: localhost)--open=false (prevent auto-opening browser)--stdio (MCP stdio transport for IDE integration — no web UI)Wait for the "Contentrain Serve" banner confirming the server is ready.
Based on the current context, tell the developer exactly where to go:
| Context | URL | What to do |
|---|---|---|
| Normalize plan ready | http://localhost:3333/normalize | Review extractions, approve or reject |
| Pending branches | http://localhost:3333/branches | Review and merge branches |
| Validation issues | http://localhost:3333/validate | Inspect errors and warnings |
| Content browsing | http://localhost:3333/content | Browse entries and models |
| General overview | http://localhost:3333 | Dashboard with project stats |
After directing the developer to the UI:
.contentrain/normalize-plan.json — if deleted, check for new branches to determine approve vs rejectThe UI communicates back through filesystem changes (plan files, branches, context.json). Poll these to detect the developer's decision.
After the developer acts in the UI:
Do NOT leave the developer hanging — always follow up after UI interaction.
The serve UI is a monitoring + approval surface, not an action trigger:
All mutations (create, edit, delete, scan, fix, normalize) are agent-driven via MCP tools. The UI never triggers these directly.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.