production-audit

A local evidence production readiness audit evaluates application deployment risks without external data transfer. It uses local evidence to identify and mitigate potential issues before launch, avoiding unpinned remote code execution and third-party uploads.

Checking application security and shipping readiness post-merge involves auditing local evidence for production risks. This process identifies potential deployment issues and highlights what needs mitigation before launching the application to ensure safe shipping.

Yes, you can use a local audit for pre-launch application security checks. It supports pre-launch reviews, post-merge checks, and shipping readiness audits by evaluating risks using only local, user-authorized evidence without external services.

A production readiness audit does not require external dependencies or remote code execution. It operates entirely on local evidence and avoids uploading repository contents to third-party services to ensure data privacy during risk assessment.

You should perform a production readiness audit during post-merge checks, pre-launch reviews, and shipping readiness evaluations. It helps identify what needs to be fixed before launch by analyzing local application evidence for potential risks.

To start a production audit using local evidence, run the audit command with your target application name. This initiates a local evaluation to identify deployment risks and necessary mitigations without external data transfer or third-party services.