Security
Byspec exists to make a claim you can check. The same standard applies to how it handles your code.
- No telemetry. The CLI makes no network calls other than to the model provider you configure. There is no usage reporting and no phone-home.
- Evidence encrypted at rest. In the hosted control plane every report, evidence file and packet is stored in S3 under SSE-KMS with a dedicated key. Evidence is written with mode 0600 locally.
- Signed ledgers. Hosted ledger entries are signed with an asymmetric KMS key (ECDSA P-256); local ledgers can be signed with an ed25519 key. Signatures sit outside the hashed payload, and packets carry the public key so anyone can verify offline.
- Sandbox isolation. Pull requests are verified in CodeBuild containers that never run in privileged mode. In isolated stages the container has no NAT gateway and reaches only S3, CloudWatch Logs, KMS and Bedrock through VPC endpoints, so a
commandortestcheck cannot reach the internet. - Least privilege by prefix. The sandbox can read and write only its own run's prefix in S3. Clone tokens are short-lived installation tokens, stored encrypted and deleted when the run ends.
- The judge is isolated. The model receives only the criterion, its rubric and the evidence it declares; never the diff, the repository or your environment.
- Retention. Evidence and packets expire after 400 days by default. Ledger entries are kept.
- Your own infrastructure is an option. The control plane is open source and deploys to your AWS account with one command; the CLI and Action need no hosted service at all.
The full list of properties, including what the CLI does not protect, is in the security documentation. Report a vulnerability to hello@byspec.ai.