hunt-regressions
Use when discovering possible regressions from a pinned change and its callers before reproduction.
v2026.11.12-149d7b23 installs+3 in 7 days8.2K StarsCC-BY-SA-4.0synced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install trailofbits/hunt-regressionsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package97e1c235…9e24b115
97e1c2353ddd…e2d29e24b1151 file · 1.1 KBScanLowno findings
Sourcegithub.com/trailofbits/skills/tree/main/plugins/regression-hunt/skills/hunt-regressions@149d7b2
On this page
When to Use
Input: sealed preparation, frozen S0/S1, change context and registry assignment. On retry, include this assignment's prior candidate-ID mapping. The caller supplies these, including for independent use. Follow project guidance before target work.
When NOT to Use
Proving a known candidate; use reproduction. Discovery cannot confirm findings.
Hunt
- Read the standard and file contract. Verify preparation; read frozen change messages, PR discussion and security documentation for intent and supported use.
- Review the entire diff; trace changed behavior through callers to real interfaces. Use frozen sources and supplied context, not later fixes, advisories or other reviews.
- Record each lead's changed code, previously supported behavior, reachable trigger, proposed new defect, false-positive checks and required proof. Retain supplied leads suggesting old bugs or incomplete fixes for adjudication. Leave PoC construction to reproduction.
- Reserve each lead's ID through registry.py
candidateusing its stable hypothesis key and assigned agent handle. Reuse the key on retry. Write candidate files andhunt.jsonwith IDs, file mappings, coverage and limitations. An empty list is valid. If blocked, record partial coverage and uninspected areas. Seal the package.
Report Back
Keep detailed evidence in the sealed package. Return only:
- Status:
completeorblocked, matching the record. - Record: sealed
hunt.jsonpath, or why none was produced. - Result: candidate count and material coverage gaps.
- Blocker: missing prerequisite or required caller action, if blocked.
Rationalizations to Reject
- “A helper fails on invented input”: show a supported interface that reaches it.
Files in this version
- SKILL.md2.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
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.12-149d7b2 | Nov 13, 2026 | 149d7b2 | 97e1c235 | Signed | – |
More from trailofbits
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk 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