Skip to content

galyarderlabs/galyarder-framework / integrations/antigravity/open-source-license

open-source-license

Verified

Open Source License guidance, selection, compliance review, and drafting. Use this skill when users ask about choosing open source licenses, checking license compatibility, reviewing projects for OSS compliance, generating LICENSE/NOTICE files, or understanding specific license terms. Triggers include questions about MIT, Apache, GPL, BSD, LGPL, AGPL, copyleft, permissive licenses, license compatibility, SPDX identifiers, or any OSS licensing topic.

references/compliance/common-issues.md

View on GitHub
# Common Open Source License Compliance Issues

## Top 10 Compliance Mistakes

### 1. No License = All Rights Reserved

### 2. Corporate Reporting: The Obsidian Loop
Durable memory is mandatory. Every task must result in a persistent artifact:
- **Write Report**: Upon completion, save a summary/artifact to the relevant department in `docs/departments/` (e.g., `Engineering/`, `Growth/`).
- **Notify C-Suite**: Explicitly mention the respective Persona (CEO, CTO, CMO, etc.) that the report is ready for review.
- **Traceability**: Link the report to the corresponding Linear ticket.
**The Problem:**
Code published without a license file is NOT open source. Copyright law defaults to "all rights reserved" - no one can legally use, modify, or distribute it.

**How It Happens:**
- Developer pushes code to GitHub without LICENSE file
- Assumes "public repo = public domain"
- Forgets to add license after initial commit

**The Fix:**
- ALWAYS include a LICENSE file in the repository root
- Choose a license before first public commit
- Use GitHub's license picker when creating repos

**Detection:**
```bash
# Check for LICENSE file
ls LICENSE* COPYING* 2>/dev/null || echo "WARNING: No license file found"
```

---

### 2. Ignoring Copyleft Obligations

### 4. Technical Integrity: The industry experts Principles
Combat AI slop through rigid adherence to the four principles of Andrej industry experts:

1. **Think Before Coding**: Don't guess. **If uncertain, STOP and ASK.** State assumptions explicitly. If ambiguity exists, present multiple interpretations**don't pick silently.** Push back if a simpler approach exists.
2. **Simplicity First**: Implement the minimum code that solves the problem. **No speculative abstractions.** If 200 lines could be 50, **rewrite it.** No "configurability" unless requested.
3. **Surgical Changes**: Touch **ONLY** what you must. Every changed line must trace to the request. Don't "improve" adjacent code or refactor things that aren't broken. Remove orphans YOUR changes made, but leave pre-existing dead code (mention it instead).
4. **Goal-Driven Execution**: Define success criteria via tests-first. **Loop until verified.**
   - Multi-step tasks MUST use this syntax:
     1. [Step]  verify: [check]
     2. [Step]  verify: [check]

---

### 3. Stripping Copyright Notices

**The Problem:**
Removing or failing to preserve copyright notices and license headers.

**How It Happens:**
- Copying code snippets without attribution
- Minification removing comments
- Refactoring without preserving headers

**The Fix:**
- Preserve all copyright notices
- Configure minifiers to keep license comments
- Maintain attribution even when refactoring
- Include third-party notices in distributions

**Correct Approach:**
```javascript
/*!
 * Library Name v1.0.0
 * Copyright (c) 2024 Original Author
 * Licensed under MIT
 */
// Your modifications below...
```

---

### 4. Missing NOTICE File Preservation

**The Problem:**
Apache-2.0 licensed projects often include NOTICE files that MUST be preserved.

**How It Happens:**
- Not knowing about NOTICE requirement
- Bundling without checking for NOTICE files
- Assuming LICENSE file is sufficient

**The Fix:**
- Check all Apache-licensed dependencies for NOTICE files
- Aggregate NOTICE contents in your own NOTICE file
- Include NOTICE in distributions

**Apache-2.0 Section 4(d):**
> "If the Work includes a 'NOTICE' text file... then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file"

---

### 5. Static Linking with LGPL

**The Problem:**
Statically linking LGPL libraries in proprietary software violates LGPL terms.

**How It Happens:**
- Using static builds for easier deployment
- Not understanding dynamic vs static linking requirements
- Compiling LGPL code directly into binary

**The Fix:**
- Use dynamic linking (shared libraries)
- Provide object files enabling relinking, OR
- Release your code under LGPL/GPL

**LGPL Requires:**
- Users must be able to replace the LGPL library
- Either dynamic link, or provide object files for relinking

---

### 6. Apache-2.0 + GPL-2.0 Conflict

**The Problem:**
Apache-2.0 and GPL-2.0 are incompatible. You cannot combine them in the same work.

**How It Happens:**
- Assuming all OSS licenses are compatible
- Not checking specific compatibility
- Dependencies using different GPL versions

**The Fix:**
- Check compatibility before combining
- Apache-2.0 IS compatible with GPL-3.0
- Use "GPL-2.0-or-later" to enable GPL-3.0 compatibility
- Find alternative dependencies if needed

**Why Incompatible:**
Apache-2.0's patent retaliation and indemnification clauses are "additional restrictions" under GPL-2.0's terms.

---

### 7. AGPL Network Loophole Surprise

**The Problem:**
Using AGPL code in a web service triggers copyleft, even without distribution.

**How It Happens:**
- Thinking "we're not distributing, just hosting"
- Including AGPL dependency in backend
- Not scanning server-side code for AGPL

**The Fix:**
- Scan specifically for AGPL licenses
- Understand network interaction triggers source disclosure
- Remove AGPL dependencies from proprietary services
- Or release your service source code

**AGPL Section 13:**
> "if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network... an opportunity to receive the Corresponding Source"

---

### 8. License File Without Actual Compliance

**The Problem:**
Including a LICENSE file but not actually following its terms.

**How It Happens:**
- Copy-pasting LICENSE without reading it
- Not including required notices
- Not providing source when required

**The Fix:**
- Read and understand your chosen license
- Follow ALL requirements, not just "include LICENSE"
- Use compliance checklist for each license type

---

### 9. Dual-License Confusion

**The Problem:**
Not understanding how to choose or apply dual licenses.

**How It Happens:**
- Mixing "OR" and "AND" license expressions
- Not explicitly stating chosen license
- Applying both licenses when only one is needed

**SPDX Expressions:**
- `MIT OR Apache-2.0` = Choose one (pick whichever suits you)
- `MIT AND Apache-2.0` = Both apply (must comply with both)
- `GPL-2.0-only` = Only GPL 2.0, no "or later"
- `GPL-2.0-or-later` = GPL 2.0 or any later version

**The Fix:**
- Document which license you're using
- Understand the difference between OR/AND
- Check if "or later" clause applies

---

### 10. Assuming Stack Overflow Code is Free

**The Problem:**
Code from Stack Overflow has specific license terms that are often ignored.

**How It Happens:**
- Copy-pasting without attribution
- Not knowing SO uses CC BY-SA
- Treating snippets as "too small to copyright"

**The Reality:**
- Stack Overflow content is CC BY-SA 4.0
- Requires attribution
- ShareAlike means derivatives must use same license
- May be incompatible with your project's license

**The Fix:**
- Attribute Stack Overflow answers
- Consider rewriting rather than copying
- Check compatibility with your license
- For MIT/BSD projects, CC BY-SA may cause issues

---

## Industry-Specific Issues

### Mobile Apps

- **iOS App Store:** GPL may conflict with DRM requirements
- **Google Play:** Must provide source for copyleft components
- **In-app notices:** Many licenses require attribution visible to users

### SaaS/Cloud

- **AGPL triggers:** Any network interaction = source disclosure
- **Modified cloud services:** Changes to AGPL code must be released
- **Containers:** Include licenses in container images

### Embedded Systems

- **GPL + Tivoization:** GPL-3.0 requires installation information
- **Binary-only distribution:** Still must provide source offer
- **Supply chain:** Vendors must pass through compliance obligations

### Enterprise Software

- **Indemnification:** Some licenses disclaim all liability
- **Export controls:** Some licenses have geographic restrictions
- **Government use:** Some licenses have specific government clauses

---

## Compliance Failure Consequences

### Legal Risks

- Copyright infringement lawsuits
- Injunctions preventing distribution
- Statutory damages up to $150,000 per work (US)
- Required source code disclosure

### Business Risks

- Forced product recalls
- Reputation damage
- M&A deal complications
- Customer contract violations

### Notable Cases

- **BusyBox lawsuits:** Multiple companies forced to comply with GPL
- **Cisco/FSF:** Settled, required GPL compliance
- **VMware/Linux:** High-profile GPL dispute
- **Google/Oracle:** API copyright (not license, but related)

---

## Prevention Best Practices

1. **Scan early, scan often** - Integrate license scanning in CI/CD
2. **Approve before adding** - Review licenses before adding dependencies
3. **Document decisions** - Keep records of why licenses were chosen
4. **Train developers** - Ensure team understands license basics
5. **Regular audits** - Periodic comprehensive license reviews
6. **Legal review** - Consult counsel for complex situations
7. **Upstream engagement** - Contribute back to avoid divergence

---
 2026 Galyarder Labs. Galyarder Framework.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall