Skip to main content

BlastContain Scout

A separate, scheduled agent that scans arXiv for new jailbreak / prompt-injection / LLM-agent-attack research and opens a draft pull request proposing additions to the Drill corpus. It embodies BlastContain's derive-then-ratify tenet: the scout derives candidate attacks; a human ratifies by reviewing the PR. It never auto-touches a security corpus.

How it works

arXiv API ─▶ dedupe (seen-ledger) ─▶ classify ─▶ render ─▶ draft PR
            (only new papers)        dataset/    digest +   (you review
                                     technique/  inert       & merge)
                                     intel        scaffolds
  1. Scan — query the arXiv API (no key) for recent cs.CR/cs.CL/cs.AI/cs.LG papers matching jailbreak / prompt-injection / agent-attack terms, newest first.
  2. Dedupe — skip anything already in tools/scout/state/seen-arxiv.json (committed, so the state travels with the repo).
  3. Classify — a local LM Studio model (or a keyword fallback) labels each paper dataset / technique / intel, suggests a Drill category, and flags the license.
  4. Render — a markdown digest plus, for each dataset/technique paper, an inert AttackSource scaffold under drill/.../corpus/contrib/ whose is_available() returns False (so load_corpus skips it until ratified — the PR is safe to merge).
  5. Draft PR — branch, commit, gh pr create. You review, verify the license, vendor the data, implement dataset(), flip availability, and register it with an enable_* flag.

Install

# from blastcontain-oss/
pip install -e tools/scout
# or run without installing:
python -m blastcontain_scout --help     # (run from the tools/scout/ directory)

Requires git and an authenticated gh CLI for --open-pr. For LLM classification, LM Studio must be serving a model on :1234.

Usage

# Dry-run preview — no writes, no git (the default; start here):
blastcontain-scout --max 50

# Use a local model for richer classification:
blastcontain-scout --model "qwen/qwen3-30b-a3b-2507"

# Write the digest + scaffolds and commit on a new branch:
blastcontain-scout --model "qwen/qwen3-30b-a3b-2507" --apply

# ...and push + open the draft PR:
blastcontain-scout --model "qwen/qwen3-30b-a3b-2507" --open-pr
Flag Meaning
--max N arXiv results to scan (newest first)
--model ID LM Studio model id for classification (omit → keyword heuristic)
--base-url URL OpenAI-compatible endpoint (default http://localhost:1234/v1)
--threshold 0..1 relevance cutoff (default 0.5)
--apply write files + commit on a new branch
--open-pr also push + open the PR via gh (implies --apply)

Ratifying a proposal (the human half)

A merged scaffold is inert. To turn it into a live source:

  1. Verify the license permits vendoring (Apache / MIT / BSD — reject Llama-Community, gated datasets, JAILJUDGE-style).
  2. Vendor the data (pin the commit) or implement dataset() to load it.
  3. Flip is_available() to a real check and set revision to the dataset version.
  4. Register the source in corpus/__init__.py behind an enable_* flag.

Schedule it (Windows Task Scheduler)

Run weekly against your local bench. Save a wrapper run-scout.ps1:

# run-scout.ps1 — assumes LM Studio is serving the model
Set-Location "C:\Users\deudn\blastcontain-oss\tools\scout"
python -m blastcontain_scout --model "qwen/qwen3-30b-a3b-2507" --open-pr *>> "$env:USERPROFILE\scout.log"

Register a weekly task (Mondays 09:00):

schtasks /Create /TN "BlastContain arXiv Scout" /SC WEEKLY /D MON /ST 09:00 `
  /TR "powershell -NoProfile -ExecutionPolicy Bypass -File C:\Users\deudn\blastcontain-oss\tools\scout\run-scout.ps1"

The task only ever opens a draft PR — nothing reaches the corpus without your review.

Metadata

Release files for blastcontain-scout 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for blastcontain-scout 0.1.0
File Size Uploaded Provenance Actions
blastcontain_scout-0.1.0.tar.gz 19.7 kB With provenance Details for blastcontain_scout-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for blastcontain-scout 0.1.0
File Interpreter ABI Platform Actions
blastcontain_scout-0.1.0-py3-none-any.whl Python 3 none any Details for blastcontain_scout-0.1.0-py3-none-any.whl

Total release size: 39.3 kB

Release files / blastcontain_scout-0.1.0.tar.gz

Download URL blastcontain_scout-0.1.0.tar.gz
Size 19.7 kB
Tags Source
SHA-256 checksum
How to use checksums
cfa7691f0f78c8a7ac79f503a16246b749631dad2943a7d410001470c613c91e
BLAKE2b-256 checksum
How to use checksums
8d79ba1cc6cd8f2f0708344a6ee777bc7ec2fb589f40fcfbc1de9f657aa3d3ab
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 6, 2026.

Transparency log

Release files / blastcontain_scout-0.1.0-py3-none-any.whl

Download URL blastcontain_scout-0.1.0-py3-none-any.whl
Size 19.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
003e3001f87b3e3ede92260b0eb5b68df02bcb32f425b74fd0bdbddc3872c184
BLAKE2b-256 checksum
How to use checksums
aa390f7b4efcb8fd75bd6a89bece988074e3471e225e89e52d7078dfbe42ec61
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 6, 2026.

Transparency log

Security for blastcontain-scout 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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for blastcontain_scout-0.1.0.tar.gz

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 6, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page