An adversarial review found 11 real defects in my Python library. Best decision I made.

Ahmed Abdeltawab — Tue, 11 Aug 2026 12:23:15 +0000

I built and published a Python library — then put it in front of an adversarial review whose only job was to break it. This is what it found, and what the library looks like now.

What pydextra is

pip install pydextra, then import dextra as dx. It's a small data-analysis library with one obsession: disclosure. Its 63 public functions — plus 5 scikit-learn-compatible wrappers, 68 public callables in all — share one flag vocabulary and:

print a one-line Decision: explaining what they did and why,
keep an audit trail on the DataFrame,
and, wherever statistics are learned from data, return a replayable params plan — fit on train, replay verbatim on test — so train/test leakage becomes hard to commit by accident.

One real call, verbatim from the leakage-safe pipeline notebook:

train_fe, params = dx.featpipe(train, steps=steps, return_params=True)

Decision: Fitted a 3-step featpipe pipeline (handle_missing -> encode -> scale);
33 new column(s) produced; combined params is a versioned, JSON-serialisable
artifact. Apply to held-out data with featpipe(df_test, params=...).

The part I'm most proud of isn't a feature

An adversarial external evaluation found 11 evidence-backed defects in the library. Version 0.6.0 closed all 11 — each one reproduced first by a failing "red" test, then fixed until green, with ~35 permanent regression tests and zero-warning exit gates. The original independent audit had scored an earlier version 82/100; the updated referee evaluation of 0.6.0 passed every agreed gate — 10/10 on a measurable definition fixed before the work started — with the remaining limitations listed openly in the repo.

Since 0.6.0 the API is frozen by policy: no new features, hotfixes only. What you evaluate today is what you run next year.

Three notebooks, real mess

All three are published fully executed on Kaggle:

Rescuing 9,291 invoice numbers from silent coercion — how numeric coercion silently eats identifiers, and how a disclosure-first loader catches it.
Two pipelines, same AUC (0.8465) — one is lying — the wrong protocol and the right one produce identical single-run AUC (0.8465); only 10 repetitions expose the real optimistic bias (+0.0261 ± 0.0210, wrong side higher in 9 of 10 runs). The full write-up: Same AUC, hidden leak, or run it in 5 minutes on Colab.
Egypt food prices 2010–2026: a fully-Arabic EDA — garlic +214.8% in one jump. Deliberately written in Arabic: technical Arabic data-science content is rare, and this is a small contribution against that gap.

Honest scope

It's a personal educational-practical project — not a pandas replacement, and not aimed at production-scale pipelines. pandas is the engine underneath; pydextra adds the disclosure layer.

GitHub: https://github.com/ahmedabdeltawab602-collab/dextra
PyPI: https://pypi.org/project/pydextra/
Docs: https://ahmedabdeltawab602-collab.github.io/dextra/

If the idea of functions that explain themselves appeals to you, a GitHub star helps others find it.

DEV Community: Ahmed Abdeltawab

An adversarial review found 11 real defects in my Python library. Best decision I made.

What pydextra is

The part I'm most proud of isn't a feature

Three notebooks, real mess

Honest scope