Skip to content

META: v0.2 readiness tracker #99

Closed

Description

@noeljackson

What v0.2 means

deepsec v0.1 (released a week ago) was feature-complete on the engineering axis: full pipeline, self-improving loop, 12-language coverage, AST grammars, CI integration. v0.2 closes the gap to real users — non-internal contributors, external installs, public scrutiny.

Status (2026-05-14)

Docs (high priority — friction-blockers for adoption)

Operational tooling (friction-blockers for daily use)

Evidence collection — the loop running in anger

Matcher / corpus follow-ups from PR #100's scan batch

Self-improvement levers

Adoption channels

Performance follow-up

Exit criteria — final status

v0.2 ships when

What's not in v0.2 (deferred to v0.3)

Activity

  1. added
    v0.2Targeted for the v0.2 readiness milestone
    on May 14, 2026
  2. noeljackson commented on May 14, 2026

    @noeljackson
    OwnerAuthor

    v0.2 engineering scope complete.

    Shipped this cycle (15 PRs)

    Docs / ops: #106 (deepsec doctor), #107 (CONTRIBUTING/SECURITY/index), #108 (deepsec spend).

    Matcher / corpus follow-ups from PR #100 scan batch: #109 (ruby-yaml-unsafe-load), #110 (open-redirect-from-referrer + bench fixture), #111 (nextjs-draft-mode-redirect + bench fixture), #112 (negative corpus from flask + jwt-go cores).

    Bench corpus growth (#84): #113, #115, #116, #117, #118, #119, #120 — went from 4 → 30 tasks (hit the exit criterion exactly). New language coverage: Java (4 fixtures), Rust (3), C (3), Kotlin (2), Swift (2). Whole-bench recall climbed from baseline 0.92 → 0.97; precision held at 1.0.

    Distribution (#88): #121 — GoReleaser config publishes Homebrew tap + Scoop bucket + ghcr.io multi-arch images + .deb/.rpm/.apk packages from a single tag push, per the simpler-than-the-original-issue approach.

    Prompt evolution (#86): #122 — benchsec process-score --core-prompt flag plus docs/prompt-evolution.md walkthrough wires the bench corpus into A/B prompt comparison.

    Deferred to v0.3

    Owner-side prerequisites (not gating engineering)

    1. Create empty repos: noeljackson/homebrew-deepsec and noeljackson/scoop-deepsec.
    2. Add HOMEBREW_TAP_TOKEN + SCOOP_TAP_TOKEN repo secrets (fine-grained PAT with Contents R+W on the two tap repos).
    3. Tag a release (git tag v0.2.0 && git push origin v0.2.0).

    Once those are in place, brew install noeljackson/deepsec/deepsec, scoop install deepsec, and docker pull ghcr.io/noeljackson/deepsec:v0.2.0 all work end-to-end. README install section is already updated to reflect the post-tag reality.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    v0.2Targeted for the v0.2 readiness milestone

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions