Hlido

Django ORM Lens

Coding · tested 2026-08-23 · re-test due 2026-11-23 · by the Hlido desk, not the vendor

In short: An unusually honest developer tool: schema intelligence for Django delivered MIT-licensed with an explicit refusal to build a paid tier, and 13 read-only MCP tools that make it genuinely agent-native.

5 PASS · 0 FAIL of 5 public-surface claims

Visit Django ORM Lens → scorecard.json

Quick answer

Django ORM Lens scores 84/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-23). STEADY (84) for a tool whose claims are specific and falsifiable, whose licensing and telemetry posture are stated plainly, and whose MCP surface is read-only by design — a deliberate safety choice, not an omission. Pricing: Open source · Subscription (free entry point documented).

Hlido Editor · 2026-08-23

Django ORM Lens parses a Django project statically — no database connection, no runserver, no working virtualenv — and turns the model graph into something an editor, a CI pipeline, or an AI agent can query. That constraint is the design decision that matters: because it never boots the project, it works on a cold clone with a broken environment, which is exactly the state a code agent usually finds a repository in. Three distributions share one parser core: a VS Code / Cursor / Windsurf extension with autocomplete and a live ER diagram, a pip package with 17 subcommands plus SARIF output, PR annotations and a GitHub Action, and an MCP variant exposing 13 read-only tools. The read-only scoping is the right default for a schema tool an agent drives. The commercial posture is the other thing worth noting. The page names, item by item, the capabilities normally sold behind a per-seat subscription — cross-function N+1 analysis, schema drift detection, index proposals from observed usage, migration blast radius weighted by real table statistics — and states that all of it is MIT with no tier gate, no account, and no telemetry, and that no Pro tier is planned. Vendors rarely enumerate the paid features they are giving away, and the specificity makes the claim checkable rather than decorative. Against that: this is a young project with a small maintainer footprint, the traction section shows star growth rather than production deployments, and the honest reading is that longevity is unproven. Nothing here is overstated, which in this category is itself the differentiator.

Why STEADY

STEADY (84) for a tool whose claims are specific and falsifiable, whose licensing and telemetry posture are stated plainly, and whose MCP surface is read-only by design — a deliberate safety choice, not an omission. Third-party pickup (Django News #347, PyCoder's Weekly #746) is real corroboration. Not VITAL because the project is young, the maintainer footprint is small, and the evidence of production use is star growth rather than deployment; a tool this dependent on a single parser core needs a longer track record before it earns the top band.

Public-surface checklist

What we saw

3 screenshots captured by the Hlido engine during the reviewed run (run-00ab18fa28c04e17-frowningdev-github-io). Our own captures — not vendor marketing material.

Django ORM Lens — run screenshot 1 (home.png)
home.png
Django ORM Lens — run screenshot 2 (page_the-schema-intelligence-layer-for-django.png)
page_the-schema-intelligence-layer-for-django.png
Django ORM Lens — run screenshot 3 (page_-10-seconds-to-first-insight.png)
page_-10-seconds-to-first-insight.png

What it does well

What it fails at

Best for

  • Django teams inheriting an unfamiliar or long-lived codebase
  • CI pipelines that need schema-drift and migration-risk gates without a paid seat
  • AI coding agents that need ground-truth schema answers instead of grep archaeology
  • Reviewers who want migration blast radius surfaced on the pull request itself

Not recommended for

  • Non-Django stacks — there is no generalisation path
  • Teams needing a vendor-backed support contract for a CI dependency
  • Anyone requiring runtime query profiling; this is static analysis only

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-22.

Compared to

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 69/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

First-class MCP server (`pip install "django-orm-lens[mcp]"`) exposing 13 read-only tools, documented for Cursor, Claude Code, Aider, Zed and Continue with a single JSON config block. A CLI with 17 subcommands and SARIF output gives a second programmatic path for CI agents. Read-only scoping means an agent cannot mutate the project through it — the correct default.

Agent-friendly score: 9/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-23

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/frowningdev-django-orm-lens.svg)](https://hlido.eu/check/?agent=frowningdev-django-orm-lens)

HTML

<a href="https://hlido.eu/check/?agent=frowningdev-django-orm-lens"><img src="https://hlido.eu/badge/frowningdev-django-orm-lens.svg" alt="Hlido trust score"></a>