#license-check.md
Version: 1.0.0
Target Models
- GPT-6 Astra
- GPT-5.6
- GPT-5.5
- GPT-5 Family
- Future GPT Models
#Purpose
This document defines engineering principles, repository licensing evaluation methods, dependency compliance standards, compatibility analysis strategies, governance practices, and long-term best practices for assessing software licenses before adopting, integrating, modifying, redistributing, or contributing to open-source projects.
It applies to
- Open Source Projects
- Enterprise Applications
- SaaS Platforms
- Libraries
- Frameworks
- SDKs
- APIs
- Monorepos
- Developer Tools
- Production Software
License evaluation is not reading a LICENSE file.
License evaluation is the engineering discipline of understanding the legal and operational obligations that govern software usage, modification, redistribution, contribution, dependency selection, and long-term sustainability.
Source code defines implementation.
Licenses define permitted engineering decisions.
#Core Philosophy
Understand Repository
↓
Identify License
↓
Understand Rights
↓
Understand Obligations
↓
Analyze Compatibility
↓
Assess Risks
↓
Document Findings
↓
Recommend Actions
Engineering decisions should respect licensing constraints before implementation begins.
#Primary Objective
Every license evaluation should maximize
Compliance
Compatibility
Engineering Safety
Operational Confidence
Maintainability
Risk Awareness
Governance
Long-Term Sustainability
Licensing should enable sustainable software engineering rather than become an unexpected constraint.
#Engineering Principles
Always prioritize
License Clarity
↓
Repository Ownership
↓
Dependency Compliance
↓
Compatibility
↓
Risk Identification
↓
Documentation
↓
Governance
↓
Continuous Review
Licensing should be evaluated as part of architecture—not after development.
#License Evaluation Lifecycle
Identify Repository
↓
Determine License
↓
Analyze Rights
↓
Analyze Obligations
↓
Evaluate Compatibility
↓
Assess Risks
↓
Document Findings
↓
Recommend Decisions
Compliance begins before adoption.
#Stage 1 — Repository Identification
Understand
Repository Purpose
↓
Maintainers
↓
Ownership
↓
Distribution Model
↓
Community
↓
Contribution Model
↓
Release Process
↓
Future Direction
Repository ownership provides licensing context.
#Stage 2 — License Discovery
Identify
Primary License
↓
Multiple Licenses
↓
Exceptions
↓
Custom Terms
↓
Contribution Agreements
↓
Patents
↓
Copyright Notices
↓
Repository Policies
Every repository should have clearly identifiable licensing information.
#Stage 3 — Rights Analysis
Understand
Usage Rights
↓
Modification Rights
↓
Distribution Rights
↓
Commercial Usage
↓
Private Usage
↓
Patent Rights
↓
Attribution
↓
Future Rights
Know what engineers are permitted to do.
#Stage 4 — Obligation Analysis
Review
Attribution Requirements
↓
Source Disclosure
↓
License Preservation
↓
Distribution Requirements
↓
Modification Notices
↓
Patent Clauses
↓
Contribution Rules
↓
Compliance Responsibilities
Every granted right may introduce obligations.
#Stage 5 — Dependency Licensing
Analyze
Direct Dependencies
↓
Transitive Dependencies
↓
License Relationships
↓
Compatibility
↓
Conflicting Licenses
↓
Supply Chain
↓
Maintenance Status
↓
Future Upgrades
Dependencies inherit licensing considerations.
#Stage 6 — Compatibility Analysis
Evaluate
Project License
↓
Dependencies
↓
Internal Software
↓
Commercial Products
↓
Third-Party Integrations
↓
Redistribution
↓
Future Contributions
↓
Long-Term Compatibility
Compatibility should be verified before integration.
#Stage 7 — Contribution Model
Review
Contribution Process
↓
Contributor Agreements
↓
Code Ownership
↓
Maintainer Rights
↓
Governance
↓
Review Standards
↓
Licensing Policies
↓
Community Expectations
Contribution rules influence long-term participation.
#Stage 8 — Operational Impact
Assess
Deployment
↓
Distribution
↓
Packaging
↓
Container Images
↓
Internal Usage
↓
Public Releases
↓
Documentation
↓
Compliance
Operational workflows should remain compliant.
#Stage 9 — Enterprise Considerations
Evaluate
Corporate Policies
↓
Compliance Standards
↓
Legal Review
↓
Approval Processes
↓
Risk Tolerance
↓
Vendor Relationships
↓
Procurement
↓
Governance
Enterprise adoption requires systematic evaluation.
#Stage 10 — Risk Assessment
Identify
Unknown Licenses
↓
Conflicting Terms
↓
Patent Risks
↓
Compliance Failures
↓
Redistribution Risks
↓
Operational Risks
↓
Maintenance Risks
↓
Future Restrictions
Licensing risks compound over time.
#Stage 11 — Repository Governance
Review
Ownership
↓
Maintainers
↓
Release Governance
↓
Policy Changes
↓
License Changes
↓
Contribution Governance
↓
Community Stability
↓
Project Health
Governance influences licensing stability.
#Stage 12 — Documentation
Evaluate
License Files
↓
Contribution Guides
↓
Compliance Notes
↓
Copyright Information
↓
Policy Documentation
↓
Exceptions
↓
Known Constraints
↓
Future Changes
Documentation preserves compliance knowledge.
#Stage 13 — Engineering Impact
Assess
Architecture Decisions
↓
Dependency Selection
↓
Distribution Model
↓
Build Systems
↓
Automation
↓
CI/CD
↓
Developer Experience
↓
Long-Term Evolution
Licensing influences technical architecture.
#Stage 14 — Review
Review
Compliance
↓
Compatibility
↓
Governance
↓
Documentation
↓
Operational Impact
↓
Engineering Risks
↓
Architecture
↓
Future Sustainability
License reviews should be systematic.
#Stage 15 — Trade-Off Analysis
Evaluate
Engineering Benefits
↓
Legal Constraints
↓
Operational Costs
↓
Maintenance Impact
↓
Migration Effort
↓
Community Value
↓
Business Alignment
↓
Long-Term Sustainability
Every license introduces engineering trade-offs.
#Stage 16 — Improvement Opportunities
Recommend
Documentation Improvements
↓
Compliance Automation
↓
Dependency Updates
↓
Governance Improvements
↓
Developer Education
↓
Review Processes
↓
Architecture Improvements
↓
Future Planning
Recommendations should strengthen compliance.
#Stage 17 — Validation
Validate
License Identification
↓
Compatibility
↓
Compliance
↓
Dependencies
↓
Documentation
↓
Governance
↓
Evidence
↓
Consistency
Conclusions should always be evidence-based.
#Stage 18 — Reporting
Produce
License Summary
↓
Compatibility Report
↓
Rights
↓
Obligations
↓
Risks
↓
Recommendations
↓
Priorities
↓
Future Considerations
Reports should support engineering decisions.
#Stage 19 — Governance
Maintain
Compliance Standards
↓
Review Process
↓
Dependency Policies
↓
Documentation
↓
Ownership
↓
Engineering Discipline
↓
Version Management
↓
Continuous Evolution
Compliance requires ongoing governance.
#Stage 20 — Long-Term Sustainability
Continuously improve
Compliance
↓
Compatibility
↓
Governance
↓
Documentation
↓
Engineering Quality
↓
Operational Readiness
↓
Knowledge Preservation
↓
Software Longevity
Exceptional engineering respects licensing throughout the software lifecycle.
#License Evaluation Quality Attributes
Evaluate
Compliance
Compatibility
Risk Awareness
Governance
Maintainability
Operational Readiness
Engineering Consistency
Long-Term Sustainability
#Engineering Questions
Before approving ask
Does the repository clearly define its licensing terms?
↓
Are engineering rights and obligations fully understood?
↓
Have dependency licenses been evaluated?
↓
Is the repository compatible with the intended project?
↓
Can engineers safely modify and redistribute the software?
↓
Are future compliance risks documented?
↓
Would experienced Staff or Principal Engineers confidently approve adoption based on this licensing evaluation?
#Severity Levels
Critical
Unknown license
License incompatibility
Compliance violations
Redistribution conflicts
Major
Weak documentation
Dependency conflicts
Governance uncertainty
Operational risks
Medium
Documentation gaps
Contribution ambiguity
Incomplete compatibility analysis
Minor
Formatting
Terminology consistency
Repository documentation quality
#License Evaluation Checklist
✓ Repository identified
✓ License discovered
✓ Rights analyzed
✓ Obligations documented
✓ Dependencies evaluated
✓ Compatibility reviewed
✓ Contribution model analyzed
✓ Operational impact assessed
✓ Enterprise considerations reviewed
✓ Risks identified
✓ Governance evaluated
✓ Documentation reviewed
✓ Engineering impact assessed
✓ Reviews completed
✓ Trade-offs documented
✓ Improvements proposed
✓ Findings validated
✓ Report completed
✓ Governance established
✓ Long-term sustainability evaluated
#Anti-Patterns
Avoid
Assuming repository popularity implies licensing safety
Ignoring transitive dependency licenses
Reading only the LICENSE file
Ignoring contribution agreements
Ignoring patent clauses
Evaluating only direct dependencies
Making architectural decisions before compliance review
Treating licensing as purely legal work
Ignoring governance changes
Assuming licenses never change
Ignoring operational distribution models
Adopting repositories without compatibility analysis
#Definition of Done
A license evaluation is considered complete when
- The repository's licensing model, ownership structure, granted rights, engineering obligations, dependency relationships, contribution policies, redistribution conditions, and governance practices are fully understood and documented.
- Direct and transitive dependencies, compatibility relationships, contribution requirements, operational distribution models, compliance responsibilities, and future licensing risks have been systematically evaluated using objective engineering evidence.
- Engineering recommendations preserve compliance while supporting maintainability, operational stability, architectural flexibility, sustainable dependency management, and long-term software evolution.
- Documentation clearly explains licensing decisions, compatibility findings, engineering implications, identified risks, operational constraints, governance considerations, and future review requirements.
- Engineering reviews validate compliance, compatibility, dependency analysis, governance quality, operational readiness, maintainability, architectural impact, and long-term sustainability before repository adoption or contribution.
- Repository adoption decisions remain reproducible, evidence-based, implementation-independent, and understandable by future maintainers without requiring repeated legal interpretation.
- The resulting evaluation demonstrates engineering discipline, governance awareness, operational responsibility, maintainability, compliance, compatibility, and long-term software sustainability.
Exceptional license evaluation is not measured by identifying a repository's license.
It is measured by understanding how licensing influences architecture, dependency selection, collaboration, redistribution, operational practices, and the long-term sustainability of software engineering decisions.