Skip to content

Security: cloudlabworks/oak-events

SECURITY.md

Security policy

Reporting a vulnerability

Please report security issues privately through GitHub's security advisories: open the repository's Security tab and choose Report a vulnerability. Do not open a public issue for security problems.

Include what you found, how to reproduce it, and the impact you expect. You should get an acknowledgement within a week.

How reports are handled

Reports are triaged, fixed and disclosed under the CloudLab Works incident response plan, which sets severity levels, fix targets and coordinated disclosure timelines. The threat model lists the threats this project defends against.

In scope

Anything that breaks the privacy model described in the README, for example:

  • a code path that sends colour frames to the host, or writes any image or depth map to disk,
  • DepthAI telemetry, crash-dump upload or auto-calibration being enabled without OAK_EVENTS_ALLOW_TELEMETRY=1,
  • the MCP server exposing anything other than event data, reading files outside the events directory, or touching the camera,
  • event files being created with permissions broader than the owner.

Verifying a release

From the release after 0.1.2, each version tag builds the sdist and wheel once, records build provenance for them through Sigstore, publishes them to PyPI and attaches the same files and oak_events-<version>.intoto.jsonl to the GitHub Release. To check a downloaded file:

gh attestation verify oak_events-<version>-py3-none-any.whl --repo cloudlabworks/oak-events

Add --bundle oak_events-<version>.intoto.jsonl to verify against the bundle from the release instead of the GitHub attestations API. PyPI also serves PEP 740 publish attestations for every file it hosts.

Supported versions

Only the latest release receives fixes while the project is pre-1.0.

There aren't any published security advisories