1. Service description
VibeShield provides static security analysis of source code that you submit via the web dashboard, the JSON API, or installed GitHub App webhooks. The service produces findings, severity, fix guidance, dependency CVE advisories, and optional pull request comments and patch suggestions.
2. Your responsibilities
- You confirm you have the right to submit any code, manifest file, or repository for analysis.
- You will not submit personal data of others as scan content.
- You will protect your API keys and revoke them on compromise.
- You will not use the service to attempt to access third-party systems without authorization.
3. Acceptable use
No reverse engineering, no scraping, no automated abuse, and no use of VibeShield findings to develop a competing scanner. Reasonable per-workspace rate limits apply.
4. Fees
VibeShield is provided free of charge. There is no paid tier, no checkout, no upsell. If that changes in the future, existing workspaces will be notified at least 30 days in advance and may export and delete their data before any payment is requested.
5. Service level
VibeShield targets 99% monthly availability, excluding planned maintenance announced 24 hours in advance. The service is delivered "as is" with no warranty that findings are exhaustive or free of false positives.
6. Liability
To the maximum extent permitted by law, VibeShield's aggregate liability for any claim is limited to the fees paid by you in the twelve months preceding the claim. We are not liable for indirect, incidental, or consequential damages.
7. Termination
Either party may terminate for material breach with 30 days written notice. Workspace owners may close their workspace at any time, which deletes findings, sessions, API keys, and audit logs.
8. Governing law
These terms are governed by the laws of California, USA, with venue in San Francisco County, unless mandatory consumer-protection law in your jurisdiction provides otherwise.
9. Contact
All non-security contact goes through GitHub Issues. Security disclosures should use GitHub Private Vulnerability Reporting. There is no email channel.