Skip to content

Contribute and maintain

This path is for people changing the project, reviewing evidence, or operating its release and repository workflows. It is secondary to the operator task chooser.

Contribute safely

Public examples must not contain credentials, private infrastructure details, deployment identifiers, or raw sensitive logs.

Monitoring ingestion for Zabbix, Checkmk, Nagios/Icinga, and Prometheus remains community-testing work. Read Monitoring, then contribute sanitized evidence through community testing issue #62.

Maintain the repository

I want to… Read this
manage issues, labels, SOS triage, and upstream monitoring Maintainer workflow
understand origin, naming, and AI-assisted development transparency Project origin and transparency
inspect every lifecycle command and option Shell scripts reference
understand manager, upstream, and component versions Versioning and upstream input policy
review the supported deployment architecture Architecture, security, and support matrix

Release and evidence

I want to… Read this
cut and verify a release Release process
review artifact integrity controls Release integrity and provenance
inspect the current validated component tuple Compatibility, current validation, and validation matrix
inspect retained historical evidence Validation evidence archive
review current release posture Production readiness

Compatibility claims remain tied to immutable manager release tags and the exact official component set that passed validation.

Project identity

Read Brand assets and the canonical asset license and usage notice before reusing the MISP DLM identity. The repository software remains GPL-3.0; the visual assets have their own terms.

Return to operator documentation

Go back to the task-first documentation homepage for support, installation, operation, recovery, secure deployment, troubleshooting, and compatibility-evidence paths.