Skip to content
DevUtils Online

Analytics

amplify-js vs partytown

partytown leads by 1.1 · narrow

B · leads

partytown

94.5

13,817 stars · MIT

amplify-js versus partytown is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 93.4 for amplify-js and 94.5 for partytown.

partytown has 13,817 GitHub stars to amplify-js's 9,556, a gap of 4,261 (1.45×). Forks are 2,171 for amplify-js and 460 for partytown. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 100 versus 80.

Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and partytown was last pushed on 09 November 2026 (7 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 1 for partytown (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 92.

amplify-js is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. partytown is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for amplify-js and 96 for partytown. This is a procurement signal, not legal advice.

In Analytics, both amplify-js (9,556 stars) and partytown (13,817 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: amplify-js is open source, partytown is open source.

The lead is split. amplify-js is furthest ahead on fork community (100 to 80), while partytown is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.

partytown finishes ahead at 94.5 against amplify-js at 93.4, a 1.1 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

amplify-js versus partytown metrics
Signal amplify-js partytown
GitHub stars 9,556 13,817
Forks 2,171 460
Open issues 518 1
Adoption 96 100
Activity 100 92
Community 100 80
Issue health 52 96
License 96 96
Self-hosting 100 100
Composite 93.4 94.5

Questions this page answers

Which has more GitHub stars, amplify-js or partytown?

partytown has more GitHub stars: 13,817 versus 9,556 for amplify-js. The gap is 4,261 stars.

Which was updated more recently, amplify-js or partytown?

amplify-js was pushed more recently: 16 November 2026 versus 09 November 2026 for partytown. That is 7 days apart.

Can I self-host both amplify-js and partytown?

Yes. This catalog marks both amplify-js and partytown as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, amplify-js or partytown?

amplify-js is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. partytown is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the amplify-js vs partytown score?

partytown scores 94.5 and amplify-js scores 93.4. This page calls that a narrow lead for partytown.

Related comparisons