Fast, portable and reliable dependency analysis for any codebase. Supports license & vulnerability scanning for large monoliths. Language-agnostic; integrates with 20+ build systems.
We have a couple warnings from when we replaced old implementations of features with new ones advising customers about it. Both of these have been extant for more than 6 months, so I think it makes sense to remove the warnings.
Acceptance criteria
Fewer log messages when analyzing Go modules projects and containers.
Testing plan
I tested this manually. The changes are entirely cosmetic.
Risks
None.
Metrics
Checklist
[x] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
[x] If this PR introduced a user-visible change, I added documentation into docs/.
[x] If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
[x] If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
[x] If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
[x] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.
Overview
We have a couple warnings from when we replaced old implementations of features with new ones advising customers about it. Both of these have been extant for more than 6 months, so I think it makes sense to remove the warnings.
Acceptance criteria
Fewer log messages when analyzing Go modules projects and containers.
Testing plan
I tested this manually. The changes are entirely cosmetic.
Risks
None.
Metrics
Checklist
docs/.docs/README.msand gave consideration to how discoverable or not my documentation is.Changelog.md. If this PR did not mark a release, I added my changes into an# Unreleasedsection at the top..fossa.ymlorfossa-deps.{json.yml}, I updateddocs/references/files/*.schema.jsonAND I have updated example files used byfossa initcommand. You may also need to update these if you have added/removed new dependency type (e.g.pip) or analysis target type (e.g.poetry).docs/references/subcommands/<subcommand>.md.