Dependency license review · Early research

Review the license change before the release.

A planned dependency license review queue for small software teams, with package changes, source evidence, and recorded review decisions. Join the waitlist.

Get early access ↗

In research · Join the waitlist · No payment required

Designed around engineering leads who need to route dependency license questions to the right reviewer.

PRODUCT CONCEPT / 16
Concept preview · fictional example
Dependency changeMetadata findingReview
New parser packageLicense missingCheck source
Updated UI libraryIdentifier changedReviewer needed
Added utilitySource linkedPolicy review
Illustrative sample data. This is a product concept; these features are not available yet.
MADE FOR THE WORK IN BETWEEN↗
THE FRICTION

A dependency update introduces a package or changes its declared license. The release checklist needs a clear record of what changed, which evidence was checked, and who reviewed it.

THE PRODUCT WE’RE EXPLORING

LicenseTrail, in three parts.

LicenseTrail would compare dependency inventories and surface license metadata changes for review. Unknown or conflicting metadata would stay unresolved until someone checks the source.

Three planned capabilities we want to validate with early users.

01 / PLANNED

Highlight changed dependencies

Planned comparisons would focus on added packages and changed license declarations between two inventories.

02 / PLANNED

Keep the evidence link

Proposed records would retain the package version, source license file, and detected identifier for inspection.

03 / PLANNED

Route a review decision

Planned owner and decision fields would record approved use, a request for more information, or a replacement task.

AN INTENDED WORKFLOW

A clearer next step.
Less work around it.

A focused approach for engineering leads who need to route dependency license questions to the right reviewer.

  1. 01

    Provide a dependency inventory

    A future pilot would accept a supported manifest or software bill of materials without requiring production credentials.

  2. 02

    Inspect the changed declarations

    Review unknown identifiers and source documents before applying your organization’s policy.

  3. 03

    Record the review outcome

    Keep the reviewer, decision, and evidence with the release record.

GOOD TO KNOW

A few useful answers.

Can I scan dependencies today?

No. LicenseTrail is a research waitlist. Inventory uploads, comparison, and review workflows are planned features.

Does this replace legal advice or guarantee compliance?

No. The proposed product would organize technical metadata and review evidence. Your qualified reviewers would interpret obligations for your use case.

Is this software subscription tracking?

No. The focus is open-source dependency license declarations and evidence, not subscription renewal dates or payments.