5 Commits
Author SHA1 Message Date
zeekay c6a60aea35 docs: cut the explanatory prose from the README; drop the stale changelog and boilerplate contributing guide 2026-08-23 12:12:51 -07:00
zeekay f7b2eda6ca Report vulnerabilities to us, not to the upstream we forked
This repo is a fork, and its SECURITY.md still carried the upstream's contact —
so a researcher who found a hole in what WE ship was told to mail a vendor who
cannot fix it, and who would then know about a live vulnerability in our
production before we did.

Fourteen repos were in that state: datastore -> [email protected], git and
its two worktrees -> [email protected], auto -> [email protected],
calendar -> [email protected], dns -> [email protected], python-sdk ->
[email protected], plus bot, gui-gates, gui-geist, playground and
playground-oauthcb pointing at brand domains with no mailbox behind them.

All of them now carry one policy and one address, [email protected], matching
what cloud and gateway already used. The policy says out loud to report here
rather than upstream, because the next fork will inherit the same file and the
same instinct.
2026-08-13 14:42:32 -07:00
stainless-app[bot] d95211a0e5 feat(api): update via SDK Studio (#6) 2025-03-17 17:46:01 +00:00
stainless-app[bot] db09188901 feat(api): update via SDK Studio (#4) 2025-03-15 03:56:11 +00:00
stainless-app[bot] 9626b2b0d6 initial commit 2025-03-15 03:31:14 +00:00