dennisdoomen / packageguard / 32582277322

81%

push

github

Restructure PackageGuard.Core into themed folders

The project root had 45 loose .cs files mixing policy rules, package
data model, license resolution, risk enrichment, and risk scoring with
no grouping, unlike the existing CSharp/, Npm/, Sbom/, and Common/
folders which already follow a folder-per-concern convention.

Move root files into new Policy/, Package/, and Risk/ (with
Risk/Enrichment/ and Risk/Scoring/ subfolders, mirroring the existing
CSharp/FetchingStrategies/ nesting) folders, each mapping to a
PackageGuard.Core.<Folder> namespace. Move NpmPackageManager.cs into
the existing Npm/ folder and LicenseFetcher.cs into CSharp/, since
both are consumed exclusively from those ecosystems. Only
ProjectAnalyzer, IProjectAnalysisStrategy, AnalyzerSettings, and
AnalysisResult remain at the root as the genuinely cross-cutting
orchestration surface.

Mirror the same moves into PackageGuard.Specs, and update using
directives across PackageGuard.Core, PackageGuard, and
PackageGuard.Specs to reference the new namespaces.

This changes the public namespace of several types (AllowList,
DenyList, PackagePolicy, PackageSelector, ProjectPolicy,
PolicyViolation, GetPolicyByProject, PackageInfo, PackageInfoCollection,
LicenseEvidence, OsvVulnerabilityRecord, RiskDimensions, RiskEvaluator,
NpmPackageManager, LicenseFetcher), so the net8.0 approved public API
snapshot is updated accordingly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

1691 of 2426 branches covered (69.7%)

Branch coverage included in aggregate %.

5294 of 6489 relevant lines covered (81.58%)

1895.8 hits per line