Skip to content

docs: add contribution docs (#291)#300

Open
mariot wants to merge 1 commit into
mainfrom
docs/291
Open

docs: add contribution docs (#291)#300
mariot wants to merge 1 commit into
mainfrom
docs/291

Conversation

@mariot

@mariot mariot commented Mar 24, 2026

Copy link
Copy Markdown
Member

Proposed changes

  • Add docs

Testing Instructions

  1. Step-by-step how to test
  2. Environment or config notes

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality
  • For bug fix -> I implemented a test that covers the bug

Further comments

@mariot mariot requested a review from Kakudou March 24, 2026 05:33
@mariot mariot self-assigned this Mar 24, 2026
@mariot mariot added filigran team Item from the Filigran team. do not merge Do not merge until this label is removed. labels Mar 24, 2026
@guzmud guzmud self-requested a review March 24, 2026 09:06
@SamuelHassine SamuelHassine changed the title [all] feat(docs): add contribution docs (#291) docs: add contribution docs (#291) Jun 7, 2026
Copilot AI review requested due to automatic review settings June 19, 2026 07:17

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a collector-focused contribution guide to help contributors understand how to scaffold and implement a new OpenAEV collector in this repository, addressing the need in #291 for clearer contribution guidance (specifically around collector development).

Changes:

  • Add a new Markdown guide describing collector architecture, inputs/outputs, and a step-by-step creation flow.
  • Include example configuration, trace model shape, and suggested linting/testing commands for collectors.

Comment thread CONTRIBUTING-COLLECTOR.md
Comment on lines +38 to +42
- **OpenAEV connection**: URL and API token (see `config.yml`)
- **Collector metadata**: Unique collector ID, log level, etc.
- **Tool-specific settings**: API keys, FQDN, credentials, etc.

Example (`config.yml`):
Comment thread CONTRIBUTING-COLLECTOR.md
Comment on lines +48 to +50
collector:
id: 'Palo Alto Cortex XDR'
log_level: 'debug'
Comment thread CONTRIBUTING-COLLECTOR.md Outdated
Comment on lines +90 to +91
poetry new my-collector
cd my-collector
Comment thread CONTRIBUTING-COLLECTOR.md Outdated
Comment on lines +101 to +107
class ConfigLoader:
def __init__(self, config_path='src/config.yml'):
with open(config_path) as f:
self.config = yaml.safe_load(f)
# Optionally override with env vars
self.config['openaev']['token'] = os.getenv('OPENAEV_TOKEN', self.config['openaev']['token'])
```
Comment thread CONTRIBUTING-COLLECTOR.md
Comment on lines +1 to +4
# Contribution Guide: Creating a New Collector for OpenAEV

## Overview
A collector integrates a security tool (EDR, XDR, SIEM, etc.) with the OpenAEV platform, fetching relevant data and transforming it into a standard format for analysis and validation. Each collector runs as a standalone service, following a common architecture and interface.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Do not merge until this label is removed. filigran team Item from the Filigran team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: create a contribution guide for OpenAEV

3 participants