Description

📌 The first PR that meets the quality standard will be accepted and the bounty will be closed.

SpiceDB powers fine-grained access control — but subtle misconfigurations or known bugs can block critical permissions.

Your task: Reproduce a high-severity failure in a recent version of SpiceDB and write a detection rule that reliably identifies the issue in production environments.

✅ You must:

1. Reproduce the failure scenario.
2. Share a minimal, working reproduction (e.g., Helm, Docker Compose, etc.).
3. Write a CRE-format detection rule for preq.
4. Install preq and run the rule.

📦 Deliverables:

• Reproduction setup and clear README
  • create a private repo and invite the maintainers (@tonymeehan @Lyndon-prequel)
• Link to your rule in the CRE playground.
• PR containing
  • the new CRE rule
  • example logs in test.log.
  • updated tags.yaml and category.yaml files
• Short demo video of
  • your reproduction
  • running the rule. i.e cat test.log | preq -r your_rule.yaml -d

💰 /bounty $250

Rule

No response

Related issues or PRs

No response

References

No response

Redacted Example Data

No response