fson (the C++ library and fson-check) and the editor tooling (ffs-lang-tools — the VS Code extensions and highlight.js grammars) are released under the MIT License. So are the sibling libraries cparse and callonce.

Use the code freely — including in closed-source and commercial products. There is no copyleft, no attribution beyond keeping the copyright line, and no CLA for contributions (inbound = outbound).

MIT License

Copyright (c) Fedem (Fehmi Demiralp)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Every source file carries SPDX-License-Identifier: MIT, and each repository ships the full text as LICENSE.

What the licence does not cover

The MIT grant is for the code. It does not grant rights to:

• the names FEDEM, FFS, FSON, FFS-MD, fson, fson-check, and the Fedem Visual Studio Marketplace publisher;
• the FEDEM / FFS / FSON logos and other brand assets;
• the domain fedem.eu and its subdomains.

If you publish a modified version, don't use these names or logos in a way that implies it is the official project or endorsed by FEDEM — rename your fork. Nominative use ("a fork of fson", "reads the FSON format") is fine. Each repo carries a TRADEMARKS.md with the details.

The FSON notation itself is free for anyone to implement — this section is about the name and the branding, not the format.

Third-party components

fson links cparse (MIT). The test suite uses GoogleTest (BSD-3-Clause), build-time only. The railroad-diagram sources use the tabatkins/railroad-diagrams DSL (CC0 / public-domain-equivalent). No component imposes terms beyond MIT on a consumer of fson.