Skip to content

Milestones

List view

  • doc Issues to track: - https://github.com/guacsec/guac-docs/issues/114 - https://github.com/guacsec/guac-docs/pull/110#pullrequestreview-1811748029 - https://github.com/guacsec/guac-docs/issues/114

    No due date
  • - Identity and trust

    No due date
    0/1 issues closed
  • - API stability - track based on days since API change, and when that hits 3 months without a change, we can consider it stable for a v1.0 release - At least 1 supported and recommended persistent and optimized, backend - Tested on small, medium, large datasets on some standardized hardware - track performance on highly used queries (TBD) and determine the acceptable time to completion - Upgrade path to 2.0 when it is out (how to get the data out to a 2.0 instance) - Ingestors - EITHER OR - Have a test suite for X documents that are generated from Y tooling/pipelines - Solve the NATS issue where we would have a centralized ingestor - Some set of use cases satisfied (TBD)

    No due date
  • Overdue by 1 year(s)
    Due by December 31, 2023
    2/2 issues closed
  • - New backend: ArangoDB - OIDC Authentication (client code) and Github Action collector - New APIs - Vuln APIs - Updated IsDepedency APIs - License Information - Returning only ID for mutation - MetataLinkFor API - Parsers - Ingest CDX Vex - Ingest OpenVex Next minor iteration of GUAC, focus on incorporating feedback from v0.1 and enabling real users to exercise their use cases with GUAC within their organizations.

    Overdue by 2 year(s)
    Due by September 30, 2023
    11/22 issues closed