Skip to content

Set up automated security scanning for core Abies libraries #128

@MCGPPeters

Description

@MCGPPeters

Goal

Add automated security scanning focused on the core libraries rather than only the sample applications.

Scope

  • Picea.Abies
  • Picea.Abies.Server
  • Picea.Abies.Server.Kestrel
  • Picea.Abies.Browser

Proposed work

  • Add CodeQL analysis for C# and JavaScript on PRs and main.
  • Add gitleaks secret scanning.
  • Add dependency and filesystem vulnerability scanning with Trivy or equivalent.
  • Add package vulnerability checks for .NET dependencies.
  • Define fail gates for high/critical findings.

Why

The main security goal is ensuring the framework itself does not ship obvious vulnerabilities or insecure defaults to consumers.

Acceptance criteria

  • PR workflow runs static security checks for the core library projects.
  • Main/nightly workflow runs a deeper scan.
  • Findings are surfaced in GitHub Security or CI logs.
  • Documented severity thresholds determine when the pipeline fails.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions