Skip to content

Licence: GPL-3.0-only + SECURITY.md - #6

Merged
usermaneGermane merged 1 commit into
mainfrom
proprietary-licence
Nov 8, 2026
Merged

usermaneGermane merged 1 commit into
mainfrom
proprietary-licence

Conversation

@usermaneGermane

@usermaneGermane usermaneGermane commented Nov 8, 2026 •

Copy link
Copy Markdown
Owner

What

  • LICENSE: MIT → GPL-3.0-only (official text from gnu.org), the same as the clients.
  • README: licence section.
  • SECURITY.md (new): private reporting, supported versions, scope.
  • .gitattributes: *.service and LICENSE are always LF. The 1.4.2 tarball had CRLF in passman-sync.service and LICENSE, because it was packed on Windows. This was harmless for the 1.4.2 update (the unit file is unchanged since 1.4.0), but systemd shouldn't get CRLF.

Why

Owner decision 2026-11-08: PassMan is open source and free for everyone, so the server is GPL too. This replaces this PR's earlier "proprietary" version, which was dropped before merging (the branch now holds one clean commit).

Checks

No code changed, so no version bump. pytest green.

🤖 Generated with Claude Code

https://claude.ai/code/session_011ojnyVg7ccsR3pZ64s7aRH

Owner decision 2026-11-08: PassMan is open source and free for everyone;
all four repositories use GPL-3.0-only. LICENSE is the official text from
gnu.org. README licence section; SECURITY.md says how to report privately.
.gitattributes: *.service and LICENSE are checked out with LF everywhere.
The 1.4.2 release tarball had CRLF in passman-sync.service and LICENSE,
because it was packed from a checkout on Windows (autocrlf=true).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ojnyVg7ccsR3pZ64s7aRH
@usermaneGermane usermaneGermane changed the title Licence: proprietary (was MIT) Licence: GPL-3.0-only + SECURITY.md Nov 8, 2026
@usermaneGermane
usermaneGermane merged commit 25cf8a8 into main Nov 8, 2026
3 checks passed
@usermaneGermane
usermaneGermane deleted the proprietary-licence branch November 8, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant