Wayne Beaton
Wayne Beaton
Thanks for sticking with this. I've updated more of the mapping data. Hopefully this addresses this (and the next) problem.
Good catch. Thanks for this. In my zeal to add mapping hints, I entered this one incorrectly. I've updated it. Thanks.
I've approved the issue on behalf of the IP Team so that you're not blocked. The line will still change because the authority of the approval has changed; this is...
> Only 2/20 were restricted dependencies, of which one still remains The IP Team has processed that one as well. So, AFAIK, you are not blocked at this time.
The tool currently supports four different file format readers: * `package-lock.json`; * `yarn.lock`; * `pnpm-lock.yaml`; and * Flat file (with one ID/line). Selection of the format reader is entirely based...
@HannesWell this looks pretty straightforward to me. Can we merge this?
Let's be careful with this one, please. I recall a conflict when I tried this update previously.
The error that we experienced in version 7.0.0 doesn't manifest with this version. I'm going to merge this. I'll also add some test cases.
Oops... My mistake. This does not compile/run with Java 11 (I had tested earlier with Java 21). I've reverted this commit. I'll keep this PR closed. See #388
Trying to parse the `package-lock.json` file from Java has been challenging. Not least because I just don't have the resources to really dig into and understand the format. The current...