Django Content License
Store license information alongside your Django data models.
A Django app that allows you to associate content licenses with model instances and display appropriate attribution in your HTML templates. Perfect for academic datasets, research publications, creative content, and any application where proper licensing and attribution are important.
Features
- License Management: Store and manage various content licenses (MIT, GPL, Creative Commons, etc.)
- Easy Integration: Simple
LicenseFieldthat can be added to any Django model - Automatic Attribution: Render proper HTML attribution snippets via the field's auto-injected
get_<field>_display()method - Template Override: Customize the attribution markup by shadowing the
licensing/snippet.htmltemplate - Validation: Built-in validation for license consistency and requirements
- Internationalization: Full i18n support with translations
- Performance: Optimized database queries and indexing
Scope & philosophy
django-content-license is deliberately small: it stores licenses, attaches them to your models, and renders attribution where a license needs it. Think of the license picker GitHub puts on a new repository, plus the attribution some licenses (like Creative Commons) ask you to show.
It stays generic on purpose. It is not a citation or metadata exporter (BibTeX, DataCite, CSL), not a license-compatibility checker, and not tied to any one project's needs or to the Creative Commons attribution style.
When choices collide: generic beats specific, simplicity beats flexibility, and attribution stays configurable: a license defines what it needs, and one that only needs its title shown simply doesn't use the feature.
Where it's headed is tracked in GOALS.md.
Requirements
- Python 3.11 or later
- Django 5.2 LTS, 6.0 or 6.1
Quick Start
Installation
pip install django-content-license
Settings
Add licensing to your INSTALLED_APPS:
INSTALLED_APPS = [
# ... your other apps
'licensing',
]
Run migrations:
python manage.py migrate licensing
Basic Usage
1. Add License Field to Your Model
from django.db import models
from licensing.fields import LicenseField
class Dataset(models.Model):
name = models.CharField(max_length=200)
description = models.TextField()
license = LicenseField() # This field links to a License
def __str__(self):
return self.name
def get_absolute_url(self):
return f"/datasets/{self.pk}/"
2. Create Licenses
from licensing.models import License
# Create licenses through Django admin or programmatically
mit_license = License.objects.create(
name="MIT License",
canonical_url="https://opensource.org/licenses/MIT",
description="A permissive license that allows commercial use",
text="Permission is hereby granted, free of charge..."
)
3. Display Attribution in Templates
<!-- In your template -->
<div class="dataset">
<h2>{{ dataset.name }}</h2>
<p>{{ dataset.description }}</p>
<!-- Automatic attribution display -->
<div class="license-attribution">
{{ dataset.get_license_display }}
</div>
</div>
This will output properly formatted HTML like:
<a href="/datasets/1/">My Dataset</a> is licensed under
<a href="https://opensource.org/licenses/MIT" target="_blank" rel="noopener">MIT License</a>
Advanced Usage
Custom License Field Options
class Article(models.Model):
title = models.CharField(max_length=200)
content = models.TextField()
# Custom license field with specific options
license = LicenseField(
verbose_name="Content License",
help_text="Choose the license for this article",
on_delete=models.PROTECT, # Prevent license deletion if referenced
limit_choices_to={'is_active': True}, # Only show active licenses
)
Working with Creators/Authors
If your model has creator information, the attribution will automatically include it:
class Research(models.Model):
title = models.CharField(max_length=200)
license = LicenseField()
# The template will automatically look for these fields
creators = models.CharField(max_length=200) # Or ForeignKey to User/Author model
def get_absolute_url(self):
return f"/research/{self.pk}/"
# In template, this will generate:
# "Research Title by John Doe is licensed under MIT License"
License Model API
from licensing.models import License
# Get all active/recommended licenses
active_licenses = License.get_recommended_licenses()
# Check license properties
license = License.objects.get(name="MIT License")
print(license.status_display) # "Active" or "Deprecated"
print(license.short_description) # Truncated description
print(license.full_name) # Full license name
# Validation
license.clean() # Validates license consistency
Template Customization
You can override the default attribution template by creating your own licensing/snippet.html:
<!-- templates/licensing/snippet.html -->
{% load i18n %}
<div class="license-info">
{% if object.creators %}
<span class="creators">By {{ object.creators }}</span>
{% endif %}
<span class="license-link">
Licensed under <a href="{{ license.canonical_url }}" target="_blank" rel="noopener">
{{ license.name }}
</a>
</span>
</div>
Available License Fields
LicenseField Parameters
verbose_name: Display name for the field (default: "license")help_text: Help text for admin formson_delete: What to do when license is deleted (default:models.PROTECT)limit_choices_to: Limit available license choicesnull/blank: Whether field can be empty
Model Validation
The License model includes built-in validation:
# Deprecated licenses must have a deprecated_date
license = License(name="Old License", is_active=False)
license.clean() # Raises ValidationError
# Active licenses shouldn't have deprecated_date
license = License(
name="Active License",
is_active=True,
deprecated_date=timezone.now().date()
)
license.clean() # Raises ValidationError
Testing
The suite uses pytest and pytest-django, with tests grouped into Test<Subject> classes.
Running Tests
# Run with pytest (settings module: tests.settings)
uv run pytest
# Run with coverage
uv run pytest --cov=licensing --cov-report=html
Test Organization
Each test module mirrors the source module it tests: tests/test_models.py covers
licensing/models.py, and so on. The full rules are in the
testing standards.
Writing Your Own Tests
import pytest
from licensing.models import License
from licensing.fields import LicenseField
@pytest.mark.django_db
def test_my_model_with_license():
license_obj = License.objects.create(
name="Test License",
canonical_url="https://example.com/license",
text="License text"
)
# Test your model here
instance = MyModel.objects.create(license=license_obj)
assert instance.license == license_obj
Admin Integration
The package does not register a ModelAdmin for you — register License in your own
project's admin.py so you control the site it appears on and how it's displayed. The model
exposes helpers (status_display, short_description) that are handy in list_display:
# admin.py
from django.contrib import admin
from licensing.models import License
@admin.register(License)
class LicenseAdmin(admin.ModelAdmin):
list_display = ['name', 'status_display', 'canonical_url']
list_filter = ['is_active', 'created_at']
search_fields = ['name', 'description']
readonly_fields = ['created_at', 'updated_at', 'slug']
Performance Considerations
Database Optimization
- Indexes are automatically created on
is_activeandslugfields - License lookups are optimized using
select_related - Slug generation uses efficient bulk queries
Caching
For high-traffic sites, consider caching license information:
from django.core.cache import cache
from django.db.models.signals import post_save
def invalidate_license_cache(sender, instance, **kwargs):
cache.delete(f'license_{instance.pk}')
post_save.connect(invalidate_license_cache, sender=License)
Migration from Other Apps
If you're migrating from another licensing solution:
# Create a data migration
from django.db import migrations
def migrate_licenses(apps, schema_editor):
OldLicense = apps.get_model('old_app', 'License')
NewLicense = apps.get_model('licensing', 'License')
for old_license in OldLicense.objects.all():
NewLicense.objects.create(
name=old_license.name,
canonical_url=old_license.url,
text=old_license.text,
# Map other fields as needed
)
class Migration(migrations.Migration):
dependencies = [
('licensing', '0001_initial'),
('old_app', '0001_initial'),
]
operations = [
migrations.RunPython(migrate_licenses),
]
Common Use Cases
Academic Research
class ResearchPaper(models.Model):
title = models.CharField(max_length=200)
authors = models.ManyToManyField(User)
license = LicenseField(
help_text="Choose appropriate license for your research data"
)
# For dataset licensing
dataset_license = LicenseField(
verbose_name="Dataset License",
related_name="research_datasets"
)
Creative Content
class Artwork(models.Model):
title = models.CharField(max_length=200)
artist = models.ForeignKey(User, on_delete=models.CASCADE)
license = LicenseField(
limit_choices_to={'name__icontains': 'Creative Commons'}
)
Software Projects
class SoftwareProject(models.Model):
name = models.CharField(max_length=200)
license = LicenseField(
limit_choices_to={'name__in': ['MIT', 'GPL', 'Apache']}
)
Contributing
We welcome contributions! Please see our Contributing Guide for details.
Development Setup
# Clone the repository
git clone https://github.com/SamuelJennings/django-content-license.git
cd django-content-license
# Install dependencies
uv sync
# Run tests
uv run pytest
# Run linting
uv run pre-commit run --all-files
Code Quality
- Coverage floors of 90% for the project and 85% for each change, set in
codecov.yml - Tests follow the testing standards
- Docstrings and comments follow the code documentation standards
- Where code lives follows the Django standards
- ruff, mypy and deptry run on every commit and in CI
License
This project is licensed under the MIT License - see the LICENSE file for details.
Support
- Documentation: this README (usage) and
docs/adr/(design decisions) - Issues: Report bugs at GitHub Issues
Changelog
See HISTORY.md for a complete changelog.
Related Projects
- Creative Commons – cc-licenses - Official CC license data
Made with ❤️ by the Django community
Metadata
Release files for django-content-license 0.3.1
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 |
|---|---|---|---|---|
| django_content_license-0.3.1.tar.gz | 25.7 kB | With provenance | Details for django_content_license-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_content_license-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for django_content_license-0.3.1-py3-none-any.whl |
Total release size: 52.5 kB
Release files / django_content_license-0.3.1.tar.gz
| Download URL | django_content_license-0.3.1.tar.gz |
|---|---|
| Size | 25.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8851aa03824ccb85210d5156269cd7d305404ea6898844aa5268dbfd4af9165b
|
|
BLAKE2b-256 checksum How to use checksums |
dc2c80fdbc4e200a500628a3bc42fa9c950b22c2b58061c241467220858aabf9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 26, 2026.
Transparency logRelease files / django_content_license-0.3.1-py3-none-any.whl
| Download URL | django_content_license-0.3.1-py3-none-any.whl |
|---|---|
| Size | 26.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7419379c105e5c3a8622fc7f7829d4bb86b3a841a6707741366f3cdda3cf372
|
|
BLAKE2b-256 checksum How to use checksums |
b806db13f13ad214480793dfdbb6c9d3eb2ceab97b9b53db8466445204f6cb01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 26, 2026.
Transparency logSecurity for django-content-license 0.3.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for django_content_license-0.3.1.tar.gz
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 Oct 26, 2026.
Transparency logA 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.