What Is the License for vorssaint-utils Source Code?

The vorssaint-utils project is released under the GNU General Public License version 3.0 (or any later version), as explicitly stated in the repository's README.md and the full LICENSE file.

The vorssaint/vorssaint-utils repository distributes a Swift utility package under a strong copyleft license that affects how you can use, modify, and redistribute the code. Understanding the specific license terms for vorssaint-utils source code is critical for legal compliance, particularly when embedding the utilities in proprietary applications or contributing modifications back to the project. According to the repository's documentation, the GPL-3.0-or-later designation applies to all source files, while brand assets are governed separately.

GPL-3.0-or-later License Terms

The vorssaint-utils codebase is protected under the GNU General Public License version 3.0 (GPL-3.0), with the additional clause "or any later version" (GPL-3.0+). This means you may choose to apply the terms of either GPL version 3 or any subsequent version published by the Free Software Foundation.

The full legal text resides in the LICENSE file at the repository root. According to the project's README.md, this license covers every source code file, ensuring that derivative works must also be distributed under the GPL.

Key License Documentation Files

LICENSE

The LICENSE file contains the complete, verbatim text of the GNU General Public License version 3.0. This is the primary legal document governing your use of the source code, and it must be included with any distribution of the software or derivative works.

README.md

The project's README.md displays a license badge and explicitly states the GPL-3.0+ status. This file serves as the first point of reference for developers checking the licensing status of vorssaint-utils before integration.

TRADEMARKS.md

While the source code falls under GPL-3.0+, the project's brand assets—including the name "Vorssaint," the logo, and UI designs—are covered separately in TRADEMARKS.md. This separation allows the code to remain fully open while protecting the commercial identity and trademarks of the project owners.

Package.swift

The Swift Package Manager manifest at Package.swift references the license file directly, ensuring that automated tools and package managers recognize the GPL-3.0+ status. This integration helps maintain license metadata across the Swift ecosystem and clarifies compliance requirements for dependency resolution.

Applying the License in Swift Development

When incorporating vorssaint-utils into your projects, you must include appropriate license headers and ensure compliance with GPL requirements regarding source distribution.

Adding License Headers to New Files

Every new source file you add to a fork or derivative work should include the standard GPL header to maintain clear copyright chains and license continuity:

//
//  MyFeature.swift
//
//  Copyright © 2026 Vorssaint
//
//  This program is free software: you can redistribute it and/or modify
//  it under the terms of the GNU General Public License as published by
//  the Free Software Foundation, either version 3 of the License, or
//  (at your option) any later version.
//
//  This program is distributed in the hope that it will be useful,
//  but WITHOUT ANY WARRANTY; without even the implied warranty of
//  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
//  GNU General Public License for more details.
//
//  You should have received a copy of the GNU General Public License
//  along with this program. If not, see <https://www.gnu.org/licenses/>.

Referencing the License in Package Manifests

If you redistribute vorssaint-utils or create a wrapper package, reference the license file in your Package.swift to maintain transparent licensing metadata for Swift Package Manager:

let package = Package(
    name: "VorssaintUtils",
    // …
    licenses: [
        .file(path: "LICENSE")
    ]
)

Runtime License Display

For GUI applications built with vorssaint-utils, you can programmatically load and display the license text to satisfy GPL attribution requirements in an "About" dialog or settings panel:

if let licenseURL = Bundle.main.url(forResource: "LICENSE", withExtension: nil),
   let licenseText = try? String(contentsOf: licenseURL) {
    // Show `licenseText` in a modal window
}

This approach reads the LICENSE file directly from the application bundle, ensuring end users have access to the full legal text as required by GPL-3.0 section 4.

Summary

• GPL-3.0-or-later: The vorssaint-utils source code is released under the GNU General Public License version 3.0 or any later version, as defined in the root LICENSE file.
• Key Files: The LICENSE contains the full text, README.md confirms the status, and TRADEMARKS.md handles non-code assets separately.
• Swift Package Integration: Package.swift references the license file for automated compliance checking within the Swift ecosystem.
• Attribution Requirements: Source files must carry GPL headers, and applications must make the license text available to end users through bundled documentation or runtime display.

Frequently Asked Questions

Is vorssaint-utils open source?

Yes, vorssaint-utils is fully open source software. The repository is publicly available under the GPL-3.0-or-later license, which grants you the freedom to run, study, share, and modify the software according to the terms outlined in the LICENSE file.

Can I use vorssaint-utils in commercial applications?

You may use vorssaint-utils in commercial applications, but the GPL-3.0-or-later license requires that any distributed derivative works or linked applications also be licensed under the GPL. This copyleft provision means you must release your application's source code under a compatible license if you distribute it publicly, ensuring downstream users retain the same freedoms.

What is the difference between the code license and brand assets?

The source code is licensed under GPL-3.0-or-later, allowing free modification and redistribution under copyleft terms. However, the project's brand assets—including the name "Vorssaint," official logos, and UI designs—are protected under the separate TRADEMARKS.md file. You cannot use these trademarks to identify derivative versions without permission, even though the underlying code is free to modify.

How do I properly attribute vorssaint-utils in my project?

Proper attribution requires including a copy of the GPL-3.0 license text in your distribution (typically by bundling the LICENSE file) and displaying appropriate copyright notices in your source code headers. If your application has an "About" dialog or credits section, you should list vorssaint-utils and provide a link to the repository or the full license text, following the pattern established in Sources/Vorssaint/main.swift and other project files.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}