redundant is a linter for project wide technical debt.
Currently, the main goal is to identify duplicate and near-duplicate code. While redundant was built with Django projects in mind, and to that end can analyze python, javascript, html, and css files, it should be useful for many types of codebases.
Usage
Simple run redundant in the top-level directory of your project and let it run. For larger projects it can take a while.
./path/to/redundant.py
You can improve how it runs by adding a .redundantrc to your project. See the dotredundantrc file for an example. Excluding vendor files, especially minimized code, can improve run time significantly.
You can configure the threshold for duplicate detection by changing the diff-delta-max setting in the [report] section of the config.
Metadata
Release files for redundant 0.1.6
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 |
|---|---|---|---|---|
| redundant-0.1.6.tar.gz | 3.6 kB | Without provenance | Details for redundant-0.1.6.tar.gz |
Release files / redundant-0.1.6.tar.gz
| Download URL | redundant-0.1.6.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40b570622c252f8d51c323a53dcf9a704784828debcfef080c29bceca8ed5ed8
|
|
BLAKE2b-256 checksum How to use checksums |
29da20a82b84f0d2b3a941fea2e87886eedac5db501dd6014265721efad923a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for redundant 0.1.6
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.