Skip to content

Commit 45e2919

Browse files
chore: add SECURITY.md, dependabot.yml, CONTRIBUTING.md, LICENSE
1 parent 3c280b1 commit 45e2919

4 files changed

Lines changed: 92 additions & 0 deletions

File tree

.github/dependabot.yml

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: pip
4+
directory: "/"
5+
schedule:
6+
interval: weekly
7+
open-pull-requests-limit: 10
8+
9+
- package-ecosystem: github-actions
10+
directory: "/"
11+
schedule:
12+
interval: weekly

CONTRIBUTING.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Contributing to Revenue Holdings
2+
3+
Thank you for your interest in contributing!
4+
5+
## Development Setup
6+
7+
1. Fork the repository
8+
2. Clone your fork: `git clone https://github.com/YOUR_USERNAME/revenueholdings.git`
9+
3. Create a virtual environment: `python -m venv venv`
10+
4. Install dev dependencies: `pip install -e ".[dev]"`
11+
12+
## Making Changes
13+
14+
1. Create a feature branch: `git checkout -b feature/your-feature`
15+
2. Make your changes
16+
3. Run linting: `ruff check .`
17+
4. Run tests: `python -m pytest tests/ -x`
18+
5. Commit with a descriptive message
19+
6. Push and open a Pull Request
20+
21+
## Code Style
22+
23+
- We use [ruff](https://docs.astral.sh/ruff/) for linting
24+
- Line length: 120 characters
25+
- Python 3.10+ compatible
26+
27+
## Reporting Issues
28+
29+
Please open a GitHub issue with:
30+
31+
- Clear description of the problem
32+
- Steps to reproduce
33+
- Expected vs actual behavior

LICENSE

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2026 Coding Dev Tools
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

SECURITY.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
| Version | Supported |
6+
| ------- | ------------------ |
7+
| 0.x | :white_check_mark: |
8+
9+
## Reporting a Vulnerability
10+
11+
We take security seriously. If you discover a vulnerability, please report it responsibly.
12+
13+
**Do not** open a public GitHub issue for security vulnerabilities. Instead, please email security@codingdevtools.com with:
14+
15+
1. Description of the vulnerability
16+
2. Steps to reproduce
17+
3. Potential impact
18+
4. Any suggested fixes
19+
20+
We will acknowledge your report within 48 hours and aim to provide a fix within 7 days.
21+
22+
## Disclosure Policy
23+
24+
- We practice responsible disclosure
25+
- We ask that you give us reasonable time to fix the issue before public disclosure
26+
- We will credit researchers who report vulnerabilities (unless they prefer to remain anonymous)

0 commit comments

Comments
 (0)