docs: add noncommercial license
Testing / remote-protocol-compat (0.9.3) (push) Successful in 35s
Testing / remote-protocol-compat (0.9.5) (push) Successful in 42s
Testing / test (push) Successful in 31s
Package Extension / package-extension (push) Successful in 28s
Build & Publish Package / publish (push) Successful in 32s

- Add the PolyForm Noncommercial License 1.0.0 with the required copyright notice.
- Declare the license file in Python package metadata.
- Document that commercial use is not permitted without separate licensing.
- Refresh the extension packaging wording to match the testing archive name.
This commit is contained in:
2026-06-14 15:47:48 +02:00
parent 642e22759f
commit 6a806f857c
3 changed files with 85 additions and 1 deletions
+9 -1
View File
@@ -491,7 +491,7 @@ The extension source lives in `extension/src/`. `extension/background.js` and `e
Packaging:
```bash
npm run package:extension # local/unpacked zip, keeps manifest.key for stable native-messaging ID
npm run package:extension # testing/unpacked zip, keeps manifest.key for stable native-messaging ID
npm run package:extension:webstore # Chrome Web Store zip, strips manifest.key
```
@@ -505,3 +505,11 @@ Chrome Web Store rejects `manifest.key`, so upload the `*-webstore-*` zip from `
- **Multiple browser instances can be auto-distinguished, but generated aliases are temporary**. Unaliased browsers get UUID aliases from the native host, which avoids collisions but is less ergonomic than setting a stable alias with `browser-cli clients rename --browser <current-alias> <new-alias>`.
- **Supported install targets are explicit, not “all Chromium browsers”**. The installer currently supports Chrome, Chromium, Brave, Edge, and Vivaldi. Other Chromium-based browsers may use different or shared native messaging manifest locations, so they need browser-specific verification before being added safely.
- **Linux and macOS only** — Windows native messaging paths are not yet handled.
---
## License
PolyForm Noncommercial License 1.0.0. See [LICENSE](LICENSE).
Commercial use is not permitted under this license. For commercial licensing, contact the project maintainer.