dennisdoomen / packageguard / 40098723891

82%

Build Type

push

github

Committed by web-flow

Commit Message

Suggest how to resolve each policy violation (#309)

* Suggest how to resolve each policy violation

Every DENIED entry now has a "- Resolve:" line after the reason. The hint
comes from the rule that caused the violation, not from the reason text:

- license not allowed: change the allow section or use another package,
  and note that riskExceptions do not cover license rules
- deny list entry: use another package, version or license, or remove the
  entry from the config file that introduced it
- risk rule: upgrade or replace the package, or add a riskExceptions entry
  with expiresOn
- minimum package age: use an older version, wait, or add a riskExceptions
  entry
- vulnerability rule: upgrade, or add a vulnerabilityExceptions entry
- malicious package: remove it

The explain command shows the same hint for a denied package.

PolicyViolation and PolicyDecision now use documented properties instead
of positional constructors. This removes the public PolicyViolation
constructor from PackageGuard.Core.

Closes #301

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Mention the Resolve line in the explain docs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Coverage Stats

2600 of 3512 branches covered (74.03%)

Branch coverage included in aggregate %.

160 of 195 new or added lines in 11 files covered. (82.05%)

31 existing lines in 6 files now uncovered.

8191 of 9788 relevant lines covered (83.68%)

1892.41 hits per line