Skip to main content

​
New features

​
Check failure threshold

Control when the Oplane Security Review check reports Fail by setting a severity threshold. Combined with your CI pipeline’s branch protection rules, this acts as a merge gate to prevent unresolved requirements at the level of your choosing from slipping through.
  • Catch issues earlier — security requirements surface during code review, not after deployment.
  • Configurable threshold — choose critical, high, medium, low, or any. Info-severity findings never cause a failure.
  • No extra pushes needed — resolving a requirement in Oplane clears the failing check on the last reviewed commit.
  • You stay in control — the threshold is opt-in per workspace; your CI pipeline decides whether to block merges based on the check result.
See Check failure threshold for the full setup.

​
Claim your Git namespace

Organisations can now claim a GitHub organisation or GitLab group so only their Oplane workspaces can subscribe to repositories under it. This ensures all threat models and security data for your repositories stay within your Oplane organisation — even when team members connect via personal Git accounts.
  • Data stays in your org — threat models for claimed repositories belong to your organisation, not scattered across personal workspaces.
  • Clear ownership — no confusion about which Oplane organisation owns which repositories when multiple teams share a Git provider.
  • Resilient coverage — PR reviews keep working even if the user who connected the repository leaves or loses access.
See Namespace claims for details.