Skip to content

v3.0: rename Kuestenlogik.Bowire.Security.Scanner → …Security — the package is the Security rail, not just a scanner #487

Description

@thomas-stegemann

The .Scanner suffix under-describes what the package has become. It started as the bowire scan engine, but it is now the home of the whole Security rail: the rail contribution + security.js, the OWASP API Top-10 suite, the endpoint spider, and (as of #486) the manual OAST pen-test panel. Only the first of those is a "scanner".

Noted while placing #486: a manual out-of-band panel is plainly not a scanner concern, yet it belongs in this package because that's where the Security rail lives. The code placement is right; the package name is the mismatch.

Proposal

Rename Kuestenlogik.Bowire.Security.Scanner → Kuestenlogik.Bowire.Security (assembly, root namespace, NuGet id), keeping the scan engine as one area inside it. This is a breaking change (assembly + namespace + package id), hence v3.0.

Interaction with #421

#421 renames the whole surface Kuestenlogik.Bowire.* → Bowire.*. Fold this in: the target becomes Bowire.Security (not Bowire.Security.Scanner). Do them together so there's a single breaking cut, not two.

Scope / gotchas

  • The rail-fragment stitching keys off the assembly name (<AssemblyName>.wwwroot.js.<file>.js logical-resource convention in BowireHtmlGenerator) — the embedded security.js LogicalName must move in lockstep or the rail JS silently stops stitching.
  • InternalsVisibleTo (Kuestenlogik.Bowire.Tests, …IntegrationTests, bowire) and the force-load in BowireCli reference the type/assembly.
  • Update the docs/ADR references to the scanner package.

Low urgency, high tidiness — a name that finally matches the contents.

Metadata

Metadata

Labels

No labels
No labels

Projects

  • Status
    Backlog

Relationships

None yet

Development

No branches or pull requests

Issue actions