REUSE compliance of ash-project/ash_double_entry

Unfortunately, github.com/ash-project/ash_double_entry 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/ash-project/ash_double_entry)](https://api.reuse.software/info/github.com/ash-project/ash_double_entry)

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 f56f13aee8c44c1a49839466ce092da2ad1293bb was checked on 02 Nov 2026 08:18:04 UTC with the following result: 

# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* test/support/migrations/20261101062443_update_ash_functions_extensions_2.exs

# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: MIT
* Read errors: 0
* Invalid SPDX License Expressions: 0
* Files with copyright information: 53 / 54
* Files with license information: 53 / 54

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/>