1. Local network boundary
The proxy should listen on 127.0.0.1 by default, reject unsolicited LAN access, use explicit ports, and avoid exposing an unauthenticated administrative interface.
2. Secret handling
API keys should remain in local environment variables, never appear in logs or crash reports, and be redacted from diagnostics. The doctor command should report presence, not value.
3. Bounded and inspectable transforms
Profiles should be schema-validated and restricted to explicitly allowed fields. Users should be able to inspect the before-and-after request diff and disable control per run.
4. Signed remote configuration
If profiles are updated remotely, the client should accept data-only configuration, verify signatures, schema, model compatibility, expiry, and runtime version, and never execute remotely supplied code.
5. Safe pass-through
When the control layer is unavailable or a profile is invalid, the original request should continue unchanged. The profile service must not become a new single point of failure.
6. Vulnerability disclosure
Please do not publish an unpatched vulnerability before SeedSky has had a reasonable opportunity to investigate. Send a concise report with affected version, reproduction steps, and impact to:
hello@seedsky.ai