Terms of Service

1. Agreement

These Terms of Service govern your access to and use of Should I Ship, a product of Zero To Build LLC. By creating an account, connecting a repository, starting a scan, creating a CLI unlock link, viewing a report, purchasing an unlocked report, or otherwise using the product, you agree to these Terms and our Privacy Policy.

If you are using Should I Ship for a company or other organization, you represent that you have authority to bind that organization to these Terms.

2. What Should I Ship Does

Should I Ship analyzes connected software repositories and produces reports about security, cost risk, architecture, launch readiness, dependencies, and related engineering concerns.

The local CLI can run scans on your machine. If you choose to create a CLI unlock link, the CLI uploads findings and scan metadata so we can store and unlock the full report without requiring GitHub.

The product uses automated checks, third-party scanners, dependency data, heuristics, and, when enabled, AI-assisted summaries or suggestions. Results are informational and may be incomplete, outdated, wrong, or not applicable to your specific situation.

Should I Ship is an automated software tool only. It does not make deployment, business, security, compliance, financial, or legal decisions for you.

3. Your Responsibilities

You are responsible for the repositories, credentials, code, settings, products, deployments, and business decisions you connect to or make using Should I Ship.

You must review, test, and validate all findings, suggested fixes, code changes, security recommendations, cost estimates, and launch recommendations before relying on them.

You are responsible for maintaining backups, access controls, deployment controls, secret management, monitoring, and independent security review appropriate for your business.

You are responsible for deciding whether to create a CLI unlock link. You should not upload findings or metadata for repositories, clients, employers, or projects unless you have permission to process that information through Should I Ship.

You are solely responsible for any decision to ship, not ship, change, delete, deploy, pause, bill, refund, disclose, rotate, or otherwise act based on anything you see in Should I Ship.

4. Repository Access

When you connect GitHub or another code host, you authorize us to access repository metadata and selected repository contents needed to provide scans and reports.

You represent that you have the rights and permissions needed to connect the repositories you choose to scan.

You must not use Should I Ship to scan repositories, code, or data you do not have permission to access.

5. CLI Unlock Links

CLI unlock links are optional. The CLI may ask whether you want to upload findings to unlock the full report, and you may skip upload with available CLI options.

When you create a CLI unlock link, you authorize us to receive, store, process, and display the uploaded findings and scan metadata for the purpose of creating the unlock link, processing payment, showing the unlocked report, providing support, preventing abuse, debugging failures, and operating and improving the product.

The CLI unlock flow is designed not to upload source code, file contents, environment variables, ignored files, code snippets, or suggested code patches. However, uploaded finding metadata may include file paths, rule IDs, descriptions, dependency information, and other technical details that may reveal information about your project.

Unlock links may be accessible to anyone who has the link unless we add additional access controls. You are responsible for deciding who receives an unlock link or unlocked report link.

6. No Professional Advice

Should I Ship does not provide legal, financial, compliance, security-audit, accounting, insurance, or professional engineering advice. The product is a software tool that helps surface possible issues.

A passing score, improved score, missing finding, or recommendation does not mean your product is secure, compliant, profitable, reliable, or safe to launch.

7. No Guarantees

We do not guarantee that Should I Ship will find every vulnerability, bug, dependency issue, architectural flaw, cost risk, compliance issue, launch blocker, or revenue-impacting concern.

We do not guarantee that a suggested fix will be correct, complete, secure, compatible with your codebase, or appropriate for your business.

You use the product and all scan results, scores, findings, summaries, forecasts, prompts, and suggestions entirely at your own risk.

8. Billing And Plans

Paid plans, scan limits, feature limits, and prices may change over time. Any plan limits shown in the product are part of the service design and may be enforced to protect service reliability and cost.

One-time CLI report unlock purchases unlock the corresponding uploaded CLI report when payment is completed and confirmed by our payment provider. Access may depend on successful webhook processing and service availability.

Payments are processed by our payment provider. You are responsible for taxes, fees, and charges associated with your account unless otherwise stated.

9. Acceptable Use

You may not abuse, overload, reverse engineer, resell, interfere with, or attempt unauthorized access to Should I Ship or its infrastructure.

You may not submit malicious code for the purpose of attacking the service, bypass rate limits, misuse credentials, or use the product in violation of law or third-party rights.

10. Disclaimers

Should I Ship is provided as is, as available, with all faults, and without warranties of any kind. To the fullest extent permitted by law, Zero To Build LLC disclaims all warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, availability, uptime, compatibility, error-free operation, and security.

We do not warrant that the product will be uninterrupted, timely, secure, accurate, complete, free from harmful components, or that any scan result or recommendation will meet your needs.

11. Limitation Of Liability

To the fullest extent permitted by law, Zero To Build LLC and its owners, employees, contractors, service providers, and affiliates will not be liable for lost profits, lost revenue, lost data, business interruption, security incidents, vulnerabilities, deployment failures, cost overruns, reputational harm, or indirect, incidental, special, consequential, exemplary, or punitive damages arising from or related to your use of Should I Ship.

To the fullest extent permitted by law, Zero To Build LLC is not liable for any action you take or do not take based on a score, report, finding, missing finding, cost forecast, fix suggestion, AI-generated text, or other product output.

This limitation applies even if we have been advised of the possibility of such damages and even if a remedy fails of its essential purpose.

To the fullest extent permitted by law, our total liability for any claim related to Should I Ship will not exceed the greater of the amount you paid us for the service in the three months before the claim or one hundred US dollars.

12. Oregon Law

These Terms are governed by the laws of the State of Oregon, without regard to conflict-of-law rules.

To the fullest extent permitted by law, any dispute related to Should I Ship or these Terms must be brought in the state or federal courts located in Oregon, and you consent to the jurisdiction and venue of those courts.

13. Changes

We may update these Terms from time to time. Continued use of Should I Ship after changes become effective means you accept the updated Terms.