ShipProof v0.10.0

ShipProof v0.10.0 — Executable Assurance and Reproducible Evidence

ShipProof v0.10.0 turns the post-0.9 development plan into enforceable local contracts. The default workflow remains read-only, offline, deterministic, and dependency-free. This release does not bulk-promote research candidates or claim precision from unreviewed findings.

Highlights

• The dependency-free public website source now ships in English and Thai with explicit sample labeling, no analytics, and no repository upload path. Support, feature, and rule-proposal surfaces route questions and evidence to the correct public or private channel.
• A separate manual npm trusted-publishing workflow validates an immutable release tag, repeats the complete package gate, uses a protected environment and OIDC, and has no long-lived-token fallback. npm availability is not claimed until that external relationship succeeds.
• Current documentation is scanner-derived at 635 executable rules, and a structure contract fails if the authoritative English, Thai, rule, research, plan, or release claims drift again.
• MCP-specific rules SP271–SP275 now require visible MCP context. File helpers no longer masquerade as traversal, real environment-access syntax is covered, and SP275 detects explicitly unbounded tool schemas instead of flagging validated input.
• All 635 executable scanner rules now have machine-readable assurance coverage for positive, negative, adversarial, CWE/control, remediation, and false-positive boundaries.
• The first 25-candidate polyglot batch was triaged before implementation. Three candidates reached research-only fixture_ready status, 22 were rejected from the batch, and zero were promoted without representative shadow evidence.
• Optional compiler/analyzer evidence reports now capture analyzer versions and distinguish unavailable, timeout, output-limit, crash, and findings states. Project-contained tools require explicit consent, and diagnostics are bounded and credential-redacted.
• Scanner performance reports include deterministic workload identity, warmup and sample counts, median and p95 timing, peak RSS, runtime identity, and separate clean, adversarial-regex, and large-file budgets.
• Controlled-corpus results report TP, FP, FN, and TN against sink-level labels while preserving source/helper files as context. The opt-in real-world evaluator pins six reviewed public repositories by full commit and license permalink.
• Every hidden legacy CLI alias has a tested 1.0 removal path and an explicit replacement. Version 0.10 keeps the warning-only compatibility window.

Evidence boundary

The three promotion prototypes are not executable ShipProof rules and do not change the 635-rule public catalog. Their fixtures show that a detector shape is testable; they do not establish representative precision.

Real-world evaluator output marks findings as unreviewed. A successful fetch and scan proves corpus identity and evaluator availability, not that each finding is a true or false positive. Precision claims require checked-in human labels and sample counts.

Performance values are observations tied to the reported machine, runtime, corpus digest, and configuration. They are not universal throughput guarantees and do not replace authorized production-shaped load tests.

Compatibility

The supported public commands remain check, scan, explain, gate, labs, init, config validate, doctor, and mcp. Hidden legacy aliases continue to emit migration warnings in 0.x. When the package major reaches 1, the parser rejects those aliases with exit code 2 and points to their replacements.

Exit codes remain 0 for pass, 1 for gate failure, and 2 for invalid or unavailable evidence. Existing v1 JSON schemas remain compatible; new evidence-adapter fields are additive.

Verification

Before a tag is created, the release must pass the complete lint/test/package/consumer suite, schema and command goldens, the direct high-severity self-scan, controlled head-to-head thresholds, and clean/adversarial/large-file benchmark budgets. Harness acceptance checks remain required when a release change was executed through the opt-in Harness workflow. Publishing, tagging, and pushing remain separate maintainer actions.

ShipProof v0.9.0

ShipProof v0.9.0 — Evidence Contracts and Analyzer Correctness

ShipProof v0.9.0 is the reviewed release after the post-v0.8.1 correctness audit. It keeps the default workflow offline, read-only, deterministic, and dependency-free while tightening evidence contracts and reducing analyzer false positives.

Highlights

• Cross-file analysis now uses the same changed-file, include, exclude, and byte limits as the regular scanner.
• JavaScript and TypeScript cross-file analysis masks comments and string-only text, rejects ambiguous cross-language/simple-name resolution, and transfers taint state in statement order.
• Git-history scanning is bounded, fail-closed, provenance-preserving, baseline-aware, and invokes Git with external diff/text conversion disabled.
• Scan JSON schemas cover real findings, fix scaffolds, cross-file statistics, and history provenance.
• Supply-chain detectors are scoped to their owning manifests and canonical Dockerfile/Containerfile names.
• The packed consumer smoke test is isolated from repository development dependencies; experimental IR stubs and the comparison harness remain development-only.
• Node, Python, plugin, lockfile, citation, README, and research metadata report the same version and rule count.

Stability boundary

check, scan, explain, gate, init, config validate, doctor, and mcp are the supported public commands. labs remains experimental and never supplies production proof. The legacy aliases remain warning-only until the planned 1.0 cleanup.

scan --history reports only bounded added patch lines. It does not prove credential rotation, deletion from every clone, or live credential validity; pair it with a dedicated history and rotation workflow.

Verification

The release must pass npm run check, the direct high-gate self-scan, real-output schema validation, cross-file changed-scope regressions, history integration tests, isolated packed-artifact smoke tests, and benchmark thresholds before the immutable v0.9.0 tag is created.

ShipProof v0.8.1

ShipProof v0.8.1 — JavaScript Taint Engine, 605-Rule Catalog, and Code-Scanning-Ready SARIF

ShipProof v0.8.1 closes the biggest capability gap against heavyweight SAST tools: the opt-in --cross-file engine now understands JavaScript and TypeScript the way it understood Python, the catalog grows to 605 executable rules with 30 promotions from the research backlog, and SARIF output speaks GitHub code-scanning's native ranking, threat-model tagging, and suggested-fix formats. Every workflow stays offline, deterministic, and dependency-free.

Highlights

• JavaScript/TypeScript interprocedural taint: inline (req, res) handlers and named handlers registered through Express-style routes become entrypoints; request-derived values flow through local aliases into SQL (query/execute/raw), command execution (exec/execSync), path traversal (fs.* with alias resolution back to the entering parameter), SSRF (bare fetch, receiver-aware axios.<method>), DOM XSS (innerHTML/outerHTML assignments, document.write), and reflected HTML responses. Sanitizer awareness covers Number/parseInt/path.basename, containment guards (startsWith prefix checks), and parameterized placeholder arrays.
• Python engine parity: a query built from a tainted parameter now reaches execute() through its variable via alias tracking, while bound-parameter tuples (execute(sql, (a, b))) are excluded from injectable SQL text — a real-world false positive found on Flask's own tutorial.
• 30 promoted rules (SP051–SP080): prototype pollution via request merges, hardcoded JWT signing secrets, DES/3DES/RC4 selection, shell interpolation on Python and Node, session cookies missing HttpOnly/SameSite, credentials embedded in URL query strings, Mongo operator injection, PHP dynamic includes / preg_replace /e / extract() / superglobal shell calls, Java EL evaluation, condition assignments, Runtime.exec concatenation, default-AES transforms, unconstrained Spring mappings, Go world-writable modes / clock-seeded math/rand / allow-all WebSocket origins, Ruby eval(params) and VERIFY_NONE, Flask/Express file responses from request data, stack traces returned to clients, bare exception handlers, and reflected HTML responses. Every rule carries explanation metadata, positive/negative tests, and a catalog row.
• Express authorization coverage: SP108 now fires on JavaScript admin routes that lack route-level auth middleware, global auth registration, and any broad authorization signal — comment prose can no longer grant or revoke coverage.
• Code-scanning-ready SARIF: rules carry a deterministic security-severity ranking property and STRIDE threat-model tags across every covered CWE root; runs bind to the scanned commit through read-only versionControlProvenance plus automationDetails; curated flag-flip findings surface review-required mechanical fix scaffolds as JSON fix_scaffold fields and SARIF fixes. Redacted secret rules never scaffold, so before/after text can never leak credential material.
• Precision hardening from real-world triage (express, flask, requests, juice-shop, DVWA, NodeGoat): SSRF loopback URLs require request-call context, .open( method look-alikes stop matching path traversal, sync-I/O findings require loop context, code-shaped matches inside string literals are suppressed while OAuth URL content rules stay exempt, minified/hashed bundles downgrade confidence, Next.js-only rules downgrade outside Next manifests, and the Python engine stops flagging bind-parameter tuples.
• Benchmark suite grows teeth: multi-file cross-file-taint corpora with secure counterparts, an adversarial precision-trap suite where comment/string-literal look-alikes must stay silent while two-hop aliasing, destructured params, cookie-to-DOM chains, and three-file taint chains must all fire, head-to-head runs over all fixtures with the full engine enabled, a promotion-shortlist pipeline ranking the 7,800-slot research backlog by local implementability, and a weekly CI benchmark workflow with opt-in open-source evaluation.

Compatibility

• Node.js 20 or newer for the CLI and adapters; Python 3.10 or newer for scanner-backed commands.
• Policy version 1 and evidence schema version 1.0 remain compatible; scan reports add an optional per-finding fix_scaffold object (additive).
• SARIF consumers see additive rule properties (security-severity, STRIDE tags) and run-level keys; existing fingerprints are unchanged.
• Exit codes remain 0 pass, 1 gate failure, 2 invalid evidence.

Verification

The release commit must pass npm run check, the approved package file set check, packed-artifact smoke testing, and the full fixture battery (precision 1.0, zero findings on secure corpora) before the exact v0.8.1 tag is created.

ShipProof v0.8.0

ShipProof v0.8.0 — Cross-File Taint, Framework Confidence, Parallel Scans, and Fair Benchmarks

ShipProof v0.8.0 turns the analysis depth, throughput, and evaluation story of the production gate up a level while keeping every workflow offline, deterministic, and dependency-free. The executable scanner now contains 575 rules; the research catalogs remain explicitly non-executable until their precision fixtures pass.

Highlights

• Opt-in cross-file taint analysis: shipproof scan . --cross-file (also on the MCP shipproof_scan tool) promotes unsanitized interprocedural flows — route entrypoints through helpers into SQL, command-execution, and eval sinks — into L2 findings on the sink line with call-chain evidence, reusing the offline impact-graph analyzer. Flow totals and unsanitized counts are reported in JSON.
• Four evidence-gated framework rules: SP662 Django wildcard CORS, SP663 Django non-secure session cookies, SP664 FastAPI routes without visible rate limiting, and SP665 Django DEBUG in deployable settings. Each ships with positive/negative/adversarial fixtures, two-source primary grounding, false-positive analysis, and both README tables; the hardened demo fixture demonstrates SP664 remediation with a real token-bucket limiter.
• Framework-aware confidence: structural framework rules keep their default confidence only when repository manifests declare the framework; present-but-undeclared frameworks downgrade confidence one level instead of suppressing, and manifest-less repositories keep full confidence.
• Deterministic parallel scanning: --jobs N scans files across worker processes with byte-identical output, enforced by a jobs=1 versus jobs=4 parity test, and falls back to sequential execution when process pools are unavailable.
• Fair, offline head-to-head benchmarking: benchmarks/head_to_head.py measures any scanner against ShipProof on identical local corpora — median end-to-end wall time plus file-level precision/recall/F1 against a shared label file. Third-party tools run only with caller-supplied rule files; ShipProof bundles, downloads, and copies no third-party rules.
• Faster, more precise engine: quadratic SP577/SP579 windows are bounded to their reporting span and a sound literal-gate prefilter (validated over 370 million rule/line checks with zero false skips) skips rules whose required literals are absent, cutting full-repository scans by roughly 48%; same-line collisions now keep the strongest proof level, docstring examples stop triggering non-secret rules, placeholder filtering targets the credential value (un-breaking SP004), entropy calibration covers SP004/SP019–SP021, and the AST engine detects concatenated and base64-encoded credentials.
• Exit-code contract, end to end: scanner crashes (including RecursionError and raw Windows NTSTATUS statuses) exit 2 as invalid evidence instead of masquerading as gate blocks; gate timeouts and buffer overflows report actionable errors with SHIPPROOF_GATE_TIMEOUT_MS / SHIPPROOF_MAX_BUFFER_BYTES overrides.
• Suppression integrity: shipproof-ignore markers are honored only inside comments (never string literals), accept multiple rule IDs at once, and bind the Python AST engine as well as the regex engine. Every credential rule that redacts evidence now receives placeholder filtering, comment scanning, and document scanning.
• Precise locations: findings carry column, end_line, and end_column; SARIF regions and GitHub annotations use them, with sanitized annotation messages.
• Quieter Node layer: one cached Python runtime probe per process across CLI, Action, and MCP; configurable MCP timeout (SHIPPROOF_MCP_TIMEOUT_MS) and optional result cache (SHIPPROOF_MCP_CACHE_MS); shipproof_scan accepts exclude, min_confidence, and cross_file; snippets are byte-limited to match the Python scanner; zod schemas are zod-4 compatible; policy limits are unified with the Action and MCP; evidence reports classify diagnostics into severity_counts; Action step summaries escape table cells and cap rendered rows; and the README documents SARIF upload for Code Scanning.

Compatibility

• Node.js 20 or newer for the CLI and adapters.
• Python 3.10 or newer for scanning and Python-backed gates.
• Policy version 1 and evidence schema version 1.0 remain compatible; scan reports add optional column, end_line, end_column, and cross_file_flows_unsanitized fields (additive, schema-versioned).
• --jobs 1 (default) and opt-out of --cross-file preserve prior behavior exactly.
• Exit codes remain 0 for pass, 1 for a measured gate failure, and 2 for invalid or unavailable evidence.

Verification

The release commit must pass npm run check, packed-artifact smoke testing, and a direct repository self-scan at the high threshold before the exact v0.8.0 tag is created.

ShipProof v0.7.0

ShipProof v0.7.0 — Contract Hardening, Evidence-Gated Rules, and Explainable Decisions

ShipProof v0.7.0 hardens the production gate around trustworthy command contracts, low-noise detection, release safety, and inspectable evidence. The executable scanner now contains 571 rules; the much larger research catalogs remain explicitly non-executable until their positive, negative, and adversarial fixtures meet the promotion policy.

Highlights

• Fail-closed contracts: init now generates a policy that immediately round-trips through check; missing or invalid targets, negative cost inputs, unsafe policy paths, unavailable analyzers, stale Action reports, and mismatched release tags return the documented evidence-unavailable exit.
• Scanner correctness and precision: previously unreachable file types are scanned, bounded multiline rules operate on structural context, changed-file discovery supports Unicode and repository subdirectories, secret renderers do not rehydrate credentials, and autofix success requires a clean verification scan.
• Evidence-gated detector growth: eleven promoted cloud, Kubernetes, CI/CD, security, and supply-chain detectors include stable IDs, official-source grounding, CWE/control mappings, remediation, false-positive analysis, and positive/negative/adversarial fixtures.
• Research without noisy bulk activation: 7,800 deduplicated candidate records cover 2021–2026 incident signals and language-specific security, reliability, performance, and scale risks. These records are prioritization inputs, not scanner findings.
• Simpler public CLI: stable workflows center on check, scan, and explain; deterministic primitives live under gate, heuristic analyzers under labs, configuration can be validated without running gates, and the unverifiable static badge command is retired.
• Progressive context and decision trace: explain and AI fix prompts support summary, overview, and full detail. Repository scans can opt into a deterministic, content-free --trace that reports selection, filtering, suppression, and gate counts without source, paths, secrets, timings, telemetry, or network calls.
• Release and package assurance: command outputs are checked against versioned schemas, MCP tools are handshake-tested with strict schemas, SARIF remains available after a blocking scan, the package file set and size are allowlisted, and the packed artifact is smoke-tested as a real consumer install.
• Project maturity: the English and Thai READMEs now state the trust boundary, evidence levels, supported ecosystems, limitations, governance, citation, contribution, conduct, security, and release policies in a consistent public contract.

Compatibility

• Node.js 20 or newer for the CLI and adapters.
• Python 3.10 or newer for scanning and Python-backed gates.
• Policy version 1 and evidence schema version 1.0 remain compatible.
• full remains the default context level, so existing explanation and fix-prompt workflows retain their detailed behavior.
• Exit codes remain 0 for pass, 1 for a measured gate failure, and 2 for invalid or unavailable evidence.

Verification

The release commit must pass npm run check, packed-artifact smoke testing, and a direct repository self-scan at the high threshold before the exact v0.7.0 tag is created.

v0.6.1

ShipProof v0.6.1 — AI Agent Cost Engine, Worktree Sandbox & 150+ Enterprise Multi-Language Gate
ShipProof v0.6.1 is a major capability release expanding production-readiness gating for AI coding workflows, bringing token & financial cost modeling, Git worktree isolation sandboxing, shields.io status badges, Next.js 15 App Router protections, Cloud IaC, Edge Runtimes, Real-Time Concurrency, Cryptography, and 60 new enterprise static analysis rules (SP591 – SP650).

Highlights
AI Cost & Token Budget Engine (shipproof cost): Automatic context footprint estimation (~3.8 bytes/token), prompt caching discount models across frontier models (Claude 3.7/3.5, GPT-4o, Gemini 2.0/1.5, DeepSeek-V3/R1), multi-iteration cadence projections, and budget gate enforcement (--budget-usd).
Git Worktree Isolation Sandbox (shipproof worktree): Safe workspace isolation in .work/ with path traversal validation, UTF-8 non-ASCII directory hardening, pre-merge gate verification, and clean worktree teardown.
Production Status Badge (shipproof badge): Emits shields.io Markdown or JSON status badges for README.md.
Next.js 15 & TypeScript Enterprise Gate (SP591 – SP600): Server-only DB/ORM leakage in "use client" bundles (SP591), mutating route body casts to any (SP592), unawaited Next.js 15 route segment params (SP593), authenticated route caching (SP594), Server Action mutations missing revalidation (SP595), client React hooks in Server Components (SP596), sequential waterfall requests blocking SSR (SP597), cookie routes missing CSRF origin checks (SP598), TypeScript non-null assertions on API responses (SP599), Server Action IDOR on client-provided userId (SP600).
Multi-Language Enterprise Production Gate (SP601 – SP625): OWASP Top 10 for LLMs (SP601–SP605), Kubernetes & Cloud Hardening (SP606–SP610), GraphQL & gRPC API Resilience (SP611–SP614), OAuth2 / PKCE Security (SP615–SP617), Data Safety (SP618–SP620), and Multi-Language Failure Modes in Rust, Go, Java, Python, C# (SP621–SP625).
Cloud IaC, Edge Runtimes, Real-Time & Cryptography Gate (SP626 – SP650): S3 public wildcard permissions (SP626), unencrypted storage (SP627), open security group SSH/RDP ports (SP628), wildcard IAM policies (SP629), CloudFront HTTPS enforcement (SP630), Edge runtime Node module check (SP631), unbounded KV fetch loops (SP632), Edge Worker buffering (SP633), authenticated CDN caching (SP634), WebSocket heartbeat monitoring (SP635), Server-Sent Events close listeners (SP636), WebSocket auth verification (SP637), BroadcastChannel unmount leaks (SP638), legacy symmetric ciphers (SP639), weak RSA key lengths (SP640), static hardcoded IV reuse (SP641), broken MD5/SHA1 hashes (SP642), timing-unsafe secret comparisons (SP643), Svelte {@html} XSS (SP644), Android WebView file access (SP645), iOS SSL validation bypass (SP646), API proxy SSRF (SP647), React useEffect WebSocket teardown (SP648), multitenant query tenant scoping (SP649), and recursive JSON nesting bounds (SP650).
Compatibility
Node.js 20 or newer for the CLI.
Python 3.10 or newer for scan, policy, budget, capacity, worktree, and cost tools.
Config schema version 1 and evidence envelope 1.0.

ShipProof v0.6.0

ShipProof v0.6.0 — AI Agent Cost Engine, Worktree Sandbox & 150+ Enterprise Multi-Language Gate

ShipProof v0.6.0 is a major capability release expanding production-readiness gating for AI coding workflows, bringing token & financial cost modeling, Git worktree isolation sandboxing, shields.io status badges, Next.js 15 App Router protections, Cloud IaC, Edge Runtimes, Real-Time Concurrency, Cryptography, and 60 new enterprise static analysis rules (SP591 – SP650).

Highlights

• AI Cost & Token Budget Engine (shipproof cost): Automatic context footprint estimation (~3.8 bytes/token), prompt caching discount models across frontier models (Claude 3.7/3.5, GPT-4o, Gemini 2.0/1.5, DeepSeek-V3/R1), multi-iteration cadence projections, and budget gate enforcement (--budget-usd).
• Git Worktree Isolation Sandbox (shipproof worktree): Safe workspace isolation in .work/<task> with path traversal validation, UTF-8 non-ASCII directory hardening, pre-merge gate verification, and clean worktree teardown.
• Production Status Badge (shipproof badge): Emits shields.io Markdown or JSON status badges for README.md.
• Next.js 15 & TypeScript Enterprise Gate (SP591 – SP600): Server-only DB/ORM leakage in "use client" bundles (SP591), mutating route body casts to any (SP592), unawaited Next.js 15 route segment params (SP593), authenticated route caching (SP594), Server Action mutations missing revalidation (SP595), client React hooks in Server Components (SP596), sequential waterfall requests blocking SSR (SP597), cookie routes missing CSRF origin checks (SP598), TypeScript non-null assertions on API responses (SP599), Server Action IDOR on client-provided userId (SP600).
• Multi-Language Enterprise Production Gate (SP601 – SP625): OWASP Top 10 for LLMs (SP601–SP605), Kubernetes & Cloud Hardening (SP606–SP610), GraphQL & gRPC API Resilience (SP611–SP614), OAuth2 / PKCE Security (SP615–SP617), Data Safety (SP618–SP620), and Multi-Language Failure Modes in Rust, Go, Java, Python, C# (SP621–SP625).
• Cloud IaC, Edge Runtimes, Real-Time & Cryptography Gate (SP626 – SP650): S3 public wildcard permissions (SP626), unencrypted storage (SP627), open security group SSH/RDP ports (SP628), wildcard IAM policies (SP629), CloudFront HTTPS enforcement (SP630), Edge runtime Node module check (SP631), unbounded KV fetch loops (SP632), Edge Worker buffering (SP633), authenticated CDN caching (SP634), WebSocket heartbeat monitoring (SP635), Server-Sent Events close listeners (SP636), WebSocket auth verification (SP637), BroadcastChannel unmount leaks (SP638), legacy symmetric ciphers (SP639), weak RSA key lengths (SP640), static hardcoded IV reuse (SP641), broken MD5/SHA1 hashes (SP642), timing-unsafe secret comparisons (SP643), Svelte {@html} XSS (SP644), Android WebView file access (SP645), iOS SSL validation bypass (SP646), API proxy SSRF (SP647), React useEffect WebSocket teardown (SP648), multitenant query tenant scoping (SP649), and recursive JSON nesting bounds (SP650).

Compatibility

• Node.js 20 or newer for the CLI.
• Python 3.10 or newer for scan, policy, budget, capacity, worktree, and cost tools.
• Config schema version 1 and evidence envelope 1.0.

v0.5.2

ShipProof v0.5.2 — Path-Aware Triage, Closed-Loop Agent Protocol & L2 Python Taint

ShipProof v0.5.2 brings path-aware noise reduction, function-local taint analysis for Python, inline GitHub annotations, and a closed-loop remediation protocol for AI coding assistants.

Highlights

• Path-Aware Triage: Findings in test, example, doc, and benchmark directories are tagged scope: test and downranked by one confidence level. Gates evaluate only app-scoped findings by default; pass --include-tests to evaluate test files in gate thresholds.
• Python Intraprocedural Taint Tracking (L2): Track local variable assignments within function scopes to detect indirect SQL injection and dynamic code execution with detection: taint and proof_level: L2.
• Closed-Loop Agent Protocol: Support --format json in --fix-prompt and --explain commands for automated remediation pipelines in Codex, Claude Code, and Cursor.
• GitHub Workflow Annotations: Direct support for --format github emitting inline ::error and ::warning annotations on PR lines.
• Automated Policy Initialization: shipproof init writes a documented .shipproof.yml template if missing.
• Framework Expansion: Extended SP106 deserialization detection to Ruby (Marshal.load, YAML.unsafe_load), and updated multi-language rule mapping tables.

Compatibility

• Node.js 20 or newer for the CLI.
• Python 3.10 or newer for scan, policy, budget, capacity, and MCP evidence tools.
• Config schema version 1 and evidence envelope 1.0.

ShipProof v0.5.1

ShipProof v0.5.1 — GitHub Action & Packages Release

ShipProof v0.5.1 delivers complete GitHub Action integration and official GitHub Packages distribution for @kingggg5/shipproof.

Highlights

• GitHub Action Support: Production-ready kingggg5/shipproof@v0.5.1 action for pull requests and CI pipelines.
• GitHub Packages Registry: Pre-configured @kingggg5/shipproof npm package distribution with automated release pipeline.
• Deep Defense Multi-Framework Scanning: Full framework-aware scanning across 30+ ecosystems and deep database/scale guardrails.
• Zero Emoji Technical Documentation: Complete English and Thai guides with responsive architecture diagrams.

Compatibility

• Node.js 20 or newer for the CLI.
• Python 3.10 or newer for scan, policy, budget, capacity, and MCP evidence tools.
• Config schema version 1 and evidence envelope 1.0.

ShipProof v0.5.0

ShipProof v0.5.0 — Deep Production Defense & Multi-Framework Engine

ShipProof v0.5.0 expands framework-aware detection across 30+ ecosystems and adds deep-dive production readiness and scale defense rules.

Highlights

• Multi-Framework Auto-Detection: Automatic framework-tailored scanning for Next.js, Nuxt, SvelteKit, Remix, Astro, React, Vue, Angular, SolidJS, Express, Fastify, NestJS, Koa, Hono, Elysia, Prisma, Drizzle, TypeORM, Mongoose, Supabase, FastAPI, Django, Flask, Starlette, Litestar, Sanic, Go (Gin, Echo, Fiber, Chi), Rust (Actix-web, Axum, Rocket), PHP (Laravel, Symfony), Ruby (Rails, Sinatra), Java/Kotlin (Spring Boot, Quarkus, Micronaut), Docker, Serverless, and GitHub Actions.
• Deep-Dive Production Rules: Added SP113 (PHP unserialize injection), SP114 (ReDoS nested quantifiers), SP314 (Committed SQLite file), SP315 (Go response body close leak), SP316 (Outbound HTTP inside database transaction), and SP317 (Blocking calls inside Python async def).
• Comprehensive Explain Catalog: Detailed why/fix/attack scenario/FP-analysis/testing guidance for all rules via shipproof explain <rule>.
• GitHub Packages Publishing: Official @kingggg5/shipproof npm package distribution on GitHub Packages.
• Bilingual Documentation: Full English and Thai documentation with responsive full-width visual terminal and capacity flow architecture diagrams.

Compatibility

• Node.js 20 or newer for the CLI.
• Python 3.10 or newer for scan, policy, budget, capacity, and MCP evidence tools.
• Config schema version 1 and evidence envelope 1.0.