REUSE compliance of docsdevbr/pandoc-website-pt-br

Unfortunately, github.com/docsdevbr/pandoc-website-pt-br is not REUSE compliant and does not fully adopt the recommendations to make software licensing easy for humans and machines alike. Have a look at our tutorial to learn about the three simple steps to become REUSE compliant.

Badge

To add the badge to your project's README.md file, use the following snippet:

[![REUSE status](https://api.reuse.software/badge/github.com/docsdevbr/pandoc-website-pt-br)](https://api.reuse.software/info/github.com/docsdevbr/pandoc-website-pt-br)

Machine-readable information

The API provides machine-readable artifacts for automatic analysis.

• All information about the latest compliance check can also be accessed via a machine-parsable JSON file.
• You can gather the automatically generated SPDX SBOM in Tag:Value format, based on the reuse spdx command.

Last lint output

Commit 8c4f657e70b3d16260b86eee604e31c4b69a0fb5 was checked on 07 Oct 2026 14:52:17 UTC with the following result:

# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* doc/faqs.md
* doc/filters.md
* doc/press.md
* doc/using-the-pandoc-api.md

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: GPL-2.0-or-later
* Read errors: 0
* Invalid SPDX License Expressions: 0
* Files with copyright information: 20 / 24
* Files with license information: 20 / 24

Unfortunately, your project is not compliant with version 3.3 of the REUSE Specification :-(


# RECOMMENDATIONS

* Fix missing copyright/licensing information: For one or more files, the tool
  cannot find copyright and/or licensing information. You typically do this by
  adding 'SPDX-FileCopyrightText' and 'SPDX-License-Identifier' tags to each
  file. The tutorial explains additional ways to do this:
  <https://reuse.software/tutorial/>