@devries-cameron20 / composio Mirror · read-only / commits / fe70f6316
Fork 0

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

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 22, 17:00 UTC

chore: adds relevant github policies

acsrujan committed Dec 17, 2025 at 10:54 UTC fe70f63164901b59d972571f9572a2554ee35f7d
4 files changed +138
.github/CODE_OF_CONDUCT.md new
+47
@@ -0,0 +1,47 @@
1 +# Code of Conduct
2 +
3 +This project and community (including our Discord server) are dedicated to providing a welcoming, safe, and collaborative environment for everyone.
4 +
5 +## Our Pledge
6 +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.
7 +
8 +## Our Standards
9 +Examples of behavior that contributes to a positive environment include:
10 +- Being kind, respectful, and considerate
11 +- Giving and gracefully accepting constructive feedback
12 +- Focusing on what is best for the community
13 +- Showing empathy toward other community members
14 +
15 +Examples of unacceptable behavior include:
16 +- Harassment, discrimination, or hate speech
17 +- Public or private harassment, including unwelcome sexual attention
18 +- Trolling, insulting/derogatory comments, and personal or political attacks
19 +- Publishing others' private information ("doxxing") without explicit permission
20 +- Advertising, spam, or off‑topic self‑promotion in project channels
21 +- Any behavior that would be illegal or violates platform Terms of Service
22 +
23 +## Discord‑Specific Guidelines
24 +Our Discord is an extension of this community:
25 +- Use appropriate channels; keep topics on‑topic for each channel
26 +- No unsolicited DMs for support or promotion; ask before DMing
27 +- Respect moderators and follow their directions; do not argue moderation in public channels
28 +- Report suspicious links or abuse to moderators immediately
29 +- Follow Discord’s Terms of Service and Community Guidelines
30 +
31 +## Enforcement Responsibilities
32 +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.
33 +
34 +## Scope
35 +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.
36 +
37 +## Reporting
38 +If you experience or witness unacceptable behavior, report it to the maintainers at support@composio.dev or via a direct message to the Discord moderators. All good‑faith reports will be reviewed and investigated promptly and fairly.
39 +
40 +## Enforcement Guidelines
41 +- Correction: Private, written warning and guidance
42 +- Warning: Official warning with consequences for continued behavior
43 +- Temporary Ban: Temporary removal from community spaces
44 +- Permanent Ban: Permanent removal from community spaces
45 +
46 +## Attribution
47 +This Code of Conduct is adapted from common open‑source community standards, including the Contributor Covenant.
.github/PULL_REQUEST_TEMPLATE.md new
+29
@@ -0,0 +1,29 @@
1 +## Summary
2 +Explain the motivation and context for this change. Link to any related issues.
3 +
4 +Fixes #
5 +
6 +## Changes
7 +-
8 +-
9 +
10 +## Type of change
11 +- [ ] Bug fix
12 +- [ ] New feature
13 +- [ ] Refactor/Chore
14 +- [ ] Documentation
15 +- [ ] Breaking change
16 +
17 +## How Has This Been Tested?
18 +Describe the tests you ran and instructions so reviewers can reproduce. Include any relevant config/versions.
19 +
20 +## Screenshots (if applicable)
21 +
22 +## Checklist
23 +- [ ] I have read the Code of Conduct and this PR adheres to it
24 +- [ ] I ran linters/tests locally and they passed
25 +- [ ] I updated documentation as needed
26 +- [ ] I added tests or explain why not applicable
27 +- [ ] I added a changeset if this change affects published packages
28 +
29 +## Additional context
.github/SECURITY.md new
+46
@@ -0,0 +1,46 @@
1 +# Security Policy
2 +
3 +## Reporting a Vulnerability
4 +
5 +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 security@composio.dev
6 +
7 +### How to Report
8 +
9 +**Please do not report security vulnerabilities through public GitHub issues.**
10 +
11 +Instead, please report them using one of the following methods:
12 +
13 +1. **GitHub Security Advisory (Preferred)**: Report a vulnerability directly through GitHub by visiting:
14 + - https://github.com/composiohq/composio/security/advisories/new
15 +
16 +2. **Email**: If you prefer not to use GitHub Security Advisories, you can email security concerns to the maintainers.
17 +
18 +### What to Include
19 +
20 +Please include as much of the following information as possible:
21 +
22 +- Type of vulnerability
23 +- Full paths of source file(s) related to the vulnerability
24 +- Location of the affected source code (tag/branch/commit or direct URL)
25 +- Step-by-step instructions to reproduce the issue
26 +- Proof-of-concept or exploit code (if possible)
27 +- Impact of the vulnerability, including how an attacker might exploit it
28 +
29 +### Response Timeline
30 +
31 +- We will acknowledge your report within 48 hours
32 +- We will provide a more detailed response within 7 days indicating the next steps
33 +- We will keep you informed of the progress toward resolving the issue
34 +- We may ask for additional information or guidance
35 +
36 +## Supported Versions
37 +
38 +We release patches for security vulnerabilities. Please ensure you are using the latest version of Composio.
39 +
40 +## Disclosure Policy
41 +
42 +- We follow coordinated disclosure practices
43 +- Security advisories will be published after a fix is available
44 +- We appreciate responsible disclosure and will acknowledge reporters in the advisory (unless you prefer to remain anonymous)
45 +
46 +Thank you for helping keep Composio and our users safe!
.github/SUPPORT.md new
+16
@@ -0,0 +1,16 @@
1 +# Support
2 +
3 +Thanks for using Composio! If you need help, use the following channels:
4 +
5 +- Documentation: https://docs.composio.dev
6 +- Discord: https://discord.gg/composio (best for community help and quick questions)
7 +- Email: support@composio.dev (account issues, private questions, or if you can’t use Discord)
8 +
9 +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`.
10 +
11 +## Before asking for help
12 +- Check open and closed issues
13 +- Search the docs and Discord
14 +- Include versions, logs, minimal repro steps, and expected vs. actual behavior
15 +
16 +We do our best to respond within 2–3 business days.