Closed lirantal closed 5 years ago
Merging #2 into master will decrease coverage by
30.11%
. The diff coverage is51.35%
.
@@ Coverage Diff @@
## master #2 +/- ##
===========================================
- Coverage 95.29% 65.17% -30.12%
===========================================
Files 7 5 -2
Lines 85 112 +27
Branches 12 18 +6
===========================================
- Hits 81 73 -8
- Misses 4 34 +30
- Partials 0 5 +5
Impacted Files | Coverage Δ | |
---|---|---|
packages/lockfile-lint-api/src/ParseLockFile.js | 0% <0%> (-100%) |
:arrow_down: |
packages/lockfile-lint-api/index.js | 100% <100%> (ø) |
:arrow_up: |
packages/lockfile-lint-api/src/ParseLockfile.js | 97.36% <97.36%> (ø) |
|
packages/lockfile-lint/src/cli.js | ||
packages/lockfile-lint/src/main.js |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 1c96a6e...242c1c8. Read the comment docs.
Description
BREAKING CHANGE Add support for parsing npm package-lock.json lockfiles
Types of changes
Related Issue
Motivation and Context
This has been a TBD for a while but we surely need to support npm's lockfile for policy and trust checking.
How Has This Been Tested?
Multiple unit and integration tests. Still room for more unit tests around the new flattening array for npm's lockfile.
Screenshots (if appropriate):
Checklist: