Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

chore: adds relevant github policies

acsrujanfe70f6316490
diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md
new file mode 100644
index 000000000..725cd21df
--- /dev/null
+++ b/.github/CODE_OF_CONDUCT.md
@@ -0,0 +1,47 @@
+# Code of Conduct
+
+This project and community (including our Discord server) are dedicated to providing a welcoming, safe, and collaborative environment for everyone.
+
+## Our Pledge
+We, as maintainers and contributors, pledge to make participation in our community a harassment‑free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio‑economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+Examples of behavior that contributes to a positive environment include:
+- Being kind, respectful, and considerate
+- Giving and gracefully accepting constructive feedback
+- Focusing on what is best for the community
+- Showing empathy toward other community members
+
+Examples of unacceptable behavior include:
+- Harassment, discrimination, or hate speech
+- Public or private harassment, including unwelcome sexual attention
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Publishing others' private information ("doxxing") without explicit permission
+- Advertising, spam, or off‑topic self‑promotion in project channels
+- Any behavior that would be illegal or violates platform Terms of Service
+
+## Discord‑Specific Guidelines
+Our Discord is an extension of this community:
+- Use appropriate channels; keep topics on‑topic for each channel
+- No unsolicited DMs for support or promotion; ask before DMing
+- Respect moderators and follow their directions; do not argue moderation in public channels
+- Report suspicious links or abuse to moderators immediately
+- Follow Discord’s Terms of Service and Community Guidelines
+
+## Enforcement Responsibilities
+Project maintainers and Discord moderators are responsible for clarifying and enforcing standards. They may take appropriate and fair corrective action in response to any behavior they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+This Code applies within all community spaces—GitHub repositories, issues, pull requests, and our Discord—and when an individual is officially representing the community in public spaces.
+
+## Reporting
+If you experience or witness unacceptable behavior, report it to the maintainers at [email protected] or via a direct message to the Discord moderators. All good‑faith reports will be reviewed and investigated promptly and fairly.
+
+## Enforcement Guidelines
+- Correction: Private, written warning and guidance
+- Warning: Official warning with consequences for continued behavior
+- Temporary Ban: Temporary removal from community spaces
+- Permanent Ban: Permanent removal from community spaces
+
+## Attribution
+This Code of Conduct is adapted from common open‑source community standards, including the Contributor Covenant.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 000000000..b00054ec4
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,29 @@
+## Summary
+Explain the motivation and context for this change. Link to any related issues.
+
+Fixes #
+
+## Changes
+-
+-
+
+## Type of change
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Refactor/Chore
+- [ ] Documentation
+- [ ] Breaking change
+
+## How Has This Been Tested?
+Describe the tests you ran and instructions so reviewers can reproduce. Include any relevant config/versions.
+
+## Screenshots (if applicable)
+
+## Checklist
+- [ ] I have read the Code of Conduct and this PR adheres to it
+- [ ] I ran linters/tests locally and they passed
+- [ ] I updated documentation as needed
+- [ ] I added tests or explain why not applicable
+- [ ] I added a changeset if this change affects published packages
+
+## Additional context
diff --git a/.github/SECURITY.md b/.github/SECURITY.md
new file mode 100644
index 000000000..a37bc9324
--- /dev/null
+++ b/.github/SECURITY.md
@@ -0,0 +1,46 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+We take the security of Composio seriously. If you believe you have found a security vulnerability, please report it to us through GitHub Security Advisories or drop us an email at [email protected]
+
+### How to Report
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them using one of the following methods:
+
+1. **GitHub Security Advisory (Preferred)**: Report a vulnerability directly through GitHub by visiting:
+ - https://github.com/composiohq/composio/security/advisories/new
+
+2. **Email**: If you prefer not to use GitHub Security Advisories, you can email security concerns to the maintainers.
+
+### What to Include
+
+Please include as much of the following information as possible:
+
+- Type of vulnerability
+- Full paths of source file(s) related to the vulnerability
+- Location of the affected source code (tag/branch/commit or direct URL)
+- Step-by-step instructions to reproduce the issue
+- Proof-of-concept or exploit code (if possible)
+- Impact of the vulnerability, including how an attacker might exploit it
+
+### Response Timeline
+
+- We will acknowledge your report within 48 hours
+- We will provide a more detailed response within 7 days indicating the next steps
+- We will keep you informed of the progress toward resolving the issue
+- We may ask for additional information or guidance
+
+## Supported Versions
+
+We release patches for security vulnerabilities. Please ensure you are using the latest version of Composio.
+
+## Disclosure Policy
+
+- We follow coordinated disclosure practices
+- Security advisories will be published after a fix is available
+- We appreciate responsible disclosure and will acknowledge reporters in the advisory (unless you prefer to remain anonymous)
+
+Thank you for helping keep Composio and our users safe!
diff --git a/.github/SUPPORT.md b/.github/SUPPORT.md
new file mode 100644
index 000000000..a8c0b0552
--- /dev/null
+++ b/.github/SUPPORT.md
@@ -0,0 +1,16 @@
+# Support
+
+Thanks for using Composio! If you need help, use the following channels:
+
+- Documentation: https://docs.composio.dev
+- Discord: https://discord.gg/composio (best for community help and quick questions)
+- Email: [email protected] (account issues, private questions, or if you can’t use Discord)
+
+Please avoid filing support requests as GitHub issues unless you believe you’ve found a bug. For security issues, do not open a public issue—follow `.github/SECURITY.md`.
+
+## Before asking for help
+- Check open and closed issues
+- Search the docs and Discord
+- Include versions, logs, minimal repro steps, and expected vs. actual behavior
+
+We do our best to respond within 2–3 business days.