License a retired software product: inventory the code first

Preserve the code and the context around it before archiving a retired product. Check rights and signing authority, describe missing records, and review a program's terms before granting access.

On this page
License a retired software product: inventory the code first

Save the context before you lose access to it

Retiring a software product can leave you with the code but little of the material that explains it. Before archiving the project, check that you still have its history, large files, build instructions and supporting records. You can then describe what remains for a possible licensing inquiry.

This article concerns a product that has ended while the company continues. Check who holds the code rights and who can sign for the company. If the company itself is closing, use the closing-company guide for the additional authority and preservation questions.

Pangea's company code licensing page names retired products among code a company may hold rights to. Its conditions still apply: the code must be private, never public or forked, and free of confidential data or conflicting third-party rights. Its estimate considers eligible source code, supporting files and Git history; generated files, vendored code, binaries, data dumps and third-party code are excluded.

What to preserve before archiving

Ask the person who maintains the repositories to check these parts together:

  • Code and history. Retain the repositories, branches and release tags, and record which revision represents the last shipped version.
  • Large files and separate services. Check Git Large File Storage (LFS) objects and assets held in object storage. Confirm the underlying files are available, not just references to them.
  • Build and run instructions. Keep the installation and configuration notes needed to explain whether the last version can still run.
  • Third-party components. Retain dependency licenses and the terms for vendored folders or embedded software development kits (SDKs).
  • Secrets and customer data. Keep scan results and a removal plan for access tokens, keys and exports. Those contents stay out of a shared package.
  • Hosted records. Check issue trackers, wikis and deployment notes before access ends.

GitHub's backup documentation distinguishes the methods. A mirror clone preserves the repository and its revision history; LFS objects need a separate fetch, and a wiki has its own repository. A GitHub migration archive omits LFS objects, discussions and packages. GitHub says these archives can serve for archiving, but documents no supported way to restore them on GitHub.

A migration archive alone can leave parts of this inventory missing. Use the backup-coverage section in the source-code guide for the handoff to the person checking the export.

What to say when records are missing

Meridian Forms is a fictional product retired when its owner moved to a services model. The company has the code but has lost access to a hosted tracker.

Part of the product / What the company can describe
Part of the productWhat the company can describe
Application and service repositoriesMirror clones with release tags
Large filesLFS was unused; uploaded brochures still need a separate object-storage export, or must be recorded as missing
Build documentationAn older runbook covers only an earlier version
Third-party componentsLockfiles are available; a vendored charting library's license is unverified
Secrets reviewToken scan clean; legacy API keys rotated
Issues and wikiCoverage unknown after the hosting vendor shut down

This tells a potential recipient what can be inspected and which questions remain. It does not establish that Meridian is eligible or ineligible. If you cannot recover a record, describe the gap rather than inferring its contents from the files you still hold.

Read the terms before committing the code

Preserving a product and agreeing to license it are separate decisions. Pangea says it pays within 15 days after receiving the buyer's payment. Completing tax and payout details is a prerequisite, not the event that starts that clock.

Its published withdrawal terms also distinguish stages. You may withdraw a repository before it is sent to labs. Once presented, it cannot be withdrawn from the active licensing process. A process underway may continue, including for up to 90 days after the agreement ends; completed licences remain valid. Withdrawing from future opportunities takes 30 days' notice.

Check those program-specific terms against the actual agreement. The Pangea profile keeps its published requirements together. For your own next step, complete the rights checklist, then use the finder to compare programs against the product you can actually describe.

Sources and limitations

Get Paid to License Your Code | Pangea.ai Checked 2026-11-15

Pangea.ai · Primary source

only code you hold the rights to, whether that's R&D, internal tools, retired products, or anything you own outright

Describes Pangea's own company code-licensing program. Individual acceptance, pricing and a visitor's rights require separate confirmation.

View source reference ↗
Backing up a repository Checked 2026-11-15

GitHub Docs · Primary source

If the repository includes Git Large File Storage objects, pull in the objects.

Describes GitHub platform backup mechanics; it does not address licensing readiness or a visitor's rights.

View source reference ↗