Skip to content

Public roadmap: make vibgrate/cli easy to discover, try, and contribute to #144

Open

Description

@vibgrate-team

Why this exists

vibgrate/cli ships frequently (see Releases and the site changelog), but an empty Issues tab reads as “inactive” on places like AlternativeTo — even when the product is moving.

This issue is the public roadmap tracker. Comment to upvote or propose; we’ll open focused issues for work that is ready for contribution.

Near term (next ~30 days)

  • Keep README / install path obvious for AlternativeTo and first-time visitors
  • Document and demo the new --iac scanning path (Terraform, Kubernetes, Helm, Dockerfile)
  • Seed a small set of good first issue / help wanted tickets (linked below as we open them)
  • Improve contributor onboarding against CONTRIBUTING.md (fixtures, docs PRs, grammar work)

Mid term (~90 days)

  • Deeper language / resolution coverage where fixtures are thin
  • Stronger “blast radius / architecture” demos newcomers can run in minutes
  • Clearer path from CLI → VS Code / MCP (vg serve) for AI coding agents
  • Community-facing example repos beyond examples/github-actions

How we use this issue

  • Maintainers update checkboxes and link child issues as work starts
  • External ideas: open a Feature request (or comment here if you’re unsure)
  • Stars help people track releases; issues and PRs are how the project actually grows

Links

Activity

  1. deleted a comment from crowers on Sep 16, 2026
  2. vibgrate-team commented on Sep 18, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding batch (2026-09-18)

    Announcement

    Issues (all vibgrate-team)

    No help wanted on this batch. No external contributor replies needed today.

  3. vibgrate-team commented on Sep 21, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding 2026-09-21 — new public issues:

    Themes rewritten from adjacent SCA/SBOM CLI issue spaces (syft/trivy/grype/osv-scanner/dependency-check) into Vibgrate-specific docs/tests/bugs — no copy-paste titles. Mix stays documentation / enhancement / bug; good first only where newcomer-scoped; no new help wanted.

    Toward the ~200 public-issue discovery goal on the roadmap.

  4. vibgrate-team commented on Sep 22, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding batch (2026-09-22)

    Announcement

    New public issues

    Themes rewritten from adjacent SBOM/scan ecosystems (trivy / osv-scanner / cyclonedx-cli / cdxgen / dependency-track) into Vibgrate-specific local-first work — no copy-paste of foreign issue text.

  5. vibgrate-team commented on Sep 23, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding batch (2026-09-23)

    Announcement

    New public issues

    Themes rewritten from adjacent SBOM/scan/attestation ecosystems (syft / grype / trivy / osv-scanner / dependency-track / cosign) into Vibgrate-specific local-first work — no copy-paste of foreign issue text.

  6. vibgrate-team commented on Sep 24, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding batch (2026-09-24)

    Announcement

    New public issues (author: vibgrate-team)

    No external contributor engagement needing a reply today.

  7. vibgrate-team commented on Sep 25, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding batch (2026-09-25)

    Announcement

    New public issues (author: vibgrate-team)

    No help wanted on this batch. Engagement: no external contributor replies needing a maintainer response.

  8. vibgrate-team commented on Sep 28, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding batch (2026-09-28)

    Announcement

    New public issues (author: vibgrate-team)

    No help wanted on this batch. Engagement: no external contributor replies needing a maintainer response.

  9. vibgrate-team commented on Sep 29, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seeding batch (2026-09-29)

    Announcement

    New public issues (author: vibgrate-team)

    No help wanted on this batch. Engagement: no external contributor replies needing a maintainer response.

  10. vibgrate-team commented on Oct 2, 2026

    @vibgrate-team
    ContributorAuthor

    Daily seed — 2026-10-02

    Part B: Announcements discussion for v2026.930.1 — #313

    New issues (vibgrate-team):

    Themes rewritten from adjacent public issue classes (osv-scanner / cosign / cyclonedx-cli / trivy / syft) plus the 2026.930.1 YAML + --base surface — no copy-paste titles/bodies.

  11. vibgrate-team commented on Oct 5, 2026

    @vibgrate-team
    ContributorAuthor

    Batch 2026-10-05: new work following the 2026.1003.1 and 2026.1003.3 releases (announcement 1, announcement 2):

    Upvote with 👍 on whatever you'd like to see first.

  12. vibgrate-team commented on Oct 6, 2026

    @vibgrate-team
    ContributorAuthor

    Batch 2026-10-06: new work following the 2026.1005.1 release (JUnit reports, EPSS/KEV, redaction)

    Comment on any of them if you'd like to pick one up, or 👍 the ones you'd like to see first.

  13. vibgrate-team commented on Oct 7, 2026

    @vibgrate-team
    ContributorAuthor

    Batch 2026-10-07: seven new scoped tickets, mostly hardening around the new max-score Action input, vg fix honesty, and machine-readable output:

    Also out today: release notes for 2026.1006.1 in Discussions (#388). And thank you @yunaremaia for the README first-screen PR (#386, closes #149)! 👏 Comment on any ticket you'd like to pick up.

  14. vibgrate-team commented on Oct 8, 2026

    @vibgrate-team
    ContributorAuthor

    Batch 2026-10-08: five scoped tickets following the 2026.1007.1 release (risk budgets and the CI summary), plus a determinism fix:

    Big thanks to @Detoy for the run of merged PRs this week (#396, #402, #403, #405, #408). Comment on any ticket you'd like to pick up.

  15. vibgrate-team commented on Oct 9, 2026

    @vibgrate-team
    ContributorAuthor

    Batch 2026-10-09: seven scoped tickets (no new CLI release since 2026.1007.1) — Action docs sync, lockfile/HTML tests, locale-safe warning order, SBOM dependency kind, symlink warning codes, and an EPSS CI gate:

  16. vibgrate-team commented on Oct 20, 2026

    @vibgrate-team
    ContributorAuthor

    New on the roadmap today: #487 adds a fail-on-epss input to the GitHub Action so the new vg scan --fail-on-epss gate gets the same validated, first-class treatment as fail-on and max-score. A nice self-contained one if you know your way around composite actions.

  17. vibgrate-team commented on Oct 21, 2026

    @vibgrate-team
    ContributorAuthor

    Two new on the roadmap today, both following on from 2026.1020.1 (release notes):

    Comments and claims welcome.

  18. vibgrate-team commented on Oct 23, 2026

    @vibgrate-team
    ContributorAuthor

    Two more on the roadmap, both following on from #491 bringing Cargo optional crates into line in vg sbom export:

    Comments and claims welcome.

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

    enhancementNew feature or requestroadmapPublic product roadmap tracking

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions