pjfanning opened a new pull request, #234: URL: https://github.com/apache/openserverless-task/pull/234
## What The three `bun build` outputs checked into this repo carried only the standard ASF licence header: - `util/upload.js` (1.0 MB) - `util/config/configurator.js` - `admin/usage/usage.js` That header misrepresents the files. Most of `upload.js` is third-party code from npm: minio (Apache-2.0), 24 MIT packages (lodash, async, xml2js, readable-stream, ...), inherits and sax (ISC), stream-json (BSD-3-Clause). The configurator embeds @clack/core, @clack/prompts, sisteransi (MIT) and picocolors (ISC); usage.js embeds yaml (ISC). This PR keeps the ASF header for the ASF-authored part of each bundle and adds a second comment block naming the embedded packages grouped by licence, pointing to `LICENSE` for copyright holders and licence texts, and noting the file is generated. ## Checks - Apache RAT 0.18 over the repo: `Unapproved: 0` (the ASF header block is unchanged, so RAT and license-eye still match it). - `node --check` passes on all three files. - Package lists were taken from the `node_modules/` path markers inside each bundle and cross-checked against `util/upload/bun.lock`, `util/config/configurator/bun.lock` and `admin/usage/usagechecker/package-lock.json`. Licences were verified on the npm registry for the pinned versions. `stream-chain` is listed in `NOTICE` but is not actually embedded in `upload.js`. ## Related - apache/openserverless#251 adds the same packages, with copyright holders and the MIT/ISC/BSD-3-Clause texts, to the umbrella repo's top-level `LICENSE`. - This repo's own `LICENSE` should carry that list too; today it lives only in `NOTICE`, which per ASF policy should hold required attributions only. Happy to do that as a follow-up. - If the build scripts in the three `package.json` files gained a `--banner`, the header would be regenerated on every rebuild instead of being re-added by hand. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
