GitHub is where the work ships. Malveon connects over OAuth, reads the signals that tell you what is changing, and verifies every webhook it receives.
What it reads
Malveon reads pull requests, check status, and deployment events from the repositories you select. These feed the Malvedeck health engine (CI failure rate) and the Malviont CI/CD hub.
A note on scope and honesty: the GitHub OAuth grant includes repository access, which is broader than read-only at the token level. Malveon’s behavior is read-oriented. It reads metadata (titles, statuses, events), not your source files, and it does not push to your repositories.
What it writes
Where you ask it to, Malveon can create a GitHub issue (for example, from an automation in the Malviont CI/CD hub). It registers webhooks on the repositories you connect so events arrive in real time.
Security
GitHub webhooks are verified with an x-hub-signature-256 HMAC before processing. Mismatched events are rejected. Tokens are encrypted at rest with AES-256-GCM.