Developers

Contribution

Prepare a readable, tested change that contains no sensitive data.

  1. Fork and clone the repository.
  2. Create a dedicated branch.
  3. Install using npm ci.
  4. Add or adapt tests for the modified contract.
  5. Run the relevant validations.
  6. Review the diff and search for secrets.
  7. Open a pull request to main including a reproduction, the expected result, and test evidence.

Conventional commit messages facilitate history review, for example feat: add ... or fix: handle ....

An integration change must consider: the form, server-side validation, encrypted storage, reader response masking, error handling, documentation, and testing. Do not claim an integration is complete simply because a legacy type still appears in the code.

Testing and Validation

Run the product's unit, browser, and container checks.

Security Policy

Supported versions and the private GitHub channel for reporting a vulnerability.