nezaret
نظارت: oversight, supervision, inspection. The same word in Persian (nezārat), Turkish (nezaret) and Azerbaijani (nəzarət).
Find faults in MONAI pipelines that do not raise errors: a label map resampled with bilinear interpolation, a rotation applied to the image but not its label, a validation crop chosen from the ground truth, an inference pipeline that preprocesses differently from training.
Each of these trains, evaluates and reports a number. The number is wrong, and nothing in the run says so.
No dependencies. Runs offline. Reads configs as data; never imports torch, never runs a transform.
pip install nezaret
nezaret lint path/to/bundle
Python 3.10+. Apache 2.0. Rules are checked against MONAI 1.6.1.
PyPI · INSTALL · TESTING · PUBLISHING · TROUBLESHOOTING · ROADMAP · CHANGELOG
The thirty-second version
$ nezaret lint examples/faulty_bundle
configs/inference.json
E NZ104 unknown-target preprocessing#transforms#1
'AddChanneld' is not a MONAI 1.6.1 component. It was removed or renamed in MONAI; use EnsureChannelFirstd with channel_dim="no_channel".
W NZ106 saved-not-inverted postprocessing#transforms#2
SaveImaged writes 'pred' without Invertd, but the preprocessing at inference.json:preprocessing changes the grid (Orientationd, Spacingd).
W NZ109 train-eval-mismatch preprocessing
compared with train.json:train#preprocessing: NormalizeIntensityd only in training; Orientationd.axcodes: train 'RAS' vs eval 'LPS'
configs/train.json
E NZ101 label-interpolation train#deterministic_transforms#3
Spacingd resamples label key 'label' with mode 'bilinear' (MONAI's default); label maps need 'nearest'.
E NZ102 label-intensity train#random_transforms#2
RandGaussianNoised changes voxel values of label key(s) 'label'.
E NZ103 geometry-split train#random_transforms#1
RandRotated transforms 'image' but not 'label', which were loaded together and stop being aligned here.
E NZ107 label-guided-eval validate#preprocessing#transforms#4
CropForegroundd in an evaluation pipeline takes its region from ground-truth key 'label' (source_key).
W NZ109 train-eval-mismatch validate#preprocessing
compared with train.json:train#preprocessing: NormalizeIntensityd only in training
I NZ111 no-determinism train#preprocessing
random transforms in training and no set_determinism or seed in this file or the config it overrides.
2 file(s), 4 pipeline(s): 5 error(s), 3 warning(s), 1 info
Every location is a MONAI Bundle #-path, so train#deterministic_transforms#3
is the fourth entry of that list. A finding on a transform reached through
$@train#deterministic_transforms + @train#random_transforms points at the list
the transform is written in, not at the expression.
What it checks
| Rule | Severity | Catches |
|---|---|---|
NZ101 label-interpolation |
error | a label key resampled with a non-nearest mode, including MONAI's defaults (Spacingd, RandAffined: bilinear; Resized, Zoomd, RandZoomd: area) |
NZ102 label-intensity |
error | intensity transforms (noise, scaling, normalisation, contrast) on a label key; min-max scaling is a warning, since 0/255 → 0/1 masks are a real idiom |
NZ103 geometry-split |
error | a spatial transform (orientation, spacing, crop, pad, flip, rotate, zoom) applied to some of the arrays loaded together but not the others |
NZ104 unknown-target |
error | a _target_ MONAI cannot resolve, with the replacement for removed ones (AddChanneld, AsChannelFirstd, IgniteMetric…) |
NZ105 discrete-interpolation |
error | Invertd(nearest_interp=false) after AsDiscreted, which interpolates class indices |
NZ106 saved-not-inverted |
warning | predictions saved on the resampled grid, without Invertd or resample=true |
NZ107 label-guided-eval |
error | validation or inference that crops by the ground truth (CropForegroundd(source_key=label), label-guided random crops) |
NZ108 random-in-eval |
warning | a random transform in validation or inference |
NZ109 train-eval-mismatch |
warning | orientation, spacing, size or intensity scaling that differs between training and evaluation, across files of the same bundle |
NZ110 missing-channel-first |
info | a spatial transform before any channel-first step |
NZ111 no-determinism |
info | random training transforms and no seed anywhere |
nezaret rules lists them; nezaret explain NZ107 says why one matters and
how to fix it.
The defaults nezaret relies on were read from inspect.signature of MONAI
1.6.1, not from documentation, and tests/test_live_monai.py re-checks them
against whatever MONAI is installed.
What it found in MONAI's own model zoo
Linting all 37 bundles of Project-MONAI/model-zoo
(commit feb2e8c, 20 October 2026; 157 config files, 174 pipelines) gives
6 errors, 7 warnings and 5 info. Every error, and every warning below, was read
against the bundle source by hand:
| Bundle | Rule | What the config does |
|---|---|---|
prostate_mri_anatomy train |
NZ101 ×3 | RandAffined, Rand3DElasticd and RandZoomd on ["image", "label"] with no mode, so the label is resampled bilinearly (twice) and by area averaging |
prostate_mri_anatomy inference |
NZ105 | AsDiscreted(argmax), then Invertd(nearest_interp=false) on the class map |
renalStructures_CECT_segmentation train |
NZ101 | RandZoomd on the label with the default area mode |
renalStructures_CECT_segmentation inference |
NZ109 | training loads with as_closest_canonical=true (RAS); inference reorients to LPS |
wholeBrainSeg_Large_UNEST_segmentation train |
NZ109 | NormalizeIntensityd sits in random_transforms; validation copies only the deterministic list, so the checkpoint is selected on unnormalised inputs while training and inference normalise |
mednist_reg train |
NZ104 | IgniteMetric, renamed IgniteMetricHandler |
The reference bundles (spleen_ct_segmentation, swin_unetr_btcv_segmentation)
come back clean. tests/test_model_zoo.py turns this table into a regression
test.
The remaining warnings are judgement calls nezaret cannot settle from the
config alone: e.g. lung_nodule_ct_detection resamples only at inference
because its README resamples the training data offline, which the message
says.
Commands
nezaret lint PATH... # a config file, a bundle, or a folder of bundles
nezaret lint PATH --format markdown # or json; -o report.md to write a file
nezaret lint PATH --fail-on warning # exit 1 on warnings too (default: errors only)
nezaret lint PATH --ignore NZ108,no-determinism
nezaret lint PATH --label-keys seg,organs
nezaret rules
nezaret explain NZ103
nezaret doctor
Exit codes: 0 clean, 1 a finding at or above --fail-on, 2 nothing
could be checked. That makes it a CI step as it stands:
- run: pip install "nezaret[yaml]"
- run: nezaret lint configs/ --fail-on error
A directory with a configs/ folder is one bundle; a directory holding
configs is one bundle; anything else is searched for configs/ folders.
Cross-file rules only compare files within one bundle.
From Python
import nezaret
report = nezaret.lint("my_bundle/") # Report
report.ok # no errors
report.findings # [Finding(rule, severity, file, location, message, ...)]
report.to_json(); report.to_markdown()
nezaret.lint_config(config_dict, name="train.json")
For pipelines built in Python rather than in a config (needs MONAI installed):
report = nezaret.lint_compose(train_transforms, role="train")
report = nezaret.lint_compose(val_transforms, role="eval")
report = nezaret.lint_compose(post_transforms, role="post", preprocessing=val_transforms)
nezaret reads the transform objects' attributes; it does not call them, load
data or need a GPU. role has to be given because an object does not say what
it is used for. See examples/lint_compose_example.py.
How it decides what is a label
In this order:
--label-keys/label_keys=, if given, and nothing else.- Key names such as
label,seg,mask,gt,annotation,target(alsolabel_inst,seg_1,lbl…). - A per-key
modelist that mixesnearestwith something else: the author saying which keys are label maps. - The
label_keyof a label-guided crop.
A single mode: "nearest" for every key is not evidence: some bundles
resample their images that way.
What it does not do
- It does not evaluate
$expressions.@references,%macros (including%other.json#…) and$@a + @bconcatenation are resolved statically; any other expression is treated as unknown and the rules that would need it are skipped, never guessed. A pipeline built entirely by an expression is not checked. - It does not read your data list or your images. It cannot know that
your data list supplies four files per key (which is why
NZ110is info) or that two cases come from the same patient. That isnezaret data, planned for 0.2.0 (see the ROADMAP). - It does not judge custom transforms. After a
scripts.*step that may add, merge or drop keys, the key-tracking rules stop rather than guess.
Licence
Apache 2.0. See LICENSE.
Metadata
Release files for nezaret 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 | Provenance | Actions |
|---|---|---|---|---|
| nezaret-0.1.0.tar.gz | 67.1 kB | Without provenance | Details for nezaret-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nezaret-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for nezaret-0.1.0-py3-none-any.whl |
Total release size: 113.6 kB
Release files / nezaret-0.1.0.tar.gz
| Download URL | nezaret-0.1.0.tar.gz |
|---|---|
| Size | 67.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
949202a5e1d030fae2b11a366472fda2d5c8d7091ef7ba2e31b7328f0c83cc9c
|
|
BLAKE2b-256 checksum How to use checksums |
babb985c6ecbc2adf48c8daab9b3f0c0d660a08b2ef29ab2907b0cc4bdce510f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.5
|
Release files / nezaret-0.1.0-py3-none-any.whl
| Download URL | nezaret-0.1.0-py3-none-any.whl |
|---|---|
| Size | 46.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5d0d181828020bcb3a59fcd2e11e2fefe5736dbc590edcdecc7cf4056cf6416
|
|
BLAKE2b-256 checksum How to use checksums |
d2f228eaadb6d9cf798ee364c52a109e20ecd5d1beb82fc6217f8f63cb3de927
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.5
|
Security for nezaret 0.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.
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.