rpkilby/jsonfield
A reusable Django model field for storing ad-hoc JSON data observed · 2026-08-28
Health v2 · maintenance only
36/100
- Activity 30
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 6331
- days_rel: n/a
- days_push: 425
- n_releases_24m: 0
Adoption not part of the score
1160 stars · 265 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A reusable Django model field for storing validated, ad-hoc JSON data with automatic serialization to and from the database. It is now deprecated in favor of Django's native models.JSONField introduced in Django 3.1.
Use cases
- store json data in a django model
- add a json field to django models on old django versions
- serialize json to database column in django
- store ad-hoc json payloads in django orm
- migrate legacy jsonfield to django native jsonfield
When to choose
- you maintain a legacy Django project (pre-3.1) that cannot use the native JSONField
- you need a simple JSON column with basic text-style lookups and no advanced querying
When to avoid
- you are on Django 3.1 or newer - use the built-in models.JSONField instead
- you need JSON-specific querying like key-path lookups or containment operators
- you are starting a new project
Facets
library · maturity maintenance
serialization database databases web-development backend python cross-platform django json-field orm deprecated model-field
2 sources
- readme: https://github.com/rpkilby/jsonfield · fetched 2026-08-28 · 44da2e3ef0df
- registry_pypi: https://pypi.org/pypi/jsonfield/json · fetched 2026-08-29 · 981f3f810d85
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| rpkilby/jsonfield | main | 36 |
For agents
markdown · JSON · MCP: product_card(name="rpkilby/jsonfield")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem