Ship Safe CLI
PulseGate's liveness check found it on 3 Oct 2026; it is registered on GitHub and has been in the index since 16 Aug 2026. How this is checked
Ship Safe CLI scans codebases and AI-agent configurations for security vulnerabilities, including LLM risks, MCP issues, RAG poisoning, secrets, and dependency CVEs. It supports local scans, pull-request fixes, and optional cloud history for developers and teams.
Inferred · not functionally tested
Overview
6 featuresPurpose: Finding and fixing AI-agent, code, secret, and dependency security vulnerabilities before they reach production.
Inferred · not functionally tested
Audience: developers and engineering teams
Inferred · not functionally tested
Functions: monitoring, data_extraction
Inferred · not functionally tested
Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI, WEB · deployment: browser, cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: shipsafe.sh · github.com. These links do not verify the individual claims.
Ship Safe CLI sits in PulseGate's AI & LLM security category. Inferred · not functionally tested: It focuses on finding and fixing AI-agent, code, secret, and dependency security vulnerabilities before they reach production. Inferred · not functionally tested: It is built as an open-source project for developers and engineering teams. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: Ship Safe CLI is available on the web and the command line, and it can be self-hosted.
It is developed by asamassekou10, and it first shipped in 2026. The project is developed in the open on GitHub with 823 stars and 158 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are local code scans, PR fixes, and cloud scan history. Basis unknown · not verified: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Local code scans
- PR fixes
- Cloud scan history
- MCP security checks
- RAG poisoning detection
- Secrets scanning
Topics: Inferred · not functionally tested
Built with & integrations
- Next.js
- x-nextjs-prerender header · x-powered-by header · /_next/static/ in the HTML
- Vercel
- x-vercel-id header · x-vercel-cache header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed16 Aug · 17:34 UTCasamassekou10/ship-safe seen via GitHub Search (Smart)Source: GitHub Search (Smart) · Open
Frequently asked questions about Ship Safe CLI
- What does Ship Safe CLI do?
- Inferred · not functionally tested: Ship Safe CLI focuses on finding and fixing AI-agent, code, secret, and dependency security vulnerabilities before they reach production. It is catalogued under AI & LLM security on PulseGate.
- Who should use Ship Safe CLI?
- Inferred · not functionally tested: Ship Safe CLI is an open-source project built for developers and engineering teams.
- Is Ship Safe CLI free?
- Basis unknown · not verified: Yes — Ship Safe CLI is open source under the MIT license and free to use.
- What platforms does Ship Safe CLI run on?
- Basis unknown · not verified: Ship Safe CLI runs on the web and the command line. It can also be self-hosted.
- Is Ship Safe CLI still maintained?
- PulseGate's liveness check found it on 3 Oct 2026. Its GitHub repository shows 158 commits in the last 90 days.
- What are alternatives to Ship Safe CLI?
- Similar projects tracked by PulseGate include shipsignal, AI Shipcheck, and Agent Scan.shipsignalAI ShipcheckAgent Scan
- Who develops Ship Safe CLI?
- Ship Safe CLI is developed by asamassekou10.
- When did Ship Safe CLI launch?
- Ship Safe CLI first shipped in 2026.
Similar projects
Closest matches by what these projects do