A full-cohort source-check range is not summarized on this page. The dated package retains row-level source checks and historical publication limits. The package-check date records offline acceptance, not a source refresh.
100 reviewed Lemon Squeezy company accounts. Evidence covers seller-published lemon squeezy purchase links; first-party payment, subscription or licensing statements. Claims apply only to the recorded property, product or workload.
Lemon Squeezy source composition | Source class | Count | Scope |
|---|
| Seller-published Lemon Squeezy purchase links | 24 | An organization’s own page links to a Lemon Squeezy purchase destination. Destinations and transactions were not tested. |
|---|
| First-party payment, subscription or licensing statements | 76 | The seller publishes a specific own-use statement about Lemon Squeezy; the claim remains limited to its stated product. |
|---|
Contexts in the Lemon Squeezy research: Qualitative property, workload, service-role or cohort-selection statement directly described by the accepted report; presence only, no prevalence claim. WhosBuilt review of the saved accepted report and approved examples; no source refresh.
Accepted report describes the retained list. Qualitative roles show presence, not prevalence. Counts refer only to the named recorded classifications; no source-by-context intersections are released. The displayed date is the package date. Source dates remain as recorded in the package; no source was refreshed for this analysis.
- Public sources do not verify paid subscriptions, organization-wide deployment or purchasing intent.
- Source retrieval dates record access; they do not make an older statement or historical deployment current.
- Published contact channels do not establish outreach permission, mailbox deliverability or purchasing authority.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.