LinkedIn contact
Start a commercial conversation.
Use LinkedIn for an initial commercial self-hosted conversation, deployment assumptions, release workflow notes, or commercial licensing questions.
Release dossier verify-ready
01
Artifact digest
02
SBOM inventory
03
Vulnerability decision
04
Signed package
What to include
- your intended use
- target deployment model
- AGPL or commercial concerns
- support expectations
- target release workflow
- preferred next step
Do not send sensitive evidence
Do not send raw evidence payloads, bearer tokens, private keys, database URLs, customer data, or unreleased package contents through LinkedIn or any public contact path.
Use the first message only for brief, non-sensitive context. A safer private channel can be agreed separately if needed.
Next step
Evaluate the technical truth on GitHub.
The website qualifies the business problem. The repository remains the source of truth for code, docs, release artifacts, limitations, and verification evidence.