Possible license / attribution concern – Taap.it using Dub?

[alexandre-sarfati]

Hi Dub team,

I came across a service that appears to offer functionality very similar to Dub and may potentially be using parts of the project without clear attribution.

Website:

• https://taap.it/conversion
• https://docs.taap.it

From what I can see, the product provides link tracking, analytics, and conversion attribution that look quite close to Dub’s feature set.

I’m not sure whether:

they are legitimately using Dub under its license,

they built something independently,

or if there might be code reuse without respecting the project’s license requirements.

But when looking at the API i can see the exact same parameters so it's most likely a non public fork :

Since Dub is open source, I wanted to flag this in case the maintainers want to review it.

To be clear, I don’t have proof of any violation — just raising the question so the team can decide whether it’s worth looking into.

Thanks for the great work on Dub!

[linear]

ENG-1681

[alexandre-sarfati]

Hello again,

I investigated further and found additional technical indicators that this service may be using a Dub-derived implementation.

Here are the main observations:

1. Client-side code contains leftover references

When inspecting the frontend source after logging into the platform > Analytics, I found a leftover reference to “Dub” in the compiled assets.

While this alone does not prove anything conclusively, it suggests the codebase may originate from Dub or a fork of it.

2. Conversion tracking implementation appears identical

The documentation at:

https://docs.taap.it/conversions/overview

describes a system that appears extremely close to the conversion attribution architecture introduced by Dub, including:

• redirect-based tracking
• a tracking ID passed via query parameter (ta_tid)
• storing the ID in a cookie
• sending conversion events after signup/purchase

The event payload structure is also very similar.

Example payload shown in their docs:

{
"customer": {
"externalId": "user_123",
"email": "john@example.com",
"firstname": "John",
"lastname": "Doe",
"phoneNumber": "+33612345678",
"avatarUrl": "https://..."
}
}

This mirrors the same customer tracking model used by Dub’s conversion endpoints.

Moreover they have the exact same Stripe and Shopify integration (same UI in Stripe app)

https://docs.taap.it/conversions/automatic/stripe

3. SDK references a Dub-based link system

Their SDK documentation:

https://taap.it/api/sdk

appears to reference a Dub-based short link system, including parameters and behavior matching Dub’s link tracking model.

(They even mention my dub fork "pimms" in it! lol)

4. No public repository despite apparent fork

The organization GitHub page:

https://github.com/orgs/taapit

based on the existence of the SDK https://www.npmjs.com/package/taapit-sdk it's the repo of their org.

But it contains no public repositories, which suggests the codebase may be private.

Since Dub is open source, this could simply be a private fork — but if Dub components are being used under licenses requiring attribution or disclosure, it may be worth reviewing.

To be clear, I’m not asserting a license violation, only pointing out technical similarities and artifacts that may help maintainers determine whether Dub code is being reused and whether the license terms are being respected.

Hope this helps.

Vive l’open source.

[steven-tey]

@alexandre-sarfati thank you for reporting! Just shared this with our legal counsel and will take appropriate action on our end 🙏