alvarotrigo/fullPage.js

Prefer upstream unless you specifically need this old frozen version; this fork adds no visible value and is far behind current fullPage.js.

Prefer upstream unless you specifically need a frozen 2017 snapshot. This fork adds no visible capabilities and is far behind current fullPage.js, so it is a poor default choice for new or maintained projects.

Do not adopt this fork for new work unless you specifically need the 2019 snapshot; upstream is far more active and materially safer to use.

Prefer upstream unless you specifically need an old frozen snapshot. This fork adds no visible capabilities and is materially behind on maintenance, bug fixes, and newer extension support.

Prefer upstream unless you specifically need the old 2018 baseline; this fork adds no visible capabilities and is materially behind on maintenance.

Prefer upstream unless you specifically need an old frozen snapshot. This fork offers no visible added capability and is materially behind on maintenance and fixes, so it is a weak adoption candidate for most users.

Prefer upstream unless you specifically need this exact old snapshot. This fork adds no visible value and is materially behind active development.

Prefer the upstream project unless you explicitly need an old, unmaintained snapshot; this fork offers stability by stagnation, not added capability.

Prefer upstream unless you specifically need this legacy 2019 snapshot. The fork adds no visible value and is far behind on fixes and maintenance, so adopters would mostly be choosing stasis over support.