Contact
Start with the route that owns the problem.
A scientific correction, account issue, and site-security report need different context. Use the closest path below and never send passwords, session tokens, private keys, authorization codes, or repository secrets.
Do not post account data, private repository names, session information, or security details publicly. Account, privacy, accessibility, and security requests require a monitored private channel before release.
Correct scientific information
Open the exact Problem, source, or Contribution first. Its collection, source revision, and technical details identify what needs correction. A correction does not silently rewrite signed history; the relevant source or Repository records the change.
Add scientific work
Use Add a contribution to choose a Problem, check prior work, attach evidence, and prepare a Repository handoff. This is also the route for importing a selected GitHub repository.
Account or connected code
Signed-in users can inspect their account and current session at Account, and manage GitHub installations or connected repositories at Connections.
Privacy, accessibility, security, or a site bug
A verified private contact address has not been published for this release. Private support must be configured before public launch.