djangofp fetches Django's admin CSS assets from a target site, fingerprints them by size and SHA256, and compares them against a local signature database.
This helps identify the Django version, or narrow down candidates, based on unique static asset fingerprints.
How It Works
djangofp requests the Django admin CSS files from the target site, computes SHA256 and size fingerprints, and compares them against a built-in database of known Django releases.
The fingerprint database currently covers Django versions 4.1.x through 6.0.5 (latest release).
Admin CSS assets used for matching were introduced in Django 4.1 and do not exist in earlier versions.
Installation
You can install djangofp using pipx:
pipx install djangofp
Usage
djangofp https://example.com
Example
$ djangofp https://example.com
[+] base: size=22154 sha256=2374a875...
[+] forms: size=8525 sha256=bccb52c9...
[+] dashboard: size=441 sha256=882cfb2a...
[+] responsive: size=16632 sha256=890d9ac7...
[+] exact match: 18894b0...
versions: 5.2
1 maintainer
Metadata
1 maintainer
Release files for djangofp 0.4.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 | |
|---|---|---|---|
| djangofp-0.4.0.tar.gz | 8.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| djangofp-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.4 kB
Release files / djangofp-0.4.0.tar.gz
| Download URL | djangofp-0.4.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6569fd32682818e546c203eefe5dcaba2206fc8a98f65b1240ed41ddc229a3ca
|
|
BLAKE2b-256 checksum How to use checksums |
84059d5d8c44f555210d21dbc902be1aeb80909b1cdc9faefd947abe89b3602b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logRelease files / djangofp-0.4.0-py3-none-any.whl
| Download URL | djangofp-0.4.0-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79f75b03ec5af007844c93e6b0e1f47170707848c04045cc64407607af7047a7
|
|
BLAKE2b-256 checksum How to use checksums |
62aebe7a160a638fb48a29fccf48b6276540615b7dfd21d21792a7457072ddf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency log
