Pre-merge check for adding a new dependency

Created by

Dennis

Actor

Legacy Code License Scanner

Paste your project's package.json including the candidate new dependency and see immediately whether its license conflicts with your stack before merging.

Try for free

Legacy Code License Scannercodeclouds/legacy-code-license-scanner

Record type

Scanned input

Dependency

Ecosystem

+10 fields

Input

Inline manifests

Filename(required):package.json

Content(required):{"name":"my-app","license":"MIT","dependencies":{"express":"^4.18.0","extjs-gpl":"^3.3.0"}}

Output fields

Record type

Scanned input

Dependency

Ecosystem

License (SPDX)

License category

Severity

License A

License B

Finding

Highest severity (run)

Conflict count (run)

Dependencies checked

Error

How it works

Sign up on Apify or log in

The Legacy Code License Scanner Actor is ready to run with the inputs already set for "Pre-merge check for adding a new dependency". Sign up or log in and you'll land in Apify Console with a copy of this exact task.

Start the "Pre-merge check for adding a new dependency" task

The Legacy Code License Scanner Actor will start running based on the input automatically. You can also change all the input fields, like inline manifests, to match your specific use case.

Receive the "Pre-merge check for adding a new dependency" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as record type, scanned input, dependency, and more.

Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Pre-merge check for adding a new dependency" task via API.