Skip to content

0.10.0

Choose a tag to compare

View all tags
@cursor cursor released this 06 Oct 14:00
· 111 commits to development since this release
v0.10.0
6185d85
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.10.0 — Technique lists, visibility log sources, and a CLI proxy

6 October 2026. Minor on 0.9.0.

Upgrade and regenerate schemas with opentide generate. Rename technique lists to mitre_attack. Signal log sources come from visibility.toml. Signal severity uses alert labels. Regenerate CI with opentide setup ci so the install pin is exact. A root composition block is still accepted and is no longer required.

Install

pip install opentide==0.10.0
export OPENTIDE_REPO_ROOT=/path/to/detection-repo
opentide validate --strict

Regenerate editor schemas and templates with opentide generate.

Changed

  • Threat and objective technique lists are mitre_attack, pinned to att&ck::1.1. att&ck and attack are not accepted. Actor values stay scoped (att&ck::G0007).
  • objective.composition is required. A root composition block is accepted and ignored. Templates emit the block once, under objective.
  • signals[].data.logsources come from workspace visibility.toml.
  • Signal severity uses alert_severity::1.0. Threat severity stays the incident vocabulary.
  • detection_model accepts an objective UUID or a signal UUID.
  • opentide --proxy sets HTTP_PROXY and HTTPS_PROXY. [proxy], [cve].proxy, and tenant setup.proxy are errors that name the flag.
  • opentide setup ci installs opentide==<installed version>.

Fixed

  • Vocabulary extensions apply during validation. lint survives an unreadable file. setup vscode accepts JSONC. Duplicate YAML keys are rejected. info --strict fails when an object file did not load.

Verify

python -c "import opentide; print(opentide.__version__)"
opentide --help

Expect 0.10.0.

Links

Assets 2
Loading