JSPM

AI-powered application security platform for developers.

shipsafecli.com

22 security agents. 80+ attack classes. One command.

Ship Safe v8.0.0 is an AI-powered security platform that runs 22 specialized agents in parallel against your codebase — covering secrets, injection vulnerabilities, auth bypass, SSRF, supply chain attacks, memory poisoning, Hermes Agent security, Supabase RLS, Docker/Terraform/Kubernetes misconfigs, CI/CD pipeline poisoning, LLM/agentic AI security, MCP server misuse, RAG poisoning, PII compliance, vibe coding patterns, exception handling, Claude Managed Agent configs, and more. Full OWASP Agentic AI Top 10 mapping (ASI-01–ASI-10) enriches every finding. Live OSV.dev advisory feed surfaces actively exploited CVEs within hours of disclosure. OWASP 2025 scoring with EPSS exploit probability. LLM-powered deep analysis verifies exploitability of critical findings. Secrets verification probes provider APIs to check if leaked keys are still active.

v8.0.0 highlights: Ship Safe × Hermes Agent — two new agents purpose-built for NousResearch Hermes Agent deployments. HermesSecurityAgent detects 17 attack patterns across the full OWASP Agentic AI Top 10 surface: tool registry poisoning, function-call injection, goal/plan hijacking, memory layer attacks, skill permission drift, and multi-agent trust boundary violations. AgentAttestationAgent catches supply-chain failures in agent manifests: unpinned versions, missing integrity hashes on remote tool sources, unsigned manifests, and dynamic require() of manifests from env vars. Both agents integrate into the --agentic loop for automated scan → annotate → re-scan cycles. Ship Safe is now a first-class Hermes citizen via skills/ship-safe-security.md and registerWithHermes().

Documentation | Blog | Pricing

Quick Start

# Full security audit — secrets + 22 agents + deps + remediation plan
npx ship-safe audit .

# LLM-powered deep analysis (Anthropic, OpenAI, Google, Ollama, Gemma 4)
npx ship-safe audit . --deep

# Agentic loop — scan → auto-annotate fixes → re-scan until score ≥ 75
npx ship-safe audit . --agentic
npx ship-safe audit . --agentic 5 --agentic-target 85

# Red team scan (22 agents, 80+ attack classes)
npx ship-safe red-team .

# Scan only changed files (fast pre-commit & PR scanning)
npx ship-safe diff
npx ship-safe diff --staged

# Live OSV.dev advisory feed — no API key, no stale data
npx ship-safe advisories .

# Continuous monitoring
npx ship-safe watch .                         # Lightweight file watcher
npx ship-safe watch . --deep                  # Full 22-agent scan on every change
npx ship-safe watch . --deep --threshold 80   # Fail if score drops below threshold
npx ship-safe watch . --status                # Show last deep-watch results

# Fun emoji security grade with shareable badge
npx ship-safe vibe-check .

# Compare your score against industry averages
npx ship-safe benchmark .

# Quick secret scan
npx ship-safe scan .

# Security health score (0-100)
npx ship-safe score .

# CI/CD pipeline mode — compact output, exit codes, PR comments
npx ship-safe ci .
npx ship-safe ci . --github-pr

# Accept current findings, only report regressions
npx ship-safe baseline .
npx ship-safe audit . --baseline

# Check if leaked secrets are still active
npx ship-safe audit . --verify

# Environment diagnostics
npx ship-safe doctor

# Install Claude Code hooks — real-time secret blocking + advisory scan
npx ship-safe hooks install
npx ship-safe hooks status
npx ship-safe hooks remove

The audit Command

One command that runs everything and generates a full report:

npx ship-safe audit .

════════════════════════════════════════════════════════════
  Ship Safe v8.0 — Full Security Audit
════════════════════════════════════════════════════════════

  [Phase 1/4] Scanning for secrets...         ✔ 49 found
  [Phase 2/4] Running 22 security agents...   ✔ 103 findings
  [Phase 3/4] Auditing dependencies...        ✔ 44 CVEs
  [Phase 4/4] Computing security score...     ✔ 25/100 F

  Remediation Plan
  ════════════════════════════════════════════════════════

  🔴 CRITICAL — fix immediately
  ────────────────────────────────────────────────────────
   1. [SECRETS] Rotate Stripe Live Secret Key
      .env:67 → Move to environment variable or secrets manager

   2. [INJECTION] Unsafe pickle.loads()
      backend/ai_processor.py:64 → Use JSON for untrusted data

  🟠 HIGH — fix before deploy
  ────────────────────────────────────────────────────────
   3. [XSS] dangerouslySetInnerHTML without sanitization
      frontend/src/utils/blogContentRenderer.jsx:50 → Add DOMPurify

  ... 149 more items in the full report

  📊 Full report: ship-safe-report.html

What it runs:

1. Secret scan — 50+ patterns with entropy scoring (API keys, passwords, tokens)
2. 22 security agents — run in parallel with per-agent timeouts and framework-aware filtering
3. Dependency audit — npm/pip/bundler CVE scanning with EPSS exploit probability scores
4. Secrets verification — probes provider APIs (GitHub, Stripe, OpenAI, etc.) to check if leaked keys are still active
5. Deep analysis — LLM-powered taint analysis verifies exploitability of critical/high findings (optional)
6. Score computation — OWASP 2025 weighted scoring across 8 categories (0-100, A-F)
7. Context-aware confidence tuning — downgrades findings in test files, docs, and comments
8. Compliance mapping — maps findings to SOC 2 Type II, ISO 27001:2022, and NIST AI Risk Management Framework controls
9. Remediation plan — prioritized fix list grouped by severity
10. Interactive HTML report — standalone dark-themed report with severity filtering, search, collapsible findings, compliance summary, and click-to-copy ignore annotations

Flags:

• --json — structured JSON output (clean for piping)
• --sarif — SARIF format for GitHub Code Scanning
• --csv — CSV export for spreadsheets
• --md — Markdown report
• --html [file] — custom HTML report path (default: ship-safe-report.html)
• --compare — show per-category score delta vs. last scan
• --timeout <ms> — per-agent timeout (default: 30s)
• --no-deps — skip dependency audit
• --no-ai — skip AI classification
• --no-cache — force full rescan (ignore cached results)
• --baseline — only show findings not in the baseline
• --pdf [file] — generate PDF report (requires Chrome/Chromium)
• --deep — LLM-powered taint analysis for critical/high findings
• --local — use local Ollama model for deep analysis
• --model <model> — LLM model to use for deep/AI analysis
• --provider <name> — LLM provider: groq, together, mistral, deepseek, xai, perplexity, lmstudio, gemma4
• --base-url <url> — custom OpenAI-compatible base URL (e.g. LM Studio, vLLM)
• --budget <cents> — max spend in cents for deep analysis (default: 50)
• --verify — check if leaked secrets are still active (probes provider APIs)
• --agentic [n] — scan → annotate fixes → re-scan loop, up to n iterations (default: 3)
• --agentic-target <score> — stop agentic loop when score reaches this threshold (default: 75)

22 Security Agents

Post-processors: ScoringEngine (8-category weighted scoring with OWASP Agentic AI Top 10 enrichment), VerifierAgent (secrets liveness verification), DeepAnalyzer (LLM-powered taint analysis)

All Commands

Core Audit Commands

# Full audit with remediation plan + HTML report
npx ship-safe audit .

# Red team: 22 agents, 80+ attack classes
npx ship-safe red-team .
npx ship-safe red-team . --agents injection,auth    # Run specific agents
npx ship-safe red-team . --html report.html         # HTML report
npx ship-safe red-team . --json                     # JSON output

# Secret scanner (pattern matching + entropy)
npx ship-safe scan .
npx ship-safe scan . --json          # JSON for CI
npx ship-safe scan . --sarif         # SARIF for GitHub

# Security health score (0-100, A-F)
npx ship-safe score .

# Dependency CVE audit
npx ship-safe deps .
npx ship-safe deps . --fix           # Auto-fix vulnerabilities

AI-Powered Commands

# AI audit: scan + classify with Claude + auto-fix secrets
npx ship-safe agent .

# Auto-fix hardcoded secrets: rewrite code + write .env
npx ship-safe remediate .
npx ship-safe remediate . --all    # Also fix agent findings (TLS, debug, XSS, etc.)

# Revoke exposed keys — opens provider dashboards
npx ship-safe rotate .

Baseline Management

# Accept current findings as baseline
npx ship-safe baseline .

# Audit showing only new findings since baseline
npx ship-safe audit . --baseline

# Show what changed since baseline
npx ship-safe baseline --diff

# Remove baseline
npx ship-safe baseline --clear

Diff Scanning

# Scan only changed files (fast pre-commit & PR scanning)
npx ship-safe diff                   # All uncommitted changes
npx ship-safe diff --staged          # Only staged changes
npx ship-safe diff HEAD~3            # Changes in last 3 commits
npx ship-safe diff --json            # JSON output

Vibe Check & Benchmark

# Fun emoji security grade
npx ship-safe vibe-check .
npx ship-safe vibe-check . --badge   # Generate shields.io README badge

# Compare your score against industry averages (OWASP, Synopsys, Snyk)
npx ship-safe benchmark .
npx ship-safe benchmark . --json     # JSON output

CI/CD Pipeline

# CI mode — compact output, exit codes, threshold gating
npx ship-safe ci .
npx ship-safe ci . --threshold 80    # Custom passing score
npx ship-safe ci . --fail-on critical # Fail on severity
npx ship-safe ci . --sarif out.sarif  # SARIF for GitHub
npx ship-safe ci . --github-pr       # Post results as PR comment

Deep Analysis & Verification

# LLM-powered deep analysis (Anthropic/OpenAI/Google/Ollama)
npx ship-safe audit . --deep
npx ship-safe audit . --deep --local               # Use local Ollama
npx ship-safe audit . --deep --budget 50           # Cap spend at 50 cents

# Use any OpenAI-compatible provider for deep analysis
npx ship-safe audit . --deep --provider groq
npx ship-safe audit . --deep --provider together
npx ship-safe audit . --deep --provider mistral
npx ship-safe audit . --deep --provider deepseek
npx ship-safe audit . --deep --provider lmstudio   # Local LM Studio
npx ship-safe audit . --deep --provider xai
npx ship-safe audit . --deep --provider perplexity
npx ship-safe audit . --deep --base-url http://localhost:1234/v1 --model my-model  # Custom

# Check if leaked secrets are still active
npx ship-safe audit . --verify

Diagnostics

# Environment check — Node.js, git, npm, API keys, cache, version
npx ship-safe doctor

Agent Security

# Focused OpenClaw security scan
npx ship-safe openclaw .

# Auto-harden OpenClaw configs (0.0.0.0->127.0.0.1, add auth, ws->wss)
npx ship-safe openclaw . --fix

# Red team: simulate ClawJacked, prompt injection, data exfil attacks
npx ship-safe openclaw . --red-team

# CI preflight — exit non-zero on critical findings
npx ship-safe openclaw . --preflight

# Scan a skill before installing it
npx ship-safe scan-skill https://clawhub.io/skills/some-skill
npx ship-safe scan-skill ./local-skill.json
npx ship-safe scan-skill --all              # Scan all skills from openclaw.json

# Scan an MCP server's tool manifest before connecting
npx ship-safe scan-mcp https://your-mcp-server/
npx ship-safe scan-mcp ./local-manifest.json
npx ship-safe scan-mcp https://your-mcp-server/ --json

# Legal risk audit — DMCA, leaked-source derivatives (openclaude, claw-code-js), IP disputes
npx ship-safe legal .

# Generate hardened OpenClaw config
npx ship-safe init --openclaw

# Generate Agent Bill of Materials (CycloneDX 1.5)
npx ship-safe abom .

openclaude and claw-code

Ship Safe detects security issues in both major Claude Code forks from the March 2026 source leak.

openclaude (@gitlawb/openclaude) is a CLI tool that routes Claude Code's toolset through any OpenAI-compatible provider. Its only persistent file artifact is .openclaude-profile.json. Ship Safe flags:

• OPENAI_BASE_URL using http:// for non-localhost endpoints (unencrypted LLM traffic)
• The profile file present in a project not covered by .gitignore (API key exposure risk)

claw-code (ultraworkers/claw-code) is a clean-room Rust + Python rewrite of Claude Code's agent harness. Its config lives in .claw.json, .claw/settings.json, and .claw/settings.local.json. Ship Safe flags:

• permissionMode: danger-full-access or dangerouslySkipPermissions: true (no confirmation on any tool call)
• sandbox.enabled: false (filesystem isolation removed)
• Hook commands containing shell execution or remote download patterns
• MCP server connections over ws:// or http:// to non-localhost hosts

Hermes Agent Integration

Ship Safe is a first-class Hermes Agent citizen. Register Ship Safe tools directly in your Hermes tool registry:

import { registerWithHermes, verifyIntegrity } from 'ship-safe';

// Register all 5 Ship Safe tools with integrity verification
await registerWithHermes(toolRegistry);

Or use the bundled skill in your Hermes agent:

# In your Hermes agent manifest
skills:
  - ./node_modules/ship-safe/skills/ship-safe-security.md

Available tools: ship_safe_audit, ship_safe_scan_mcp, ship_safe_get_findings, ship_safe_suppress_finding, ship_safe_memory_list.

Threat Intelligence

# Update threat intel feed (ClawHavoc IOCs, malicious skills, config signatures)
npx ship-safe update-intel

# Ships with offline-first seed data — no internet required for scanning

OpenClaw GitHub Action

Drop-in CI action that blocks PRs introducing agent config vulnerabilities:

# .github/workflows/openclaw-security.yml
name: OpenClaw Security Check

on: [pull_request]

permissions:
  contents: read

jobs:
  openclaw:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: asamassekou10/ship-safe/.github/actions/openclaw-check@main
        with:
          fail-on-critical: 'true'

Inputs:

Outputs:

Scans openclaw.json, .cursorrules, CLAUDE.md, Claude Code hooks, and MCP configs. Checks against the bundled threat intelligence database for known ClawHavoc IOCs.

Live Advisory Feed

# Query OSV.dev for actively exploited CVEs across all package ecosystems
npx ship-safe advisories .
npx ship-safe advisories . --json    # JSON output for CI

No API key required. Malware advisories (MAL-*) are sorted to the top. Results include EPSS exploit probability and remediation guidance.

Defensive Hooks

# Install Claude Code defensive hooks (blocks curl|bash, exfil domains, rm -rf /)
npx ship-safe guard --generate-hooks

# Watch agent config files for drift (.cursorrules, CLAUDE.md, openclaw.json)
npx ship-safe watch . --configs

Infrastructure Commands

# Lightweight file watcher — re-scans changed files on save
npx ship-safe watch .

# Deep watch — full 22-agent orchestrator on every change
npx ship-safe watch . --deep
npx ship-safe watch . --deep --threshold 80   # Fail if score drops below threshold
npx ship-safe watch . --deep --debounce 2000  # Custom debounce in ms (default: 1000)
npx ship-safe watch . --status                # Show last deep-watch results from .ship-safe/watch.json

# Generate CycloneDX SBOM
npx ship-safe sbom .

# Policy-as-code (enforce minimum score, fail on severity)
npx ship-safe policy init

# Block git push if secrets found
npx ship-safe guard

# Initialize security configs (.gitignore, headers)
npx ship-safe init

# Launch-day security checklist
npx ship-safe checklist

# MCP server for AI editors (Claude Desktop, Cursor, etc.)
npx ship-safe mcp

Claude Code Hooks

Install ship-safe as real-time Claude Code hooks — secrets are blocked before they ever touch disk:

npx ship-safe hooks install

Once installed, two hooks activate automatically on every Claude Code session:

Hook scripts are copied to ~/.ship-safe/hooks/ at install time — a stable, user-owned location that survives npx cache rotations.

npx ship-safe hooks status   # Check installation
npx ship-safe hooks remove   # Uninstall

Claude Code Plugin

Use Ship Safe directly inside Claude Code — no CLI needed:

claude plugin add github:asamassekou10/ship-safe

Claude interprets the results, explains findings in plain language, and can fix issues directly in your codebase.

Incremental Scanning

Ship Safe caches file hashes and findings in .ship-safe/context.json. On subsequent runs, only changed files are re-scanned — unchanged files reuse cached results.

✔ [Phase 1/4] Secrets: 41 found (0 changed, 313 cached)

• ~40% faster on repeated scans
• Auto-invalidation — cache expires after 24 hours or when ship-safe updates
• --no-cache — force a full rescan anytime

The cache is stored in .ship-safe/ which is automatically excluded from scans.

LLM Response Caching

When using AI classification (--no-ai to disable), results are cached in .ship-safe/llm-cache.json with a 7-day TTL. Repeated scans reuse cached classifications — reducing API costs significantly.

Smart .gitignore Handling

Ship Safe respects your .gitignore for build output, caches, and vendor directories — but always scans security-sensitive files even if gitignored:

Why? Files like .env are gitignored because they contain secrets — which is exactly what a security scanner should catch.

Multi-LLM Support

Ship Safe supports any AI provider for deep analysis and classification:

Auto-detected from environment variables. Use --provider <name> to override. No API key required for scanning — AI is optional.

Scoring System

Starts at 100. Each finding deducts points by severity and category, weighted by confidence level (high: 100%, medium: 60%, low: 30%) to reduce noise from heuristic patterns.

8 Categories (with weight caps):

Weights aligned with OWASP Top 10 2025 risk rankings.

Grades: A (90-100), B (75-89), C (60-74), D (40-59), F (0-39)

Exit codes: 0 for A/B (>= 75), 1 for C/D/F — use in CI to fail builds.

Policy-as-Code

Create .ship-safe.policy.json to enforce team-wide security standards:

npx ship-safe policy init

{
  "minimumScore": 70,
  "failOn": "critical",
  "requiredScans": ["secrets", "injection", "deps", "auth"],
  "ignoreRules": [],
  "customSeverityOverrides": {},
  "maxAge": { "criticalCVE": "7d", "highCVE": "30d", "mediumCVE": "90d" }
}

CI/CD Integration

The dedicated ci command is optimized for pipelines — compact output, exit codes, threshold-based gating:

# Basic CI — fail if score < 75
npx ship-safe ci .

# Strict — fail on any critical finding
npx ship-safe ci . --fail-on critical

# Custom threshold + SARIF for GitHub Security tab
npx ship-safe ci . --threshold 80 --sarif results.sarif

# Only check new findings (not in baseline)
npx ship-safe ci . --baseline

GitHub Actions example:

# .github/workflows/security.yml
name: Security Audit

on: [push, pull_request]

jobs:
  security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Security gate
        run: npx ship-safe ci . --threshold 75 --sarif results.sarif --github-pr

      - uses: github/codeql-action/upload-sarif@v3
        if: always()
        with:
          sarif_file: results.sarif

Export formats: --json, --sarif, --csv, --md, --html, --pdf

Suppress False Positives

Inline: Add # ship-safe-ignore comment on a line:

password = get_password()  # ship-safe-ignore

File-level: Create .ship-safeignore (gitignore syntax):

# Exclude test fixtures
tests/fixtures/
*.test.js

# Exclude documentation with code examples
docs/

OWASP Coverage

What's Inside

/configs

Drop-in security configs for Next.js, Supabase, and Firebase.

/snippets

Copy-paste security patterns: rate limiting, JWT, CORS, input validation.

/ai-defense

LLM security: prompt injection detection, cost protection, system prompt hardening.

/checklists

Manual security audits: launch-day checklist, framework-specific guides.

/skills

Hermes Agent skill definitions. Install skills/ship-safe-security.md to give any Hermes agent native security scanning capabilities.

Add a Security Badge to Your README

Show the world your project is secure. After running npx ship-safe audit . or npx ship-safe vibe-check . --badge, add one of these to your README:

<!-- Replace GRADE and COLOR with your results -->
[![Ship Safe](https://img.shields.io/badge/Ship_Safe-A+-22c55e)](https://shipsafecli.com)

Supply Chain Hardening

Ship Safe practices what it preaches. Our own supply chain is hardened against the 2026 Trivy/CanisterWorm attack chain:

Verify provenance on any Ship Safe release:

npm audit signatures

Contributing

1. Fork the repo
2. Add your security pattern, agent, or config
3. Include comments explaining why it matters
4. Open a PR

See CONTRIBUTING.md for guidelines.

Security Standards Reference

• OWASP Top 10 Web 2025
• OWASP Top 10 Mobile 2024
• OWASP LLM Top 10 2025
• OWASP API Security Top 10 2023
• OWASP CI/CD Top 10
• OWASP Agentic AI Top 10

Sponsors

Ship Safe is MIT-licensed and free forever. If it saves you time or helps you ship more securely, consider sponsoring — it helps keep the project maintained and growing.

License

MIT - Use it, share it, secure your stuff.

Star History

Ship fast. Ship safe. — shipsafecli.com