legal // credits

Credits & licensing

Pull's application code is MIT and its curriculum is CC BY-SA 4.0. The third-party books, specifications, and tools that lessons link to stay under their own licenses.

What is covered by which license

Application code — everything in the Pull repository that makes the product run is released under the MIT License. Fork it, self-host it, or build on it.

Pull curriculum — lesson text, roadmap structure, project specs, and original diagrams are written by Pull contributors and released under CC BY-SA 4.0. Reuse and adapt it with credit to Pull, and keep derivative curriculum under the same license.

Third-party works — books, specifications, documentation, and tools listed below are owned by their authors and licensed on their own terms. Pull links to them. It does not mirror, fork, or republish them, and linking does not relicense them.

Brand — the Pull name, wordmark, and logo files are not covered by either license.

How the curriculum uses external sources

  • Required reading is a deep link to the source, never a copy of its text.
  • Interactive labs open on the publisher's own site; Pull tracks only your completion state.
  • Explanations are written in Pull's own words. Direct quotes, if any, are short and attributed inline.
  • Diagrams under public/ are original to Pull unless the lesson credits another source.

Books

Required reading in lessons links to the freely licensed source repositories. Pull writes its own summaries and does not reproduce book text.

Specifications

Normative references. Lessons explain the specs in Pull's own words and link to the canonical text.

Implementations and libraries

Software users install or read while completing labs and projects. Each project stays under its own license.

Learning resources and tools

Companion material Pull links to from study plans. None of it is forked, mirrored, or embedded.

Something missing or wrong?

If you maintain a project listed here and want the attribution corrected, the license updated, or the reference removed, email hello@pullos.dev or open an issue on the repository. Licenses are recorded as published upstream at the time of writing — always check the source for the current terms.

See also Terms and Privacy.