| Version | Supported |
|---|---|
| 0.1.x | Yes |
If you discover a security vulnerability in workledger, please report it responsibly.
Do not open a public GitHub issue for security vulnerabilities.
Use GitHub's private vulnerability reporting flow for this repository when the Security tab shows Report a vulnerability.
If private reporting is not available, open a regular GitHub issue that asks for a private follow-up path, but do not include exploit details or sensitive data in the public issue.
For non-sensitive bugs or hardening suggestions, use the normal bug-report workflow.
workledger is community-maintained, so security review and response are best effort. No response timeline is guaranteed.
The following are in scope:
- The
workledgerPython package (src/workledger/) - The
workledger-serverFastAPI application (src/workledger_server/) - The
workledger_observeSDK (src/workledger_observe/) - Policy pack evaluation logic
- DuckDB storage layer
The following are out of scope:
- Demo scripts and example data
- Documentation site infrastructure
- Third-party dependencies (please report those to the respective maintainers)
We prefer coordinated disclosure when a maintainer is available to engage. Any timeline for disclosure or credit will be agreed case by case through the GitHub reporting thread.
This repository enforces the following safeguards:
- Branch protection on
main: Direct pushes are prohibited. All changes must go through a pull request. - Required reviews: At least one approving review from a code owner is required before merging.
- Required status checks: CI must pass (lint, type-check, test) before a PR can merge.
- CODEOWNERS: All file changes require review from
@couscous18. - Dependabot: Enabled for automated dependency vulnerability alerts.
- Code scanning: GitHub Advanced Security code scanning is enabled.
- Secret scanning: Prevents accidental credential leaks in commits.
These settings must be configured manually in Settings → Branches → Branch protection rules for main:
- ✅ Require a pull request before merging
- ✅ Require approvals (1)
- ✅ Require review from Code Owners
- ✅ Require status checks to pass before merging — add:
test - ✅ Require conversation resolution before merging
- ✅ Do not allow bypassing the above settings
Under Settings → Code security and analysis, enable:
- ✅ Dependabot alerts
- ✅ Dependabot security updates
- ✅ Code scanning (CodeQL)
- ✅ Secret scanning
workledger processes AI trace data that may contain sensitive information:
- PII in traces: Raw LLM spans may contain user inputs. Use the
mask_piifacet and configure your ingestion pipeline to redact sensitive fields before they reach workledger. - Cost data: Work unit cost figures may be commercially sensitive. Restrict access to the DuckDB file and exported reports.
- Policy decisions: Accounting classifications are candidate interpretations, not authoritative. Do not use them as the sole basis for financial reporting without human review.