V
Vishwakarma
Your services

Supported Versions

Only the latest deployed version of Vishwakarma receives security updates.

Reporting a Vulnerability

If you discover a security vulnerability, please report it privately by emailing the team directly (do not file public GitHub issues).

What to include:

Response timeline:

24 hours:Acknowledgment of receipt 7 days:Initial assessment and remediation plan 30 days:Fix deployed or rationale for extended timeline

Bug Bounty

We do not currently offer a bug bounty program.

Backup & Recovery

Automated Backups

Restore Procedure

  1. Go to Supabase Dashboard Database Backups
  2. Select backup "Restore"
  3. Choose target: new project (recommended) or same project
  4. Wait for restoration (5-30 min depending on size)
  5. Verify integrity after restoration
  6. Update connection secrets if restoring to new project

RTO / RPO Targets

MetricTarget
RTO (Recovery Time)< 1 hour (PITR) | < 4 hours (manual)
RPO (Recovery Point)< 24 hours (daily) | < 1 hour (PITR)

Incident Response

1. Credential Leak

If API keys, service role key, or secrets are exposed:

  1. Rotate compromised key immediately in provider dashboard
  2. Update configuration files and secrets store
  3. Revoke old key
  4. Check audit logs for unauthorized access
  5. Notify affected users if data may have been exposed

2. Database Corruption / Data Loss

  1. Stop writes: Temporarily disable write operations
  2. Restore from backup
  3. Verify integrity with database statistics
  4. Notify users of service disruption

3. DDoS / Brute Force Attack

Security Checklist

✓ HTTPS enforced — Cloudflare + HSTS
✓ Security headers — CSP, X-Frame-Options, X-Content-Type-Options
✓ RLS policies — All tables have RLS enabled
✓ Rate limiting — Login and mutation throttling
✓ Input validation — Server-side validation + DB constraints
✓ Error sanitization — Schema details stripped from errors
◯ Backup test — Verify quarterly
◯ Dependency audit — Pre-deploy audit

Key Contacts & Escalation

RoleResponsible
Security LeadDevOps Lead
Database AdminBackend Dev
Incident ResponseOn-call rotation

For security issues: email the team directly — do not file public GitHub issues.