← 输入框|github.com|刷新
Skip to content

[Consistency/Scanners] SCB scanners use different versioning system #716

Open

Description

@SebieF

Working on the consistency of all scanner files, it was noticed that our own scanners (SCB scanners), that is test-scan, git-repo-scanner and zap-advanced, use a different versioning scheme which is linked to the scb releases. This leads to an inconsistent and potentially confusing use of Chart.Version vs. Chart.AppVersion in the scan-type.yaml file:

Git-Repo-Scanner (SCB) - Chart.Version (linked to SCB release):

 - name: git-repo-scanner
       image: "{{ .Values.scanner.image.repository }}:{{ .Values.scanner.image.tag | default .Chart.Version }}"

Nmap (Extern) - Chart.AppVersion (linked to current nmap release):

  - name: nmap
        image: "{{ .Values.scanner.image.repository }}:{{ .Values.scanner.image.tag | default .Chart.AppVersion }}"

Although this is a minor issue, it should probably kept in mind when new internally maintained scanners are added to the SCB.

Also affects scanner.image.tag in values.yaml.

The following scanners are affected:

  • git-repo-scanner
  • screenshooter
  • test-scan
  • zap-advanced

Activity

  1. changed the title [-][Consistency/Scanners] SCB scanner use different versioning system[/-] [+][Consistency/Scanners] SCB scanners use different versioning system[/+] on Oct 13, 2021
  2. Weltraumschaf commented on Jul 27, 2023

    @Weltraumschaf
    Member

    This is intended bc we use our own SCB version for our own implemented scanners (.Chart.Version). For 3rd party scanners we use their versions (.Chart.AppVersion).

    We will not change this, but should document it properly.

  3. moved this from Triage to Backlog in secureCodeBoxon Aug 19, 2025
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

    maintenancescannerImplement or update a security scanner

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions