deviant-scan
Find the one thing in your code that breaks the pattern.
Deviant learns your project's own conventions, flags the exceptions, and shows the git history you need to judge them. You write no rules, and finding the exceptions needs no AI, no API key and no network.
Picture a project with 48 API routes. 47 of them check who is calling. The 48th doesn't, and it exports every user's data. Nobody noticed. Deviant counts what your code already does, picks out the rare item that breaks the pattern, and shows the git history behind it.
Use it
pip install deviant-scan
deviant-scan path/to/your/project --with-git
Or without installing it: uvx deviant-scan path/to/your/project --with-git.
It checks FastAPI routes and GitHub Actions workflows today. Add --json for machine-readable
output. Everything runs on your machine. It reads your files and never runs your code.
In Claude Code
A plugin judges each exception as a bug, intentional or unsure, with proof:
/plugin install deviant --marketplace ImalkaPerera/deviant
Learn more
Licensed under either the MIT license or the Apache License 2.0, at your option.
Metadata
Release files for deviant-scan 0.2.0
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 | |
|---|---|---|---|---|
| deviant_scan-0.2.0.tar.gz | 70.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deviant_scan-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 111.3 kB
Release files / deviant_scan-0.2.0.tar.gz
| Download URL | deviant_scan-0.2.0.tar.gz |
|---|---|
| Size | 70.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fa594b58e3fa7a0da494f7c0a8779a59f011af29b2fd0034fd6c3745574de25
|
|
BLAKE2b-256 checksum How to use checksums |
2e2f097b4e926d6c445b721b1ebd1583742705f0e2dfe27fe39984afaa1e5d7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 20, 2026.
Transparency logRelease files / deviant_scan-0.2.0-py3-none-any.whl
| Download URL | deviant_scan-0.2.0-py3-none-any.whl |
|---|---|
| Size | 41.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8669d61a9e82379cfa4e8a8fc958f2f2f20cdce624d292d067a7e234fb69e33f
|
|
BLAKE2b-256 checksum How to use checksums |
d5f5976dac4f5060c9f6a5110b5e48dc3f8b9a24290f73e9e3804479d0807ed8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 20, 2026.
Transparency logSecurity for deviant-scan 0.2.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for deviant_scan-0.2.0.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 20, 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.