Skip to content

Security: PartBuddy/partbuddy

Security

SECURITY.md

Security policy

Reporting a vulnerability

The repository is private; only invited collaborators can read it. Report vulnerabilities as an issue with the label type: security and mark sensitive details as such. A public reporting channel (security contact address or GitHub private vulnerability reporting) is set up before the first public release.

Include the affected version, the steps to reproduce and the impact you expect. Remove personal data, API keys and model files from logs before attaching them.

We acknowledge reports within five working days and agree on a disclosure date with you once a fix is available.

Supported versions

The project is in pre-release development. Until version 1.0.0 only the latest release receives security fixes.

Security principles

  • API keys of users are stored only in the operating system's credential store (Windows Credential Manager / DPAPI for the current user), never in plain text, never in logs or crash reports.
  • AI providers, local model servers and the CAD kernel are reached only through endpoints the user configured. Tool calls of the assistant are validated against schemas and pass the same check gates as manual actions.
  • Dependencies are pinned to exact versions with lockfile integrity hashes; GitHub Actions are pinned to commit SHAs. Dependency updates wait seven days after release.
  • Every commit is scanned for secrets and personal data locally (pre-commit hook) and in CI.

There aren't any published security advisories