AnalyView
AnalyView is a command-line tool that scans a Python/Django project and gives you an interactive visual overview of its structure — Python files, HTML templates, and Django apps — right in your browser.
Point it at a project folder and get an instant snapshot of what's inside, no configuration needed.
Installation
pip install analyview
Requires Python 3.9+.
Commands
analyview scan
Scans a project directory and prints a summary to the terminal.
analyview scan .
Or point it at any folder:
analyview scan D:\git\MyProject
What it reports:
- Total number of Python (
.py) files found - Total number of HTML template files found
- Detected Django apps (folders containing both
models.pyandviews.py)
The scan automatically skips virtual environments, node_modules, .git, build folders, and broken symlinks — so it's safe to run on any real-world project without manual cleanup.
analyview serve
Launches a local web app so you can explore the project's structure visually instead of just reading a terminal summary.
analyview serve .
This starts a server (default: http://127.0.0.1:9001) — open the printed URL in your browser to view the interactive layout of your project.
Optional flags:
| Flag | Description | Default |
|---|---|---|
--host |
Host address to bind to | 127.0.0.1 |
--port |
Port to serve on | 9001 |
Example with custom host/port:
analyview serve . --host 0.0.0.0 --port 9002
Press Ctrl+C to stop the server.
What counts as a "Django app"?
AnalyView uses a simple, reliable heuristic: any directory that contains both a models.py and a views.py file is treated as a Django app. This works without needing your project's settings, installed apps list, or any Django-specific configuration.
Notes
- Works on any Python project, not just Django ones — non-Django projects will simply show
0Django apps. - Safe on Windows, including projects with virtual environments that use symlinks/junctions (a common source of crashes in other scanning tools).
- No internet connection or external services required — everything runs locally.
Metadata
Release files for analyview 0.1.3
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 | Actions |
|---|---|---|---|---|
| analyview-0.1.3.tar.gz | 178.5 kB | Without provenance | Details for analyview-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| analyview-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for analyview-0.1.3-py3-none-any.whl |
Total release size: 364.8 kB
Release files / analyview-0.1.3.tar.gz
| Download URL | analyview-0.1.3.tar.gz |
|---|---|
| Size | 178.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
292223ee72e6eb83822d0d6e1af3cd50684eca3896f87b129ee9bfdfa4a738f6
|
|
BLAKE2b-256 checksum How to use checksums |
05da347e553e34a516876ce269f8248f45f8a9d6b05be3792c4fcd17bb15ba37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.0
|
Release files / analyview-0.1.3-py3-none-any.whl
| Download URL | analyview-0.1.3-py3-none-any.whl |
|---|---|
| Size | 186.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2da2764b8e3d8161c1a25d540e047e4772536ed33f6f55b5a784dcfef1145500
|
|
BLAKE2b-256 checksum How to use checksums |
b0ae2bf1f8bbb6f4b5feb633c7834c45da18726b46428d22ff7e7ad21aed8ecc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.0
|
Security for analyview 0.1.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.