Legal and governance
Engineering transparency note, not legal advice.
License and attribution
Apache License 2.0, copyright 2026 Vatsal Shah. Redistributions must keep LICENSE and NOTICE. There are no bundled third-party components (THIRD_PARTY_NOTICES.md).
Warranty and liability
Provided "as is", without warranty. Reports are advisory. Using DeploySutra does not transfer responsibility for a deployment decision, a security assessment or a compliance claim to the author.
What the project does not claim
- No approval, certification, audit opinion or compliance attestation (SOC 2, ISO 27001, PCI DSS, HIPAA and similar are not assessed).
- No guarantee of live state, reachability, IAM scope or recoverability.
- No independent benchmark of rule accuracy.
Names and trademarks
Third-party names are used for identification only. The name "DeploySutra" has not been trademark-searched; the npm package name and GitHub repository name were available when created. Do not assume legal uniqueness, and run your own clearance before commercial branding.
Privacy and data protection
No personal data is collected, transmitted or stored by the tool. Inputs you supply may contain personal or confidential data; they are processed locally and only the redacted analysis is written where you choose.
Governance
Maintainer: Vatsal Shah. The maintainer decides merges, releases, rule changes and moderation. Contributions need tests, a corpus case for any rule change, and an honest note of what was not tested. Automated or AI-generated suggestions are not authoritative. A Code of Conduct, security policy and support policy are in the repository root.
Vulnerability disclosure
Private GitHub security advisory; no live credentials in reports; acknowledgement within days, no SLA.
Provenance
Source is public. npm releases are published from CI with provenance when trusted publishing is configured. A manual publish has no provenance and is labelled as such in release notes. Reports carry an unkeyed SHA-256 seal, not a signature.
Using it in regulated settings
Treat it as one input to your change process. Keep human approvals, runtime admission control and your own audit trail. Cite the exact version and the recorded audit report if you need evidence of how the tool behaves.