Strategy | Direct Deps | Transitive Deps | Edges | Classifies Dev Dependencies | Container Scanning |
---|---|---|---|---|---|
`*META.{yml, json} | ✅ | ✅ | ❌ | ✅ | ✅ |
Find a file named MYMETA.json
, MYMETA.yml
, META.json
, or META.yml
.
- Parse
MYMETA.{yml, json}
orMETA.{yml, json}
to identify dependencies.
- Dependency required for
runtime
only will be reported. - Reported analysis will not have any edges.
- Build your perl target. When you do this, you should have
MYMETA.yml
andMYMETA.json
. - Execute
fossa analyze -o
on the project to print analyzed dependency graphing (this will not upload any analysis to any endpoint)
Explicitly specify an analysis target in .fossa.yml
file. The example below excludes all other analysis targets:
# .fossa.yml
version: 3
targets:
only:
- type: perl