Skip to main content

ferrolint-django

ci rust PyPI crates.io License: MIT Topics

Pylint-django's rules as a ferrolint plugin, so a Django project keeps its pylint_django messages in a ferrolint run.

Contents

About

pylint-django adds Django checks to Pylint. ferrolint runs Pylint-compatible checks as WebAssembly plugins next to Ruff. This crate ports the pylint_django rules that the syntax decides, plus its migration checks, to a ferrolint plugin built for wasm32-wasip2. The rules keep Pylint's message IDs and symbols, so # pylint: disable= comments and selections in an existing configuration keep working.

Key features

  • Thirteen pylint_django rules with their original IDs and symbols; see Rules.
  • Migration checks as a sub-plugin that loads only when the configuration names it, as Pylint does.
  • One component, two plugin names. The package registers pylint_django and pylint_django.checkers.migrations as ferrolint.plugins entry points, so a load-plugins line written for Pylint works unchanged.

Requirements

  • A ferrolint that supports plugin contract 1.2.0, and Python 3.9 or later.
  • To build: the toolchain in mise.toml (Rust with the wasm32-wasip2 target, uv), installed by make install, and a ferrolint binary for the tests; see CONTRIBUTING.md.

Usage

Install the package into the virtual environment that ferrolint reads:

uv pip install ferrolint-django

To try an unreleased change, build the wheel from a checkout instead:

make wheel
uv pip install dist/*.whl

ferrolint finds a plugin only through VIRTUAL_ENV, and loads it only when load-plugins names it. In pyproject.toml:

[tool.pylint.main]
load-plugins = "pylint_django, pylint_django.checkers.migrations"

Then run ferrolint in the project. Leave pylint_django.checkers.migrations out to skip the two migration rules.

Rules

ID Symbol Flags
E5101 model-unicode-not-callable A model's __unicode__ assigned something that is not callable.
E5141 hard-coded-auth-user The string 'auth.User'.
E5142 imported-auth-user User imported from django.contrib.auth.models.
R5101 http-response-with-json-dumps HttpResponse(json.dumps(data)).
R5102 http-response-with-content-type-json HttpResponse(content_type='application/json').
R5103 redundant-content-type-for-json-response JsonResponse(content_type=...).
W5102 model-has-unicode A model that defines __unicode__.
W5103 model-no-explicit-unicode A model that only inherits __unicode__.
W5104 modelform-uses-exclude A ModelForm whose Meta sets exclude.
W5150 format-html-interpolation format_html() with an interpolated format string.
W5151 mark-safe-interpolation mark_safe() of an interpolated string.
W5197 missing-backwards-migration-callable A RunPython migration without a backwards callable.
W5198 new-db-field-with-default An AddField migration with a default, in an app's latest one.

Security

Report a vulnerability by emailing dev@gajaguar.com rather than opening a public issue. SECURITY.md has the supported versions.

Contributing

See CONTRIBUTING.md.

Open items

  • Only the pylint_django messages the syntax decides are ported, plus the two migration checks.

License

See LICENSE.

Metadata

Release files for ferrolint-django 1.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for ferrolint-django 1.1.0
File Interpreter ABI Platform Actions
ferrolint_django-1.1.0-py3-none-any.whl Python 3 none any Details for ferrolint_django-1.1.0-py3-none-any.whl

Release files / ferrolint_django-1.1.0-py3-none-any.whl

Download URL ferrolint_django-1.1.0-py3-none-any.whl
Size 80.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a7ab57806be5ee9f76bce7e4987f12bb5257040bf897f91945195be10d3bff32
BLAKE2b-256 checksum
How to use checksums
b72e094ed51fcebe9c610faa4b28fb03897f5fde4038e0e5a0f117081542bf3f
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 Nov 5, 2026.

Transparency log

Security for ferrolint-django 1.1.0

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

1 file in this release has been uploaded with provenance metadata.

Attestation for ferrolint_django-1.1.0-py3-none-any.whl

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 Nov 5, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page