Skip to content

docs: add a security policy - #19

Merged
mschmicking merged 1 commit into
mainfrom
docs/security-policy
Jul 31, 2026
Merged

docs: add a security policy#19
mschmicking merged 1 commit into
mainfrom
docs/security-policy

Conversation

@mschmicking

Copy link
Copy Markdown
Owner

GitHub's template is a supported-versions table and a placeholder sentence. This one is written around what the tool actually does: it points at credential storage, the path-traversal guards, and the auth/TLS handling, and records the deliberate trade-offs so they are not re-reported as bugs.

Private vulnerability reporting is enabled, so the report link works.

GitHub's template is a supported-versions table and a placeholder sentence,
which tells a researcher nothing. This one names where the risk actually
is — credential storage, the path guards that turn server-controlled ids
into filenames, the auth and TLS handling — so someone looking has
somewhere to start.

It also records the deliberate trade-offs so they need not be re-reported:
the stored password is a 0600 file rather than encrypted because there is
no portable keychain, there is no --password flag because argv is readable
via ps, allowSelfSigned accepts any certificate, and push is field-scoped
by design.

Response expectations are what one person in their spare time can actually
meet, rather than an SLA that would be missed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mschmicking
mschmicking merged commit 0b13d4a into main Jul 31, 2026
7 checks passed
@mschmicking
mschmicking deleted the docs/security-policy branch July 31, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant