django-report-builder
A GUI for Django ORM. Build custom queries and display results. Targets sysadmins and capable end users who might not be able to program or gain direct interactive shell access.
Status
Maintained and feature-complete. This project is no longer accepting new features — the scope is what's already shipped, and that's the project's strength: it does what it does, well, without churn.
Bug reports are welcome, especially when paired with a fix. Issues opened without a reproduction or proposed patch will likely sit. Please open them on GitLab.
For the version history, see CHANGELOG.
What is Django Report Builder?
A staff-facing UI that lets users:
- Pick a root model, drag in display fields, and traverse related models several levels deep
- Add filters with the full set of Django ORM lookup types (
exact,gt,icontains,range,relative_range,isnull, regex, etc.) - Preview results in the browser and export to xlsx or csv
- Optionally hand off long-running exports to a background task queue
(Celery or
django-tasks) - Schedule reports to run on a recurring basis and email the results
- Trigger a report from a Django admin change-list as a global action
Report builder is intended for trusted staff users — access is gated on
is_staff, and the standard Django change/view permissions control who can
see existing reports.
Documentation
django-report-builder.docs.burkesoftware.com
Development quickstart
The repo ships a Django demo project plus the Angular SPA. The fastest path:
docker compose up— starts Postgres and the Django dev server on:8000docker compose run --rm web ./manage.py migratedocker compose run --rm web ./manage.py createsuperusercd js && npm install && npm start— Angular dev server with hot reload, proxying API requests to Django- Open http://localhost:8000/admin, log in, then visit the URL the Angular
CLI prints (
/report_builderon the dev-server port)
For deeper notes, see docs/contributors.md.
If your Django project needs error tracking or performance monitoring, take a look at GlitchTip — my open-source, Sentry-compatible error tracker.
2 maintainers
Metadata
2 maintainers
Release files for django-report-builder 7.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_report_builder-7.1.0.tar.gz | 198.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_report_builder-7.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 408.9 kB
Release files / django_report_builder-7.1.0.tar.gz
| Download URL | django_report_builder-7.1.0.tar.gz |
|---|---|
| Size | 198.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a1f7841abe198540f268f862472a40fb8e1b8870a077479249ed9b948cae8c9
|
|
BLAKE2b-256 checksum How to use checksums |
e771805b37fc326fa328cb0a3bdbb3aea8caf8b6a99c5f65046c2ccb41ea69e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / django_report_builder-7.1.0-py3-none-any.whl
| Download URL | django_report_builder-7.1.0-py3-none-any.whl |
|---|---|
| Size | 210.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4dfc0569b23cd33e3950e94e9c82d9bcfa593dea3da27972edc88532839604b9
|
|
BLAKE2b-256 checksum How to use checksums |
2982f6d3b8b074e7995ac7ef49b314e89682c4494f86a95d0405d1f7c4bae7ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for django-report-builder 7.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
