Pre-release support availability
No public support SLA or monitored security mailbox is certified here. Use the established private maintainer channel for your authorized build. A public issue tracker is not represented as available while repository publication remains unapproved.
Before public release, provision and test a private vulnerability-reporting route, publish its exact address/link and define response expectations. Do not substitute an invented contact or expose vulnerability details in a public thread.
Prepare a bounded reproduction
- Record
commandem version, app build, OS and timestamp. - Describe the action, expected result, observed result and whether a retry changed it.
- Include a content-free error or a redacted fictional reproduction. Preserve original receipts locally.
- Never attach raw environments, credential files, private account labels or complete real transcripts.
Report a suspected vulnerability privately
If an authorized repository's Security tab actually offers Report a vulnerability, use that private route. Otherwise request an established private contact without disclosing the vulnerability publicly. This page does not certify that GitHub private reporting is enabled.
Remove data deliberately
- Inventory projects, history, receipts and notes you need to keep. Back up required local state first.
- Removing the app bundle does not remove Commandem's local state or provider-owned credentials/history.
- Inspect the specific application's data directory and the provider's controls. Delete only confirmed targets; there is no recommended blanket cleanup command.
- Local deletion does not remove copies sent to providers or sync destinations. Use each service's verified deletion process.
See Privacy, Security and troubleshooting. This is operational guidance, not a legal-compliance certification.