01 — GitHub IP Audit

Find open-source license bombs
before your VC does.

A full legal analysis of your GitHub repository's open-source license exposure, co-ownership risk, and GPL/AGPL contamination — delivered by a practicing lawyer in 2 business days.

Order this report → From $299 · 2 business days

The Problem

Investors and acquirers are scanning your repo right now.

GPL contamination, missing license headers, and undisclosed third-party dependencies are among the top deal-killers at technical due diligence. Most founders discover these issues only when a VC's legal counsel flags them — at the worst possible moment in a raise or acquisition process.

Open-source license compliance isn't just a legal formality. A single AGPL dependency in your core product can trigger a copyleft obligation that affects your entire codebase — and transforms a closed SaaS into a forced open-source disclosure.

This audit gives you a complete picture before anyone else has it — and a remediation roadmap so you can fix it before it costs you the deal.

What You Get

Every deliverable, defined upfront.

Executive summary (1 page) — plain-language findings for your board or investor

Full dependency tree analysis — every third-party library mapped to its license

GPL/AGPL/LGPL contamination analysis with affected modules identified

Co-ownership and contributor IP assignment review

Risk matrix (High / Medium / Low) with severity scoring per finding

Prioritized remediation roadmap with specific action items

Full legal analysis PDF — due-diligence ready format

Optional 30-min debrief call to walk through findings with your team

Pricing

Choose your scope.

Starter

$299

2 business days

— Up to 1 repository
— Dependency + license scan
— Executive summary
— Risk matrix

Order this report →

Standard

Built for founders who ship fast and raise faster.

Pre-seed to Series B founders actively fundraising

If your data room is open or will be in the next 90 days, you need this before investors' counsel finds something you don't know about.

Tech startups approaching M&A or strategic acquisition

Acquirers run IP due diligence as a standard step. Walking in with a clean audit report signals professionalism and eliminates negotiating leverage from legal risk.

CTOs and engineering leads going into enterprise sales

Large enterprise customers require IP warranties in MSAs. This audit tells you exactly what you can and can't warrant before you sign.

FAQ

Common questions.

What access do you need to my repository?

Read-only access to your GitHub repository is sufficient. For public repos, no credentials are needed. For private repos, a temporary read-only token is sufficient and can be revoked after delivery.

What if my codebase uses only permissive licenses like MIT or Apache 2.0?

Permissive licenses are much lower risk, but there are still notice requirements, attribution obligations, and patent clauses that matter at due diligence. The audit confirms you're actually compliant — not just that your license choice is theoretically safe.

How is this different from an automated tool like FOSSA or Snyk?

Automated tools identify what's present. A lawyer tells you what it means, what your obligations are, and what happens if you get it wrong. I interpret the legal implications and give you a defensible legal analysis — not just a flag count.

Get Started

Ready to get clarity?

Describe your repository and timeline. I'll reply within 48 hours with a fixed price and scope.