Minosse
Detects AI-generated or AI-edited images using three complementary, hand-crafted artifact signals — no ML model, just signal processing.
Minosse looks for tell-tale traces that diffusion models and neural upsamplers leave behind: ringing halos around text, noise in flat regions that shouldn't have any, and a synthetic signature in the high-frequency spectrum.
Signals
| Signal | What it catches | How it works |
|---|---|---|
| ringing | Diffusion VAE decoder halos | Radial profile of band-pass energy vs. distance from strong edges. Real edges decay fast; ringing persists 10–40 px out. |
| noisy-flats | AI "film grain" on solid panels | RMS residual noise inside coarse-flat regions. Real screenshots are truly flat; JPEG smooths photo flats. |
| synthetic-noise | Upsampled / generated noise | Spectral energy at the Nyquist ring vs. mid frequencies. Real sensor noise stays hot at the highest frequencies; synthetic noise dies off. |
An image is flagged if any signal fires; the fired signals are reported along with the raw feature values.
Quick start
python -m venv .venv
.venv/bin/pip install -r requirements.txt
# Analyse a single image
.venv/bin/python -m minosse path/to/image.png
# Analyse multiple images with visual proof sheets
.venv/bin/python -m minosse --proof results/ image1.png image2.jpg
--proof output
The --proof flag writes <name>_proof.png: a side-by-side sheet with
the original image next to one panel per fired signal, with the artifact
evidence burned in as a red heatmap.
Heat is scaled absolutely (calibrated to the detection thresholds), so clean images render dark — the glow itself is the proof. For ringing, the map only shows oscillation in regions that should be smooth (8–40 px from strong edges, locally flat at coarse scale), so legitimate texture doesn't light up.
Python API
from minosse import analyze, analyze_path, Result
# From a file path
r = analyze_path("image.png")
print(r.verdict) # "likely AI-generated/edited" or "likely clean"
print(r.reasons) # e.g. ["ringing", "synthetic-noise"]
print(r.decay) # ringing feature value
print(r.vhf_mf) # spectral ratio feature value
print(r.flat_noise) # flat-region noise feature value
print(r.resid_std) # overall residual noise
# From a PIL Image
from PIL import Image
img = Image.open("image.png")
r = analyze(img)
Result fields
| Field | Type | Description |
|---|---|---|
verdict |
str |
"likely AI-generated/edited" or "likely clean" |
reasons |
list[str] |
Fired signal names: ringing, noisy-flats, synthetic-noise |
score |
float |
Confidence score [0, 1] (0.75 per firing signal, capped at 1.0) |
decay |
float |
Ringing persistence: mid-distance / near-edge band energy |
halo_vs_bg |
float |
Mid-distance energy vs. image background |
vhf_mf |
float |
Spectral ratio: Nyquist ring / mid frequencies |
resid_std |
float |
Standard deviation of the noise residual |
flat_noise |
float |
RMS residual inside coarse-flat regions |
Visual proof from Python
from minosse import analyze, evidence
from PIL import Image
img = Image.open("image.png")
r = analyze(img)
sheet = evidence.render(img, r)
sheet.save("proof.png")
Project structure
minosse/
├── minosse/
│ ├── __init__.py # Public API: analyze, analyze_path, Result
│ ├── __main__.py # python -m minosse entry point
│ ├── cli.py # Argument parsing and CLI loop
│ ├── detector.py # Feature extraction + threshold logic
│ └── evidence.py # Visual proof sheet renderer
├── results/ # Default --proof output directory
├── requirements.txt # numpy, pillow, scipy
└── README.md
How it works (briefly)
- Preprocessing — the image is converted to RGB and downscaled if its longest edge exceeds 1600 px.
- Feature extraction (
detector._features()) — three independent signal-processing pipelines compute scalar features from the grayscale luminance. - Thresholding — each feature is compared against a tuned threshold; if it exceeds the threshold the corresponding signal is flagged.
- Verdict — if any signal fires, the image is marked likely AI-generated/edited; otherwise it's likely clean.
For a deeper explanation of each signal, see docs/signals.md.
Caveats
The thresholds are calibrated on a small set of examples and should be re-validated as more AI samples are added. See docs/tuning.md for instructions on re-tuning.
License
MIT
Metadata
Release files for minosse 0.1.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 | |
|---|---|---|---|
| minosse-0.1.0.tar.gz | 11.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| minosse-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.3 kB
Release files / minosse-0.1.0.tar.gz
| Download URL | minosse-0.1.0.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e734b5d47fc398b7c2372fc03960877db639a6af0a048fdea63657584592b6a1
|
|
BLAKE2b-256 checksum How to use checksums |
7fa4c2c1a30f1ca5fad117efcd4ce6217fb2f66d7c7003e2f51414e36af9d2b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 16, 2026.
Transparency logRelease files / minosse-0.1.0-py3-none-any.whl
| Download URL | minosse-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4530ed8dbb3b2771181b4447d23a511d6ed7d76577a7661b1327d63fdc9f371
|
|
BLAKE2b-256 checksum How to use checksums |
5fe0f2e4f2af6512d44a755beb683fbd2e845b4398d095cf40696264425cbb1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 16, 2026.
Transparency log