Activities / How software is offered

Distributes a software product

distributes_software_product

Your app is itself a software product a maker ships to customers, rather than a service you operate and run yourself.

  • scope deployment
  • in the registry since 1.0
  • 217 laws in 110 jurisdictions name it

What triggers it

The lint's definition. It makes software available to others in any form: a desktop app, library, package, CLI, firmware, or a server others self-host. A service used only through a browser or API is not this.

This covers packaged desktop software, a licensed on-premises system, and a software development kit other companies embed in their own products.

What does not

A service you host and operate entirely yourself, with no separate product to install, does not count in the same way.

Often confused with Ships a mobile app.

The law it brings into scope

The kinds of law that name this activity in the LexLint law library, with the number of laws and jurisdictions in each, as of . The examples are chosen by rule, laws in force first and the widest jurisdiction first; each section's page lists every law.

Area of lawLawsJurisdictions
Cybersecurity law

Build software securely, handle reported flaws, and report incidents on a deadline.

136 84
Product and AI liability law

Answer in damages when defective software or an AI system causes harm.

56 38
AI law

Tell people when they are dealing with an AI system or its output, and control the uses the law calls high-risk.

13 5
Privacy law

Have a legal basis for personal data, honor people's rights over it, and report a breach.

9 7
Reuse law

Reproduce other publishers' content only as far as an exception or a license allows.

6 4
Communications law

Get consent before marketing, calling, recording or storing data on a device, and honor an opt-out.

3 3
Content moderation law

Act on notice of unlawful content, explain moderation decisions, and report on them.

1 1
Scraping law

Stay within computer-access law, a site's terms, and the copyright in what is copied.

1 1

Counterparties that usually come with it

  • a package registry
  • an update or download server

A component that cannot run as documented without one of these names it in its ACTIVITIES.md under talks_to, with required: true. That party's jurisdiction then joins the run of every product that uses the component, and the finding says why it is there. A default the deployer can change is asked about, never added. Talking to a party never makes a product that party.

In a declaration

This activity is a property of how software is offered, so only an application or a service declares it, and only as performs. A component with a package URL is on a package registry, so a validator adds this activity to it without its being written; a repository that is deployed and never distributed says so under not.

For an application

activities: - id: distributes_software_product mentioned: performs enabled: by_default note: <one sentence: what it does, and the kind of law it attracts>

History

In the registry since version 1.0, .

In the glossary: Distributes a software product.

The activity registry is LexLint's open list; this page's text is licensed under Creative Commons Attribution 4.0.