René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Consistency/Scanners] SCB scanners use different versioning system","articleBody":"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:\r\n\r\nGit-Repo-Scanner (SCB) - Chart.Version (linked to SCB release):\r\n```yaml\r\n - name: git-repo-scanner\r\n       image: \"{{ .Values.scanner.image.repository }}:{{ .Values.scanner.image.tag | default .Chart.Version }}\"\r\n``` \r\n\r\nNmap (Extern) - Chart.AppVersion (linked to current nmap release):\r\n```yaml\r\n  - name: nmap\r\n        image: \"{{ .Values.scanner.image.repository }}:{{ .Values.scanner.image.tag | default .Chart.AppVersion }}\"\r\n```\r\n\r\nAlthough this is a minor issue, it should probably kept in mind when new internally maintained scanners are added to the SCB.\r\n\r\nAlso affects *scanner.image.tag* in values.yaml.\r\n\r\nThe following scanners are affected:\r\n- [ ] git-repo-scanner\r\n- [ ] screenshooter\r\n- [ ] test-scan\r\n- [x] zap-advanced","author":{"url":"https://github.com/SebieF","@type":"Person","name":"SebieF"},"datePublished":"2021-10-11T12:32:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/716/secureCodeBox/issues/716"}