[License-discuss] Solving copyright & licensing information in client-side JavaScript, CSS etc.

Tue Aug 25 22:01:53 UTC 2026

Dear all,

after several workshops and iterations, a bunch of us finally agreed to 
a solution to the problem that client-side JavaScript, CSS etc. gets 
distributed to the user without proper (or typically any) license and 
copyright information.

Upon tripple-checking with everyone involved, I finally wrote about it 
here (incl. a small PoC):

https://matija.suklje.name/solving-copyright-licensing-information-in-client-side-javascript-css-and-similar-agreeing-on-a-useful-solution

TL;DR:

# *apply REUSE.software <https://reuse.software>* best practices, just as 
you would with writing in any other programming language
# use a *tool of /your choice/ to generate* either:

  * an SBOM – SPDX <https://spdx.dev>, CycloneDX
    <https://cyclonedx.org>, or whatever you prefer
  * an attribution file, of whatever kind you prefer
  * whatever document/file/webpage you feel is the most appropriate way
    to fulfill your licensing obligations

# make sure that *the file/page from /2./ is linked in a |<link> 
rel="license" href="">| HTML tag* in the HTML |<head>|
# create something *in the web UI to present this link too, using a |<a 
rel="license" href="">| HTML tag* in the HTML |<body>|

Next steps:

1. include it in REUSE.software documentation/FAQ

2. spread the word and start implementing it – I’m counting on you here

cheers,

Matija

-- 
gsm:tel:+386.41.849.552
www:https://matija.suklje.name
xmpp:hook at campfire.wheremymonkeyis.at
matrix: @hook:kompot.si
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20260826/a6184682/attachment.htm>