schemathesis
Auth/lab ref: OpenAPI/GraphQL property-based API fuzzer. Use to auto-generate API tests, catch schema violations, triage failures systematically, and run high-coverage stateful campaigns in REST/GraphQL services.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/schemathesisWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package8663e991…0544184d
8663e991fe4c…6da10544184d1 file · 1.3 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/schemathesis@21cd568
On this page
Schema-driven API fuzzing for developer and AppSec workflows.
Quick Start
# CLI
uvx schemathesis run https://example.schemathesis.io/openapi.json
# Installed CLI
schemathesis run https://your-api/openapi.jsonimport schemathesis
schema = schemathesis.openapi.from_url("https://your-api/openapi.json")
@schema.parametrize()
def test_api(case):
case.call_and_validate()Operator Flow
- First run with defaults to map baseline failure landscape.
- Triage in this order: undocumented status codes -> schema conformance -> server errors.
- Narrow scope by tag/path to fix incrementally.
- Run longer optimization profile for release/security gates.
- Keep CI smoke + nightly deep profiles separated.
Strengths
- Generates large input space from API schema automatically.
- Detects 500s, contract/schema drift, validation bypasses.
- Supports stateful API workflows (operation sequences).
Optimization Profile (Deep Runs)
schemathesis run <schema_url> \
--max-examples 1000 \
--continue-on-failureOften paired with targeted generation and health-check suppression on complex schemas.
Practical Tricks
- Use include-path/include-tag scope to eliminate triage noise.
- Keep one strict schema-conformance pass and one exploratory bug-hunting pass.
- Export machine-readable artifacts (JUnit/Allure) for team triage.
- Re-run minimal reproducer from failing example before opening defect ticket.
Common Pitfalls
- Trying to fix every first-run failure globally at once.
- Ignoring repetitive undocumented status patterns that should be schema-level fixes.
- Treating long-run health-check warnings as always ignorable.
CI Pattern
- Run fast smoke profile on PRs.
- Run longer stateful/negative campaigns nightly.
- Publish JUnit/Allure artifacts for triage.
Resources
Files in this version
- SKILL.md2.4 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 8663e991 | Signed | – |
More from AeonDave
All from this publisherMore in APIs, SaaS and identity
See the category- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login