refactor(security): move DependencyViolation and ComplianceReport to shared module #378
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Resolves #324
Moves inline class definitions from
Test-DependencyPinning.ps1to a dedicated module for improved reusability and testability.Changes
New:
scripts/security/Modules/SecurityClasses.psm1DependencyViolationclass - represents a single pinning violationComplianceReportclass - aggregates violations and generates reportsAddViolation()methodCalculateScore()methodToHashtable()method for serializationUpdated:
Test-DependencyPinning.ps1using moduleimport for SecurityClasses.psm1Testing
npm run lint:ps- PSScriptAnalyzer passesnpm run test:ps- All Pester tests pass (779 passed)Notes
Follows the pattern established by
FrontmatterValidation.psm1in the linting modules.